| mup | Bug #1454469 was opened: 8 nodes transition to failed state within very short period of time <oil> <MAAS:New> <https://launchpad.net/bugs/1454469> | 01:06 |
|---|---|---|
| vijayt | Hi | 02:31 |
| vijayt | I need help in understanding how to pxe boot (enlist->commission) KVM guests. My VM's NIC model type is virtio and is in same network as MaaS, but pxe process does not succeed, it halts at ""Loading ubuntu/amd64/generic/trusty/release/boot-kernel." | 02:33 |
| vijayt | after retrying couple of times it goes through.. | 02:34 |
| vijayt | is there any specific guideline for configuring VMs for MaaS to support them | 02:34 |
| mup | Bug #1437494 changed: Cannot view power details from CLI for New nodes as Admin user. But I can view them in the WebUI <cli> <usability> <MAAS:Invalid> <https://launchpad.net/bugs/1437494> | 03:51 |
| mup | Bug #1447681 was opened: 1.8b3 Zones on "zone" page doesn't match zones on "node listing" <ui> <MAAS:Triaged> <https://launchpad.net/bugs/1447681> | 03:51 |
| mup | Bug #1454495 was opened: Changing nic port without deleting/recommissioning always comes up with non-eth0 <cts> <sts> <MAAS:New> <https://launchpad.net/bugs/1454495> | 05:07 |
| === ming is now known as Guest29940 | ||
| === TheRealMue is now known as TheMue | ||
| vijaytripathi | Hi | 06:09 |
| vijaytripathi | I have setup in which I have maas server able to pxe all hardware nodes w/o any issues, but during PXE process of KVM VMs it halts at "Loading ubuntu/amd64/generic/trusty/release/boot-kernel." | 06:09 |
| vijaytripathi | KVM Node and VM Network interface settings are here http://paste.ubuntu.com/11108288/ | 06:09 |
| vijaytripathi | Are there any other settings required here for configuring VMs for MaaS to support them? | 06:10 |
| mup | Bug #1454554 was opened: Spinner position on the image import page is off <ui> <MAAS:Triaged> <https://launchpad.net/bugs/1454554> | 08:34 |
| mup | Bug #1454554 changed: Spinner position on the image import page is off <ui> <MAAS:Triaged> <https://launchpad.net/bugs/1454554> | 08:46 |
| mup | Bug #1454554 was opened: Spinner position on the image import page is off <ui> <MAAS:Triaged> <https://launchpad.net/bugs/1454554> | 08:52 |
| mup | Bug #1454554 changed: Spinner position on the image import page is off <ui> <MAAS:Triaged> <https://launchpad.net/bugs/1454554> | 09:10 |
| mup | Bug #1454495 changed: Boot nic should always be eth0 <cts> <sts> <MAAS:Opinion> <https://launchpad.net/bugs/1454495> | 09:40 |
| mup | Bug #1453726 changed: MAAS error failed [3/7] (00-maas-03-install-lldpd, 99-maas-01-wait-for-lldpd, 99-maas-02-capture-lldp) <MAAS:Invalid> <https://launchpad.net/bugs/1453726> | 10:52 |
| anony_ | Hi guys, I have a Dell poweredge server that I'm trying to provision using the latest version of MaaS. However, during commissioning the Machine is shutdown and MaaS fails to repower it - giving the error "failed to power on". | 11:08 |
| anony_ | If you're wondering, Dell poweredge servers make use of IPMI version 2.02 | 11:09 |
| anony_ | My attempts so far where to check whether the hardware clocks are synchronized, and both were in fact properly synced | 11:09 |
| anony_ | Anyone knows how I can further debug/solve this issue? | 11:10 |
| Beret | hi | 12:07 |
| === jfarschman is now known as MilesDenver | ||
| bleepbloop | My nodes keep ending up in the "Failed Commissioning" state, could anyone help me trace this down? | 13:51 |
| blake_r | bleepbloop: give me about 30 minutes and then I can help you | 13:57 |
| bleepbloop | Thank you! | 13:57 |
| === imthewhe` is now known as cgseller_is_away | ||
| === cgseller_is_away is now known as imthewherd | ||
| blake_r | bleepbloop: hey whats up | 14:25 |
| blake_r | bleepbloop: what error are you getting | 14:25 |
| bleepbloop | blake_r: I just finally traced it down after about 5 days of debugging, what was happening was I have a pfsense box which controls all my external networking and my maas server setup to proxy all traffic over to the local subnet, pfsense was blocking the traffic over ipv6 that was being bridged across the maas server, even though we had all allow rules set. | 14:31 |
| bleepbloop | It was causing the pxe booted machines to hang for extremely long periods of time downloading windows updates | 14:31 |
| blake_r | bleepbloop: glad you figured that out, I would have been able to help you debug that, lol | 14:32 |
| blake_r | bleepbloop: wouldnt* | 14:32 |
| bleepbloop | blake_r: yeah I had an inkling it had something to do with our pfsense boxes because I had gone over the configuration of maas many times and everything there felt right, thank you anyway though! | 14:33 |
| blake_r | bleepbloop: no problem, glad you got it working let me know if you have nay maas questions | 14:33 |
| blake_r | bleepbloop: i be happy to help you out | 14:33 |
| bladernr_ | Hey guys, what exactly does this mean: Unable to connect to cluster 'Cluster 503bc204-030e-40d9-9c80-7f6112e9a5e6' (503bc204-030e-40d9-9c80-7f6112e9a5e6); no connections available. | 15:09 |
| roaksoax | bladernr_: seems like the region cannot contact the cluster | 15:10 |
| bladernr_ | how have I run out of connections? I have a 1.7.3 maas install | 15:10 |
| bladernr_ | region and cluster are on the same machine tooo :/ | 15:10 |
| roaksoax | bladernr_: check the cluster page to see if the cluster shows as connected or not | 15:10 |
| bladernr_ | yeah, cluster page says it's connected (check mark) | 15:10 |
| bladernr_ | and looking at the cluster page specifically, its state says Accepted | 15:11 |
| bladernr_ | if I click power state, it successfully queries... | 15:11 |
| bladernr_ | hrmm, probably a transient problem I've just never seen it before | 15:11 |
| bladernr_ | yeah, thre it goes... now it released | 15:12 |
| bladernr_ | that was just weird... and this is a MAAS server wtih only 2 nodes and one user. that was just bizarre | 15:12 |
| roaksoax | bladernr_: if the cluster fails to connect, then the region will also say that when trying to connect the cluste | 15:12 |
| roaksoax | rso that might have been the reson | 15:13 |
| bladernr_ | yeah... I found errors in the django log, but I'll not file a bug since I'm on 1.7.3 and not 1.7.4 yet... if It happens once I upgrade to 1.7.4, I'll file one. | 15:15 |
| bladernr_ | that was just bizarre | 15:15 |
| roaksoax | bladernr_: so when you upgrade, you will see that issue while daemons are being restarted | 15:21 |
| roaksoax | and the cluster is fully connected again | 15:21 |
| bladernr_ | ok... thanks for that heads up. I'll do it in a bit after I finish digging into this thing with images that I'm looking at right now | 15:21 |
| bleepbloop | If I have multiple harddrives in a server hooked up to maas, will maas properly handle multiple drives which are not in raid or will it just use one drive and waste the others? Is there a best practice to use with maas and raid? | 15:41 |
| dweaver | bleepbloop, normally MAAS will just use a single hard drive for the OS install. To use the additional drive(s) you would use additional management tools (like Juju/Puppet/Chef/Ansible) or you could modify the preseeds used by MAAS to partition and use the additional drive(s). | 15:47 |
| bleepbloop | dweaver: okay thank you! | 16:03 |
| stranger_ | Hi guys, I have a Dell poweredge server that I'm trying to provision using the latest version of MaaS. However, during commissioning the Machine is shutdown and MaaS fails to repower it - giving the error "failed to power on". | 16:05 |
| stranger_ | Any clues on how to debug this issue? | 16:06 |
| mup | Bug #1454767 was opened: "Node with this Hostname already exists" displays as JSON on Devices tab <ui> <MAAS:New> <https://launchpad.net/bugs/1454767> | 16:14 |
| elurkki | Getting error for "bmc-config --key-pair Lan_Config:IP_Address_Source" and the server is powered off. Where should I look into to figure out the problem? Thanks a lot | 17:04 |
| elurkki | Couldn't find this error from MaaS side, but it is shown on the console when the commisioning is ongoing | 17:05 |
| blake_r | elurkki: maas is performing that action | 17:17 |
| blake_r | elurkki: the script that does that is at /etc/maas/templates/commissioning-user-data/snippets/maas_ipmi_autodetect.py | 17:18 |
| blake_r | elurkki: looks like your machine does not like that option | 17:18 |
| elurkki | blake_r: Ok | 17:21 |
| elurkki | blake_r: I will check the script | 17:21 |
| elurkki | blake_r: Thanks | 17:21 |
| blake_r | elurkki: Your welcome | 17:21 |
| elurkki | Hmm, I assume I need to install Ubuntu this machine to see why this command fails | 17:40 |
| elurkki | +to | 17:40 |
| mup | Bug #1454810 was opened: IPMI power template can silently fail <oil> <MAAS:New> <https://launchpad.net/bugs/1454810> | 19:09 |
| elurkki | Any tips for bmc-config. The command gives error "Unable to get number of users" when executed with any flag (e.g. bmc-config --checkout) ? Thanks a lot | 19:21 |
| lm_ | hi all | 19:24 |
| lm_ | when will 1.8 be released? | 19:24 |
| blake_r | roaksoax: ^ | 19:49 |
| elurkki | Should the machine be reinstalled after stop / start node ? | 22:00 |
| elurkki | I assumed that stop/start would be just power off/on | 22:00 |
| elurkki | But seems that everytime I stop / start the machine, the OS is reinstalled | 22:00 |
| elurkki | Thanks for tips. | 22:00 |
| mwenning | elurkki, check in Settings at the very bottom. There is a clickbox that says "Disk Erasing On Release" and make sure it is unchecked | 22:49 |
| === bradm_ is now known as bradm | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!