crowbar
database: keep the sst passwort in the proposal
When you enable/disable HA on the database proposal in your existing deployment, the sstuser_password wasn't stored and on reenable was reset to "random_password", which broke IST/SST of the existing cluster, so an inconsistent cluster was not recoverable without manual intervention. Always keep the password that was previously set, even if we switch to non-HA.
need to figure out how to migrate the data back into the proposal
@dirkmueller I've tried adding a migration there. It's only briefly tested. But at least it survived an installation on an already deployed galera system and migrated the (mysql) password into the proposal.
Note: I bumped the schema revision to 301 because of: https://github.com/crowbar/crowbar-openstack/pull/1764, but we can still re-visit that of course.
