Public bug reported:
I'm trying to commission a machine and I'm getting the following error
in the maas.log:
Apr 9 00:24:39 maas maas.drivers.power.ipmi: [warn] Failed to change the boot
order to PXE xxxxxx: /usr/sbin/ipmi-config: connection timeout
Apr 9 00:25:45 maas maas.drivers.power.ipmi: [warn] Failed to change the boot
order to PXE xxxxxx: /usr/sbin/ipmi-config: connection timeout
Apr 9 00:27:13 maas maas.power: [error] Error changing power state (on) of
node: server1 (8w7s4m)
Apr 9 00:27:14 maas maas.node: [info] server1: Status transition from
COMMISSIONING to FAILED_COMMISSIONING
Apr 9 00:27:14 maas maas.node: [error] server1: Marking node failed: Power on
for the node failed: Could not contact node's BMC: Connection timed out while
performing power action. Check BMC configuration and connectivity and try
again.
MaaS Versions:
# dpkg -l | grep maas
ii maas 2.3.0-6434-gd354690-0ubuntu1~16.04.1
all "Metal as a Service" is a physical cloud and IPAM
ii maas-cli 2.3.0-6434-gd354690-0ubuntu1~16.04.1
all MAAS client and command-line interface
ii maas-common 2.3.0-6434-gd354690-0ubuntu1~16.04.1
all MAAS server common files
ii maas-dhcp 2.3.0-6434-gd354690-0ubuntu1~16.04.1
all MAAS DHCP server
ii maas-dns 2.3.0-6434-gd354690-0ubuntu1~16.04.1
all MAAS DNS server
ii maas-proxy 2.3.0-6434-gd354690-0ubuntu1~16.04.1
all MAAS Caching Proxy
ii maas-rack-controller 2.3.0-6434-gd354690-0ubuntu1~16.04.1
all Rack Controller for MAAS
ii maas-region-api 2.3.0-6434-gd354690-0ubuntu1~16.04.1
all Region controller API service for MAAS
ii maas-region-controller 2.3.0-6434-gd354690-0ubuntu1~16.04.1
all Region Controller for MAAS
ii python3-django-maas 2.3.0-6434-gd354690-0ubuntu1~16.04.1
all MAAS server Django web framework (Python 3)
ii python3-maas-client 2.3.0-6434-gd354690-0ubuntu1~16.04.1
all MAAS python API client (Python 3)
ii python3-maas-provisioningserver 2.3.0-6434-gd354690-0ubuntu1~16.04.1
all MAAS server provisioning libraries (Python 3)
Ubuntu version:
# lsb_release -rd
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Expected result:
MaaS is able to correctly reboot/start/stop the machine, it just can't change
the boot order to PXE. I would assume that if it can't change the boot order
after 1-2 attempts, MaaS wouldn't fail the commissioning but still allow
another 5-10 mins before failing, to let the server PXE boot since the server
is most likely already configured to PXE boot as the first option. It might
also be nice to have an option to disable MaaS from trying to set the boot
option so we don't waste time resetting the server when we know it can't set
the boot option.
What happens:
Right now, MaaS turns the server on, gets the first ipmi-config timeout, resets
the server, gets the second timeout, resets the server, and then immediately
fails the commissioning.
** Affects: maas (Ubuntu)
Importance: Undecided
Status: Incomplete
** Tags: ipmi maas
** Tags added: ipmi maas
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762555
Title:
ipmi-config connection timeout
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1762555/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
