Comment 5 for bug 1916860

I've made progress on a workaround. By setting the MAAS power type to "manual" and using the BMC's web UI to control it, I deployed Ubuntu on the affected node. I then found this, using ipmitool in-band:

# ipmitool lan print 1 | grep Cipher
RMCP+ Cipher Suites : 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16
Cipher Suite Priv Max : XXXaXXXXaXXXaXX

This output differed from another node that had no problems:

# ipmitool lan print 2 | grep Cipher
RMCP+ Cipher Suites : 0,1,2,3,6,7,8,11,12,15,16,17
Cipher Suite Priv Max : XaaaaaaaaaaaXXX

I tried setting the cipher suites on the x3650 to match those on the working system:

# ipmitool lan set 1 cipher_privs XaaaaaaaaaaaXXX

The node's BMC then began working, at least via ipmitool. (We're having unrelated problems with our MAAS server, so I'm not immediately able to test with MAAS.)

This is a rather blind change. I don't know much about IPMI cipher suites, so this configuration on the x3650 might be wrong in some significant way; but it at least works with ipmitool. Unfortunately, I don't know the node's configuration prior to the upgrade of our MAAS server, and documentation seems pretty sparse.