Andres, Thanks for the quick reply and the info on the MaaS subsystem. A couple things I have noticed:
1. MaaS can power on/off the machine correctly and can detect that the system is either power on/off. 2. I believe the servers I'm trying to boot are using shared nics which seem to flap when the system is either starting up/shutting down, which might explain why the MaaS check might fail. It looks like the BMC deactivates for about a minute: # bash ./ipmi.sh server1 user Mon Apr 9 23:41:52 EDT 2018 server1: ok Mon Apr 9 23:41:52 EDT 2018 server1: on Mon Apr 9 23:41:52 EDT 2018 # bash ./ipmi.sh server1 user Mon Apr 9 23:41:53 EDT 2018 server1: ok Mon Apr 9 23:41:53 EDT 2018 server1: on Mon Apr 9 23:41:53 EDT 2018 # bash ./ipmi.sh server1 user Mon Apr 9 23:41:53 EDT 2018 server1: ok Mon Apr 9 23:41:53 EDT 2018 server1: on Mon Apr 9 23:41:53 EDT 2018 <I powered down the server through the IPMI interface> # bash ./ipmi.sh server1 user Mon Apr 9 23:41:59 EDT 2018 server1: connection timeout Mon Apr 9 23:42:19 EDT 2018 server1: connection timeout Mon Apr 9 23:42:39 EDT 2018 # bash ./ipmi.sh server1 user Mon Apr 9 23:42:52 EDT 2018 server1: ok Mon Apr 9 23:43:05 EDT 2018 server1: on Mon Apr 9 23:43:05 EDT 2018 Even just continually sending those same commands it looks like the BMC is locking up/flapping: # for i in `seq 1 100`;do bash ./ipmi.sh server1 user; sleep 3; done Tue Apr 10 00:09:31 EDT 2018 server1: ok Tue Apr 10 00:09:31 EDT 2018 server1: off Tue Apr 10 00:09:31 EDT 2018 Tue Apr 10 00:09:34 EDT 2018 server1: ok Tue Apr 10 00:09:34 EDT 2018 server1: off Tue Apr 10 00:09:35 EDT 2018 Tue Apr 10 00:09:38 EDT 2018 server1: connection timeout Tue Apr 10 00:09:58 EDT 2018 server1: connection timeout Tue Apr 10 00:10:18 EDT 2018 Tue Apr 10 00:10:21 EDT 2018 server1: ok Tue Apr 10 00:10:32 EDT 2018 server1: on Tue Apr 10 00:10:32 EDT 2018 Tue Apr 10 00:10:35 EDT 2018 server1: ok Tue Apr 10 00:10:36 EDT 2018 server1: on Tue Apr 10 00:10:36 EDT 2018 Tue Apr 10 00:10:39 EDT 2018 server1: connection timeout Tue Apr 10 00:10:59 EDT 2018 server1: connection timeout Tue Apr 10 00:11:19 EDT 2018 Tue Apr 10 00:11:22 EDT 2018 server1: connection timeout Tue Apr 10 00:11:42 EDT 2018 server1: on Tue Apr 10 00:11:46 EDT 2018 Tue Apr 10 00:11:49 EDT 2018 server1: ok Tue Apr 10 00:11:49 EDT 2018 server1: on Tue Apr 10 00:11:49 EDT 2018 Tue Apr 10 00:11:52 EDT 2018 server1: ok Tue Apr 10 00:11:52 EDT 2018 server1: on Tue Apr 10 00:11:52 EDT 2018 Tue Apr 10 00:11:55 EDT 2018 server1: connection timeout Tue Apr 10 00:12:15 EDT 2018 server1: connection timeout Tue Apr 10 00:12:36 EDT 2018 Tue Apr 10 00:12:39 EDT 2018 server1: connection timeout Tue Apr 10 00:12:59 EDT 2018 server1: on Tue Apr 10 00:13:02 EDT 2018 And unfortunately, I think this server has the latest BMC firmware. I'll try and use the dedicated BMC NIC and see if that helps. -- 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
