| lathiat_ | Hi Folks.. I have a new installation of MAAS ( 1.8.0+bzr4001-0ubuntu2~trusty1) - when PXE booting to auto enlist it comes up, gets and ip and gets into cloud-init but seems to hang forever and doesn't enlist. Any suggestions on how I can debug that, not sure how to SSH to the host or what logs to check etc. | 03:01 |
|---|---|---|
| lathiat_ | previously these hosts were enlisting fine on a 1.7 installation | 03:01 |
| roaksoax_ | lathiat_: 1.check that maas-proxy is running 2. did you set DNS forwarders in the MAAS settings page so they can access archives and so on? | 03:52 |
| roaksoax_ | lathiat_: also, check clusterd.log to see if the machine pxe boots? | 03:52 |
| roaksoax_ | lathiat_: can you show the console of the machine that PXE booted? (kernel paramters and so on) | 03:52 |
| roaksoax_ | lathiat_: it seems that it is getting stuck when trying to access the repositories to download packages | 03:53 |
| lathiat_ | ah ok | 04:03 |
| lathiat_ | the machine definitely pxe boots, i confirmed that much | 04:03 |
| lathiat_ | i can also resolve the archives with local requests to the maas dns server IP | 04:05 |
| lathiat_ | i did however have a proxy that proabbly won't work set at one point, since removed, but i wonder if thats cached somewhere | 04:05 |
| lathiat_ | is there some way to logon to the machine once its half-booted in enlist? | 04:05 |
| lathiat_ | oh.. i also set a custom non official mirror.. i wonder if that is messing up the apt proxy | 04:06 |
| lathiat_ | if its expecting archive.ubuntu or something | 04:06 |
| === zz_CyberJacob is now known as CyberJacob | ||
| === Satyr1con is now known as Satyricon | ||
| === CyberJacob is now known as zz_CyberJacob | ||
| === zz_CyberJacob is now known as CyberJacob | ||
| === CyberJacob is now known as zz_CyberJacob | ||
| bitchecker | hi @ all | 09:15 |
| bitchecker | can MAAS install also other linux distributions? | 09:15 |
| === zz_CyberJacob is now known as CyberJacob | ||
| secate | Hi there! I'm using MAAS 1.8 and am trying to figure out the best way to override the default settings for the networking preseed data that gets generated when deploying hosts | 10:50 |
| secate | by default the only interface that gets configured on a node is the one connected to the MAAS server, but I'd also like to get another interface configured by default when deployments happen | 10:51 |
| secate | I've managed to find the code that generates the curtin network preseed data, but before I started to look where it's getting the config from I figured I should try my luck here | 10:53 |
| secate | so as an example, eth0 on my nodes are connected to a DHCP network with Internet access that is not managed by MAAS, and I would like it to be enabled and active after deployment, and eth1 is managed by MAAS and is an isolated network with no Internet access | 11:16 |
| secate | at the moment only eth1 is brought up during deployment, eth0 is disabled | 11:16 |
| secate | so when using Juju to deploy services, the nodes don't have Internet access via eth0 | 11:17 |
| === liam_ is now known as Guest30118 | ||
| secate | so after more googlefu apparently a feature like this is coming in 1.9 | 12:09 |
| secate | im going to test a daily build of 1.9 now, but if it isnt functioning yet is there some kind of workaround i can use for now, like either hacking the auto_interfaces option in the preseed config? | 12:10 |
| === lathiat_ is now known as lathiat | ||
| mup | Bug #1470930 opened: Devices API: claim-sticky-ip-address appears not to work <MAAS:New> <https://launchpad.net/bugs/1470930> | 14:41 |
| mup | Bug #1471249 opened: After MAAS server IP change, curtin still uses old IP <hs-arm64> <MAAS:New> <https://launchpad.net/bugs/1471249> | 14:41 |
| === mmidgett is now known as mTeK | ||
| === mmidgett is now known as mTeK | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!