=== imthewherd is now known as cgseller_is_away [10:12] Bug #1456538 was opened: Package install fails with "invoke-rc.d: unknown initscript, /etc/init.d/maas-regiond-worker not found." === cgseller_is_away is now known as imthewherd [13:01] mpontillo, rvba, allenap, juju+maas interlock? [13:02] dimitern: I don't have anything on my calendar...? [13:08] allenap, ah, sorry, I'll send you an invite, but rvba is already on it [13:12] allenap, you didn't miss much btw - and there's the agenda/minutes doc for the meeting (attached to the calendar event) [13:46] Bug #1456190 changed: 1.8b6 Add hardware broken [13:59] Bug #1456190 was opened: 1.8b6 Add hardware broken [14:10] Bug #1456190 changed: 1.8b6 Add hardware broken === capncrunch4me_ is now known as capncrunch4me [14:46] dimitern: sorry, I'm on swap today === mpontillo is now known as mpontillo-swap [14:47] mpontillo-swap, no worries === l6unchpad is now known as sky-shiny [15:09] Hello, I was hoping to get to the bottom of some errors I have been getting when deploying images I made with curtinator for ubuntu desktop distros. [15:12] I found similar questions in some of the bug reports on launch pad but im unable to figure out the solution. The error has to do with dev/sda/ not being available....I am acutally going to run an installation and get the exact message right now [15:26] Error: /dev/sda: unrecognised disk label Unexpected error while running command. Command: ['partprobe', '/dev/sda'] Exit code: 1 Reason: - Stdout: '' Stderr: '' Installation failed with exception: Unexpected error while running command. Command: ['curtin', 'block-meta', 'simple'] Exit code: 3 Reason: - === matsubara_ is now known as matsubara [16:01] so since going to 1.7.4, I can no longer get nodes to complete the provisioning process. I have backdoor’d into the ephemeral image and it simply hangs at the maas-signal process [16:06] just getting: request to http://10.0.0.2/MAAS/metadata//2012-03-01/ failed. sleeping 1.: '' [16:06] request to http://10.0.0.2/MAAS/metadata//2012-03-01/ failed. sleeping 1.: '' [16:21] ok, this appears to be a race condition. DNS isnt assigned to the node via DHCP until AFTER commissioning is done. Commissioning requires a FQDN to finish the commisioning. So it hangs waiting for a FQDN [16:21] so it hangs forever [16:28] Bug #1456696 was opened: 1.8b6 Cannot mark a ready node "Broken" [16:28] Bug #1456698 was opened: 1.8b6 Unable to deploy a node that is marked fixed when it is on [16:28] Bug #1456699 was opened: 1.8b6 Cannot mark a machine broken that is "deployed" and "on" [17:05] this appears to be a regression [19:24] hello anyone here? === yabbo is now known as Guest52952 [19:25] i have a maas setup with ipmi working on most of my systems but im having issues with it working on my sun servers [19:26] i can use the ipmitool through the cli and get back responses and even power on the server but i get timeouts from within maas itself [19:26] ipmitool -H 192.168.1.5 -I lanplus -U maas -P nothanks chassis power status Chassis Power is off [19:28] Guest52952: you should be seeing an error in clusterd.log if error is occurring with power actions [19:29] were is that log found [19:31] i see this in my maas.log [19:31] May 19 15:26:21 maas maas.power: message repeated 2 times: [ [ERROR] Node could not be queried node-db3fef0e-fdad-11e4-98bd-00505688b5b2 (delsol.vanillasystem.com) username invalid] May 19 15:26:21 maas maas.power: [ERROR] delsol.vanillasystem.com: Failed to query power state: username invalid. [19:31] i just verrified the username is correct [20:03] should i file it as a bug? [20:14] Guest52952: check the username is correct in MAAS [20:15] it is set to maas all lowercase... same as the command i use for ipmitool [20:16] blake_r: i have changed it to other accounts such as root which i have logins for aswell with the same error message. [20:17] Guest52952: do you have it set to IMPI 2.0? [20:18] yes [20:19] blake_r: i have tried both 1.5 and 2.0 [20:20] Guest52952: it needs to be set to 2.0 [20:21] Guest52952: can you provide a screenshot of the parameters for me, just to check [20:21] one sec uploading it somwere [20:25] blake_r: http://www.vanillasystem.com/x2200ipmi.jpg [20:26] Guest52952: check that there are no spaces after the username and password [20:26] Guest52952: are you sure that you can query that node from the maas server? [20:26] blake_r: yup no spaces [20:26] Guest52952: it has access to that network? [20:27] blake_r: yes... logged into maas i can run the ipmitool and get back a response [20:27] blake_r: yabbo@maas:/var/log/maas$ sudo -H -u maas ipmitool -H 192.168.1.5 -I lanplus -U maas -P nothanks chassis power status Chassis Power is off [20:29] blake_r: i can even log into the web gui of the eLOM on the server using the maas account and password [20:31] Guest52952: I would go ahead and file a bug then, something very wierd is happening [20:31] Guest52952: please attach all the logs [20:31] Guest52952: you could try to modify the impi template in /etc/maas/power/impi.template [20:32] blake_r: thanks... i have a dell server that when powered on it will query the power status but when powered off it does the same thing [20:32] blake_r: i dont have that directory... only /etc/maas [20:33] blake_r: no power directory [20:33] blake_r: nevermind its in /etc/maas/templates/power [20:33] Guest52952: yeah sorry