Activity log for bug #1379563

Date Who What changed Old value New value Message
2014-10-09 23:19:44 Auston McReynolds bug added bug
2014-10-09 23:20:00 Auston McReynolds summary Configuration Group Load Fails If Datastore Version is Inactive Configuration Group DB Load Fails If Datastore Version is Inactive
2014-10-09 23:20:04 Auston McReynolds trove: importance Undecided Medium
2014-10-09 23:20:07 Auston McReynolds trove: milestone kilo-1
2014-10-09 23:20:12 Auston McReynolds trove: status New Triaged
2014-10-17 06:19:52 OpenStack Infra trove: status Triaged In Progress
2014-10-17 06:19:52 OpenStack Infra trove: assignee Auston McReynolds (amcrn)
2014-10-19 05:49:25 Auston McReynolds description trove-manage db_load_datastore_config_parameters will fail if the datastore_version on which it's being run is marked as inactive (aka active is set to 0). this is not correct, because it's completely reasonable to want to update/refresh a datastore_version's configuration-group's parameters even if it's inactive. examples: - you're rolling out a new datastore_version, so you have it marked as active=0 until your launch date. - you've rolled out a new datastore_version, and you want to deactivate the old datastore_version. instances built prior to the deactivate are still on the old_version, and can still utilize their configuration-groups, hence the parameters should be update'able by the admin/cloud provider. how to reproduce: sudo $trove_root/bin/trove-manage --config-file=/etc/trove/trove.conf datastore_version_update $datastore_name $datastore_version $datastore_manager $glance_image_id "$datastore_packages" 0 sudo $trove_root/bin/trove-manage db_load_datastore_config_parameters $datastore_name $datastore_version $trove_root/src/trove/templates/mysql/validation-rules.json trove-manage db_load_datastore_config_parameters will fail if the datastore_version on which it's being run is marked as inactive (aka active is set to 0). this is not correct, because it's completely reasonable to want to update/refresh a datastore_version's configuration-group's parameters even if it's inactive. examples: - you're rolling out a new datastore_version, so you have it marked as active=0 until your launch date. - you've rolled out a new datastore_version, and you want to deactivate the old datastore_version. instances built prior to the deactivate are still on the old_version, and can still utilize their configuration-groups, hence the parameters should be update'able by the admin/cloud provider. how to reproduce: sudo /usr/local/bin/trove-manage --config-file=/etc/trove/trove.conf datastore_version_update mysql 5.5 mysql 1-2-3-4 "mysql-server-5.5" 0 sudo /usr/local/bin/trove-manage db_load_datastore_config_parameters mysql 5.5 /opt/stack/trove/trove/templates/mysql/validation-rules.json
2014-12-16 17:01:13 Nikhil Manchanda trove: milestone kilo-1 kilo-2
2015-01-06 16:49:16 OpenStack Infra trove: status In Progress Fix Committed
2015-02-03 16:27:41 Thierry Carrez trove: status Fix Committed Fix Released
2015-04-30 10:00:17 Thierry Carrez trove: milestone kilo-2 2015.1.0