Comment 1 for bug 1589082

Revision history for this message
Nitish Krishna Kaveri (nitishk) wrote :

This bug occurs with old params because in 3.0 mysql_root_password had default value as c0ntrail123 when not supplied by user. also keystone_admin_password had default value as contrail123.

When these two are not supplied by user in 3.0 the defaults are taken.
When upgrade happens, the defaults are now blank because these params are now mandatory (generated if not supplied).
https://github.com/Juniper/contrail-puppet/commit/22583e137b2759a5460e1f9bb971bd82e4b6346e#diff-b7d255442b89e53b557c1dffcec1c225L628

For existing clusters, the workaround is to re-add the cluster params giving some password for the keys: mysql_root_password, keystone_admin_password

If you are using new params format in 3.0, you need to rename the mysql root password as given in the change below, AFTER upgrade to 3.0.2:

https://github.com/Juniper/contrail-server-manager/commit/4f106110cdb5906fbdc30cbe6cf0f92c45b11abd#diff-ee4207be841e09bf780338cf29ce26d5L135

If you haven't supplied mysql root password in the new params cluster in 3.0, you need to add it to your cluster JSON as in the link above and re-add the cluster.