30-maas-01-bmc-config failing on commissioning Cisco UCSC-C220-M4L

[Rod Smith]

I recently tried re-commissioning feebas, a Cisco UCS-C220-M4L server, using MAAS 2.9.2 (9164-g.ac176b5c4-0ubuntu1~20.04.1). This server had previously been successfully commissioned using earlier versions of MAAS (we had MAAS 2.6 installed most recently, but it's possible it was last successfully commissioned with 2.4 or earlier). The re-commissioning failed with the following output shown for 30-maas-01-bmc-config:

ERROR: Unable to get all current IPMI settings!
INFO: Loading IPMI kernel modules...
INFO: Checking for HP Moonshot...
INFO: Checking for IPMI...
INFO: IPMI detected!
INFO: Reading current IPMI BMC values...
Traceback (most recent call last):
  File "/tmp/user_data.sh.a3oqvC/scripts/commissioning/30-maas-01-bmc-config", line 1222, in <module>
    main()
  File "/tmp/user_data.sh.a3oqvC/scripts/commissioning/30-maas-01-bmc-config", line 1218, in main
    detect_and_configure(args, bmc_config_path)
  File "/tmp/user_data.sh.a3oqvC/scripts/commissioning/30-maas-01-bmc-config", line 1111, in detect_and_configure
    bmc.configure()
  File "/tmp/user_data.sh.a3oqvC/scripts/commissioning/30-maas-01-bmc-config", line 752, in configure
    self._bmc_get_config()
  File "/tmp/user_data.sh.a3oqvC/scripts/commissioning/30-maas-01-bmc-config", line 174, in _bmc_get_config
    proc = run(
  File "/usr/lib/python3.8/subprocess.py", line 491, in run
    stdout, stderr = process.communicate(input, timeout=timeout)
  File "/usr/lib/python3.8/subprocess.py", line 1024, in communicate
    stdout, stderr = self._communicate(input, endtime, timeout)
  File "/usr/lib/python3.8/subprocess.py", line 1867, in _communicate
    self._check_timeout(endtime, orig_timeout, stdout, stderr)
  File "/usr/lib/python3.8/subprocess.py", line 1068, in _check_timeout
    raise TimeoutExpired(
subprocess.TimeoutExpired: Command '['bmc-config', '--checkout']' timed out after 60 seconds

[Lee Trager (ltrager)]

MAAS 2.9 verifies that an IPMI BMC has been properly configured for MAAS usage. MAAS has always used "bmc-config --checkout" however it previously polled specific sections as needed. MAAS 2.9 pulls all BMC config at once and caches it. I'm wondering if that is just taking much longer than expected.

Could you run the following and tell me how long it takes? I suspect we just need to increase the timeout.

time bmc-config --checkout

[Rod Smith (rodsmith)]

Lee, I assume you wanted this run from the server itself (I had to use sudo), and are interested only in the time measurements, not the bmc-config output per se. What I got for the time output was:

Command exited with non-zero status 1
0.06user 0.01system 1:18.04elapsed 0%CPU (0avgtext+0avgdata 7112maxresident)k
1072inputs+0outputs (4major+567minor)pagefaults 0swaps

If you need something else, please tell me.