Description of problem: packstack install from current juno RDO repo fails when trove is enabled at puppet trove-manage db_sync step. OperationalError: (OperationalError) (1832, "Cannot change column 'datastore_version_id': used in a foreign key constraint 'instances_ibfk_1'") '\nALTER TABLE instances CHANGE COLUMN datastore_version_id datastore_version_id VARCHAR(36) COLLATE utf8_unicode_ci NOT NULL' This is due to the current version of mariadb on Fedora 21 (10.0) being more strict about altering columns used in foreign key constraints. Likely an issue since mariadb 5.6. Not sure if SQLAlchemy needs an update since the DML is generated from there, although the originating python statement is in the db_sync code. Version-Release number of selected component (if applicable): Fedora 21 How reproducible: 100% Steps to Reproduce: 1. install packstack from juno RDO repo in Fedora 21 2. generate and edit answers to enable trove 3. run packstack with answers file Actual results: packstack install of trove fails at db_sync step in puppet manifest Expected results: packstack succeeds and continues to install Additional info:
Created attachment 995676 [details] trove pp log file
Workaround: 1. Create trove database: CREATE DATABASE trove; GRANT ALL PRIVILEGES ON trove.* TO trove@'localhost' IDENTIFIED BY 'pass'; GRANT ALL PRIVILEGES ON trove.* TO trove@'%' IDENTIFIED BY 'pass'; 2. Disable FK checks globally (affects all sessions): use trove; SET GLOBAL foreign_key_checks=0; 3. Setup all config files on Trove controller, then run: su -s /bin/sh -c "trove-manage db_sync" trove 4. Enable FK again SET GLOBAL foreign_key_checks=1; Success :) Here is output: 2015-04-29 00:41:59.854 27446 INFO migrate.versioning.api [-] 19 -> 20... 2015-04-29 00:41:59.864 27446 INFO trove.db.sqlalchemy.migrate_repo.schema [-] creating table configurations 2015-04-29 00:41:59.887 27446 INFO trove.db.sqlalchemy.migrate_repo.schema [-] creating table configuration_parameters 2015-04-29 00:42:00.013 27446 INFO migrate.versioning.api [-] done
Also seen in Fedora 22.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
It is still not fixed at upstream.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.