| === lp|away is now known as lazyPower | ||
| mup | Bug #1440763 was opened: 1.8b1 regiond.log Tracebacks when trying to deploy 42 nodes at a time <isolation> <MAAS:Triaged> <https://launchpad.net/bugs/1440763> | 15:12 |
|---|---|---|
| mup | Bug #1440765 was opened: 1.8b1 oauth.oauth.OAuthError: <isolation> <MAAS:Triaged> <https://launchpad.net/bugs/1440765> | 15:12 |
| === jfarschman is now known as MilesDenver | ||
| === cmagina_ is now known as cmagina | ||
| mup | Bug #1440823 was opened: Using both MAC address fields in AMT config causes AMT Power to fail <MAAS:New> <https://launchpad.net/bugs/1440823> | 18:06 |
| saltlake | Hi, | 18:22 |
| saltlake | I am working with maas and HO servers for the first time and I was able to see a "node" recognized on the maas server but wanted to know what the "power" settings for the node need to be ? The error I have right now is that "The node does not have apowere type" | 18:23 |
| roaksoax | saltlake: do your nodes have an IPMI bmc? | 18:25 |
| saltlake | roaksoax : Yes | 18:25 |
| roaksoax | saltlake: and how was the node recognized by MAAS? | 18:25 |
| roaksoax | saltlake: if you commission the node (even if you power it on manually), it should automatically configure the power parameters | 18:25 |
| saltlake | roaksoax : But I have not setup or done anything with them ..I setup Network boot option for the node and rebooted it. I see the MAC addresses look different than what they were in linux | 18:25 |
| roaksoax | that doesn't make any sense | 18:26 |
| roaksoax | how would the mac address be different? | 18:27 |
| roaksoax | saltlake: so if the node pxe booted from maas and registered itself into MAAS, automatically | 18:27 |
| saltlake | Not sure maybe I mistaken.. but looks like it .. | 18:27 |
| roaksoax | MAAS should have configured IPMI and updated the parameters automatically | 18:27 |
| saltlake | roaksoax : the sttus on the maas page says "commissioning" for the node but there is a red error on top of the page that says "Doens not have a power type etc.. " I could manually reboot the node again to see if it makes a difference | 18:28 |
| roaksoax | saltlake: yeah, reboot the node, make sure it PXE boots | 18:29 |
| roaksoax | saltlake: and let it do the commissioning | 18:29 |
| roaksoax | it should fix the power parameters | 18:29 |
| saltlake | roaksoax : I aborted the commissioning and restarted commission... is there a way to see what is going on on that node ? | 18:30 |
| roaksoax | saltlake: you'd have to setup console logging | 18:30 |
| roaksoax | saltlake: and look at it directly | 18:30 |
| saltlake | ok.. I have not tried that .. do you know how long it might take for a server to get commissioned ? | 18:31 |
| roaksoax | saltlake: depends, no more than 10 mins | 18:31 |
| roaksoax | i'd think | 18:31 |
| saltlake | Right now the node log syas this "INFO 1 minute ago Node changed status — From 'New' to 'Commissioning' " | 18:31 |
| roaksoax | depends on how fast is the server, how long it takes to do POST, etc | 18:31 |
| saltlake | Ok.. I'd give it 20 min and then reboot it physically | 18:32 |
| saltlake | I mean hard reset it | 18:32 |
| roaksoax | saltlake: Right. If the Node was in New state, and there were *no* power parameters configured, that means that when maas changed the status to 'Commissioning', it was unable to power on the node | 18:32 |
| roaksoax | saltlake: because it cannot control is power | 18:32 |
| roaksoax | saltlake: so, you need to force a reboot, physically | 18:32 |
| saltlake | ok.. | 18:32 |
| roaksoax | or via IPMI if you have that | 18:33 |
| saltlake | ok .. do I delete this node from maas before poering it on ? | 18:33 |
| roaksoax | saltlake: no | 18:33 |
| saltlake | ok | 18:33 |
| roaksoax | saltlake: just reboot it, and make sure it PXE boots from MAAS | 18:33 |
| roaksoax | saltlake: that should make it run the commissioning environment | 18:34 |
| roaksoax | that *should* allow BMC discovery | 18:34 |
| saltlake | roaksoax : "INFO 0 minutes ago PXE Request — commissioning " This is a good sign right ? | 19:18 |
| roaksoax | saltlake: yes | 19:23 |
| === jfarschman is now known as MilesDenver | ||
| saltlake | roaksoax : Unfortunately it failed comissioning thanks to this error on "failed [3/7] (00-maas-03-install-lldpd, 99-maas-01-wait-for-lldpd, 99-maas-02-capture-lldp)" How would I go about this now ? | 19:26 |
| roaksoax | saltlake: check the logs and see what failed? | 19:29 |
| saltlake | roaksoax : Finally the node went from commissioning to Ready.. I think that is a good sign!! | 20:01 |
| roaksoax | saltlake: did the power paramters get added automatically? | 20:02 |
| saltlake | roaksoax : Though the message continues to appear if I ignore the powere parameters.. it eventually commissions!! | 20:07 |
| saltlake | roaksoax : BY message I mean the intimidating red message complaining about power parameters on the maas page | 20:07 |
| saltlake | roaksoax : the power type in the node is still "--" though the status is ready.. should I be worried about that ? | 20:08 |
| saltlake | roaksoax : Ok I have concluded that the power type -- is NOT a good thing since maas cannot control the node. | 20:22 |
| saltlake | am now researching how to setup ipmi on these dl360 serers | 20:22 |
| saltlake | ok has anyone used a DL360 server and know how to set the power type parametrs for the respective node ? | 20:36 |
| saltlake | I think givev the boot screen for the node says it supports ILO 2 I think the power parameter should "Moonshot HP ILO chassis manager". Does nayone know how to get this setup ? | 20:47 |
| mup | Bug #1440894 was opened: get_effective_power_parameters() - exceptions.AttributeError: 'unicode' object has no attribute 'copy' <MAAS:New> <https://launchpad.net/bugs/1440894> | 21:19 |
| mup | Bug #1434257 was opened: MAAS should set dnssec-validation to no in /etc/bind/named.conf.options <MAAS:Triaged> <maas (Ubuntu):New> <https://launchpad.net/bugs/1434257> | 21:40 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!