Comment 4 for bug 2068502

Sorry for being superficial, you're right.

Regarding MAAS overriding the current configuration: you can avoid this by checking the option "Skip configuring supported BMC controllers with a MAAS generated username and password" and MAAS will not override anything (the 30-maas-01-bmc-config will be skipped). When you are doing commissioning without that, you're basically asking MAAS to configure the BMC and, to do so, it will override the actual configuration (with the wrong cipher suite id, unfortunately).

Regarding the cipher suite id we should implement a solution to find the right one (thanks for pointing out possible ways of doing this and the correct default cipher suite id).