Comment 4 for bug 1846212

I found a more serious issue with this.
It turns out that barbican is not updated with a new password if only the bm_password is changed.

So if the customer provisions the BMC and accidentally fat fingers the password, he/she cannot simply command line up, change the password to the correct value and re-execute.

Instead the username or password would also have to be changes and then changed back after the good password is stored.

The other alternative is to deprovision completely and then reprovision.

I think this is higher than a Low priority.

I will deliver the change to maintenance that re-fetches the password on a reconnect but that still won't fix the password only change behavior.