| roaksoax | allenap: any luck with the fix for maas-import-pxe-files? That's what I need to test in order to ceritify it is working | 16:04 |
|---|---|---|
| allenap | roaksoax: I'll do that now. | 16:05 |
| roaksoax | allenap: cool thanks | 16:05 |
| allenap | roaksoax: Is that https://bugs.launchpad.net/maas/+bug/1040462? Or the MAAS_PROVISIONING_SETTINGS one? | 16:06 |
| ubot5 | Ubuntu bug 1040462 in MAAS "maas-import-pxe-files blows up (packaged version)" [Critical,In progress] | 16:06 |
| allenap | Both need to be done... | 16:06 |
| roaksoax | allenap: right so running sudo maas-provisiong install-pxe-image alone fails too | 16:09 |
| allenap | The latter bug is https://bugs.launchpad.net/maas/+bug/1032462 | 16:09 |
| ubot5 | Ubuntu bug 1032462 in MAAS "MAAS_PROVISIONING_SETTINGS: required but not set and not documented?" [High,Triaged] | 16:09 |
| roaksoax | smoser: have you ever done something like: Package A version 1 Depends on B, then Package A version 2 no longer Depends on B. So on upgrade, remove package B automatically | 16:40 |
| smoser | i dont think you can cause the removal | 16:57 |
| melmoth | is not aptitude suppose to do this kind of stuff on its own ? | 16:58 |
| melmoth | i always use apt-get, but last time at a local lug, people told me that was one of the benefit of aptitude | 16:59 |
| melmoth | i did not check if i understood correctly what i heard though. | 16:59 |
| roaksoax | it is supposed to | 17:00 |
| roaksoax | I was thinking that a simple COnflicts/Replaces woiuld do, but my tests failed, so I consulted, and it should actually work | 17:02 |
| melmoth | if one can call dpkg -l from within a postinst script, one should be able to test wether package B is installed, and try to uninstall it. | 17:03 |
| melmoth | but i smell locking problems of some sort. | 17:03 |
| melmoth | Grmblblbl... When i juju deploy a service (within maas if that matter), how does the new system decide to install the regular version of juju, or the ppa one ? | 17:05 |
| melmoth | or, may be to ask it in a more clear way: "how does the new system decide to install some ppa or not". where does it get this information from ? | 17:06 |
| roaksoax | melmoth: right so using dpkg -i in my particular case was plain wrong :) | 17:07 |
| roaksoax | allenap: alright, i'm only waiting that fix and everything else should be fine | 17:26 |
| allenap | roaksoax: Yeah, I'm having to put kids in bed and such. | 17:54 |
| roaksoax | allenap: no worries | 17:56 |
| allenap | roaksoax: Simple fix! /usr/sbin/maas-provision, last line, should have "$@" appended. | 17:57 |
| allenap | (including quotes) | 17:58 |
| allenap | That doesn't fix the MAAS_PROVISIONING_SETTINGS problem, but I'll do that later. | 17:58 |
| allenap | roaksoax: If you don't get to it in the next hour, I'll propose a merge against the packaging branch. | 17:59 |
| roaksoax | allenap: lkike this? http://paste.ubuntu.com/1163087/ | 18:01 |
| roaksoax | allenap: btw.. maas-provision and its dependencies have to be removed on upgrade right? Otherwise, things like tftp will overlap | 18:02 |
| allenap | roaksoax: Yes, but you need to add "" quotes around the $@. | 18:58 |
| roaksoax | allenap: ok, so on the other hand | 18:59 |
| roaksoax | allenap: the tftp server doesn't seem to be working | 18:59 |
| allenap | roaksoax: Oh, jolly good :) | 18:59 |
| roaksoax | allenap: DNS doesn't have access to do what it needs to do | 18:59 |
| roaksoax | allenap: are we assuming that MAAS will handle both DNS/DHCP simultaneoulsy or can it do it separately | 19:01 |
| allenap | roaksoax: The TFTP port needs setting to 69 in /etc/maas/pserv.yaml. | 19:15 |
| roaksoax | allenap: could you change that in trunk? | 19:16 |
| allenap | roaksoax: The tftp/generator setting in pserv.yaml needs setting too. | 19:16 |
| allenap | roaksoax: etc/pserv.yaml in trunk is configured for development. I can add another file, pserv.prod.yaml, or something like that. I can't change etc/pserv.yaml without upsetting several other things (i.e. it can be done, but it's not going to be quick). | 19:19 |
| allenap | roaksoax: One other thing: maas (the package) does not depend on wget, but the scripts need it. | 19:20 |
| roaksoax | allenap: i'll do it in packaging | 19:42 |
| roaksoax | allenap: could you provide a diff? | 19:42 |
| roaksoax | allenap: IMHO, the settings file should all be production in trunk | 19:42 |
| allenap | roaksoax: Actually, I'm changing it in trunk. You'll still need to patch it, but it'll be more obvious. | 19:44 |
| allenap | Having it all production in trunk makes development a little challenging. | 19:44 |
| roaksoax | allenap: they shouldn't differ IMHO | 19:45 |
| roaksoax | allenap: please, just send me a diff that I'll need to apply | 19:45 |
| roaksoax | allenap: now, for the DHCP stuff, do we want to keep the debconf config like stuff? | 19:46 |
| roaksoax | i thought this was gonna be done through the WebUI | 19:46 |
| allenap | roaksoax: I don't know. I haven't used the debconf stuff for that yet. | 19:47 |
| roaksoax | allenap: right, but my point being is that how are we planning to configure DHCP | 19:47 |
| roaksoax | simply do it manually with maas-provision generate-dhcp-config? | 19:47 |
| allenap | roaksoax: Leave it at that for now. | 19:52 |
| roaksoax | allenap: ok bigjools was pointint stuff about that | 19:55 |
| roaksoax | so that's why I was checking | 19:55 |
| allenap | roaksoax: https://code.launchpad.net/~allenap/maas/default-to-production-config/+merge/121080 will make the default configuration production-ready. Then you can patch out the custom settings of tftp/port and tftp/generator, and it ought to work. | 20:05 |
| roaksoax | allenap: ok | 20:06 |
| allenap | roaksoax: Once that's landed, you can apply the following additional patch: http://paste.ubuntu.com/1163300/ | 20:07 |
| roaksoax | allenap: shouldn't we uncomment the #port and #generator? | 20:09 |
| allenap | roaksoax: They'll default to the same things. | 20:09 |
| roaksoax | allenap: ok, with that I get : "Unable to locate configuration file" while pxebooting | 20:10 |
| allenap | roaksoax: That /may/ be unrelated to this. Can you try: curl 'http://localhost/MAAS/api/1.0/pxeconfig/?mac=12:34:56:78:90:ab' | 20:11 |
| roaksoax | allenap: No provided arch! | 20:12 |
| allenap | roaksoax: Ah, okay, the next branch hasn't landed yet ;) Try: curl 'http://localhost/MAAS/api/1.0/pxeconfig/?mac=12:34:56:78:90:ab&arch=i386&subarch=generic' | 20:13 |
| roaksoax | allenap: http://pastebin.ubuntu.com/1163315/ | 20:14 |
| roaksoax | erro | 20:14 |
| roaksoax | allenap: No provided arch too | 20:14 |
| roaksoax | allenap: ok so we have a broken tftp server then | 20:17 |
| roaksoax | allenap: also please check that the changes in python-tx-tftp in trunk | 20:17 |
| roaksoax | are the same ones from the packaging | 20:17 |
| allenap | roaksoax: You didn't put "curl" before the URL ;) | 20:17 |
| roaksoax | allenap: yeah, curl http://localhost/MAAS/api/1.0/pxeconfig/?mac=12:34:56:78:90:ab&arch=i386&subarch=generic | 20:17 |
| roaksoax | gives the same | 20:17 |
| roaksoax | No Provided Arch | 20:17 |
| allenap | roaksoax: single quote it; the & is backgrounding the arch=... bit. | 20:18 |
| allenap | backgrounding the bit *before* rather. | 20:18 |
| roaksoax | allenap: that works | 20:18 |
| allenap | Okay, the problem is that there's a mismatch between the expectations of the TFTP server and what the pxeconfig view gives back. I'm still working on that. | 20:19 |
| roaksoax | alright | 20:19 |
| roaksoax | allenap: alright then, so I guess it is still not teasteable | 20:21 |
| roaksoax | allenap: though I'm just trying to enlist | 20:21 |
| roaksoax | allenap: and it doesn't work | 20:21 |
| allenap | roaksoax: I'm trying to fix it now. | 20:21 |
| roaksoax | allenap: ah ok thought it was deployment wise only not any pxe booting | 20:22 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!