Hi Mark, The output of the logs didn’t seem to indicate anything what I had forgotten to check “IPMI over LAN” in iDRAC.
root@ct-maas-rack03:/var/log/maas# tail rackd.log 2017-02-13 08:38:35 sstreams: [info] maas:v2:download/maas:boot:ubuntu:amd64:hwe-16.04-edge:xenial: to_add=['20170209'] to_remove=[] 2017-02-13 08:38:35 sstreams: [info] maas:v2:download/maas:boot:ubuntu:amd64:hwe-16.04-lowlatency:xenial: to_add=['20170209'] to_remove=[] 2017-02-13 08:38:35 sstreams: [info] maas:v2:download/maas:boot:grub-efi:arm64:generic:uefi: to_add=['20170125.0'] to_remove=[] 2017-02-13 08:38:35 sstreams: [info] maas:v2:download/maas:boot:ubuntu:amd64:ga-16.04:xenial: to_add=['20170209'] to_remove=[] 2017-02-13 08:38:35 sstreams: [info] maas:v2:download/maas:boot:pxelinux:i386:generic:pxe: to_add=['20160930.0'] to_remove=[] 2017-02-13 08:38:35 sstreams: [info] maas:v2:download/maas:boot:ubuntu:amd64:hwe-16.04-lowlatency-edge:xenial: to_add=['20170209'] to_remove=[] 2017-02-13 08:38:35 sstreams: [info] maas:v2:download/maas:boot:ubuntu:amd64:ga-16.04-lowlatency:xenial: to_add=['20170209'] to_remove=[] 2017-02-13 08:38:55 DHCPProbeService: [info] External DHCP probe complete. 2017-02-13 08:48:35 DHCPProbeService: [info] Probe for external DHCP servers started on interfaces: virbr0, ens3. 2017-02-13 08:48:56 DHCPProbeService: [info] External DHCP probe complete. root@ct-maas-rack03:/var/log/maas# tail maas.log Feb 13 08:38:35 ct-maas-rack03 maas.import-images: [info] Started importing boot images. Feb 13 08:38:35 ct-maas-rack03 maas.import-images: [info] Downloading image descriptions from https://ct-maas-region.activision.com/MAAS/images-stream/streams/v1/index.json Feb 13 08:38:35 ct-maas-rack03 maas.import-images: [info] Updating boot image iSCSI targets. Feb 13 08:38:36 ct-maas-rack03 maas.import-images: [info] Finished importing boot images, the region does not have any new images. Feb 13 08:41:43 ct-maas-rack03 maas.power: [error] ct-dev-u02: Power state could not be queried: Connection timed out while performing power action. Check BMC configuration and connectivity and try again. Feb 13 08:41:43 ct-maas-rack03 maas.power: [error] ct-dev-u02: Could not query power state: Connection timed out while performing power action. Check BMC configuration and connectivity and try again.. Feb 13 08:46:43 ct-maas-rack03 maas.power: [error] ct-dev-u02: Power state could not be queried: Connection timed out while performing power action. Check BMC configuration and connectivity and try again. Feb 13 08:46:43 ct-maas-rack03 maas.power: [error] ct-dev-u02: Could not query power state: Connection timed out while performing power action. Check BMC configuration and connectivity and try again.. Feb 13 08:51:59 ct-maas-rack03 maas.power: [error] ct-dev-u02: Power state could not be queried: Connection timed out while performing power action. Check BMC configuration and connectivity and try again. Feb 13 08:51:59 ct-maas-rack03 maas.power: [error] ct-dev-u02: Could not query power state: Connection timed out while performing power action. Check BMC configuration and connectivity and try again.. > On Feb 13, 2017, at 8:29 AM, Mark Shuttleworth <[email protected]> wrote: > > On 13/02/17 16:06, Mark Wenning wrote: >> R630 is definitely a supported server. >> Look like it autodetected OK, if you have those settings in the GUI. One >> quick thing you might want to check is in the iDRAC -> Network Settings, >> scroll near the bottom and make sure that "IPMI Over LAN" is enabled. >> When you tell it to commission, do you see the R630 power on? You should >> also be able to click "Check Power" at the top of the GUI page and see it >> change to green Power On after a few seconds. > > Try using ipmipower from the freeipmi-tools package to check power on the BMC: > > ipmipower -u maas -p <password-for-bmc-in-maas> -h ip-of-bmc -s > > The rack controller (not the region controller) talks to the BMC. So watch > the rackd.log not the regiond.log as I suspect useful things will show up > there. > > Also, you need to have a route from the rack controller to the BMC. If your > BMC is on a network that the rack controller cannot reach, that can cause > these issues. > > Mark > -- > Maas-devel mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/maas-devel
-- Maas-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/maas-devel
