Can't recommission to correct bad IPMI password without hacking node state into Commissioning via SQL

[Jason Hobbs]

We upgraded to 1.8 MAAS, recommissioned our nodes (which made new passwords) and then later downgraded back to our 1.7 MAAS via restoring the old LXC backup of 1.7.

When we went back to 1.7, many of the nodes had different IPMI passwords due to the recommissioning. I have the default passwords for them and so I wanted to set them in the 'Commissioning' state, then power them on via the command line. This doesn't work though because the nodes immediately get set to 'Failed Commissioning' when their power commands don't work.

I didn't want to delete and recreate these nodes because they have lots of tags and events that I don't want to lose. So, to fix this, I had to manually run SQL commands to set these node's state to 1 (commissioning), so that when I powered them up they would recommission.

[Jason Hobbs (jason-hobbs)]

You can recreate this with any IPMI system by changing its password to something that's incorrect, and then trying to commission it.

[Jason Hobbs (jason-hobbs)]

The SQL I used was like this:

update maasserver_node set status = 1 where power_type = 'ipmi';

[Ricardo Bánffy (rbanffy)]

Since it seems to be a rare condition (a 1.8 to 1.7 downgrade via an image restore) and we have a workaround for it, I'm setting its importance to "low".

[Adam Collard (adam-collard)]

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team