Description of problem: A command is being added to Satellite 6.3 (candlepin 2) to check the database prior to the cp database migration for any database validity problems that could cause the upgrade to fail. This needs to be added somehow to a 6.2.z/foreman-maintain release so that users can run this prior to the upgrade to 6.3. Version-Release number of selected component (if applicable): 6.2.z The idea being that the user would run 'foreman-maintain upgrade check' and some queries would be run to determine the health of the candlepin database prior to starting the 6.3 upgrade.
Ivan, Anurag, Should this go in to foreman-maintain 0.5 or 1.0 instead of Satellite 6.2.z?
F-m 1.0
Aligning to foreman-maintain 1.0 based upon comment 3. Please reach out to bcourt or jsherrill on any questions to ensure this is captured and available in time for maintenance-1.0.
Crog suggested we use https://github.com/candlepin/candlepinproject.org/blob/master/binaries/cpvalidation.zip and run liquibase pointing at that. Chris Rog should have more details on how to do that.
Information on how to run those validation steps: https://github.com/candlepin/candlepinproject.org/blob/master/docs/candlepin/database_validation.md
Found similar BZ created by Lukas - https://bugzilla.redhat.com/show_bug.cgi?id=1520326 where he mentioned below command to check candlepin validation # /usr/share/candlepin/cpdb --validate --verbose I would like to confirm whether above command serves the purpose of this BZ or not as version value specified for both BZs are different.
Reading the instructions: https://github.com/candlepin/candlepinproject.org/blob/master/docs/candlepin/database_validation.md it appears these are the same operation. Lzap says: WARNING: On installations pre 6.2.14 the cpdb utility will fail as the command line option will not be present I'm not sure what is actually causing this to be brought into 6.2.14 (as my discussion with the candlepin team did not reveal this). Lzap, can you shed some light? thanks!
Not sure what you are asking for, Justin. Let me try. In Sat 6.2 we do have "cpdp" but currently it don't understand --validate option, so it fails out with "Command line option not found" or similar. As part of the workaround for the issue we had during beta testing, CP guys backported the "--validate" option into 6.2 series, now it should be present. Providing this option will perform only validation of the database, not migration. The goal of formean-maintain is then calling this prior upgrading. An extra action might need to be taken if error is found (e.g. delete orhpaned records or similar).
bcourt, can you clarify if what is being backported to 6.2.14 matches this: https://github.com/candlepin/candlepinproject.org/blob/master/docs/candlepin/database_validation.md ?
Upstream bug assigned to kgaikwad
Then yes, this seems to be a duplicate. *** This bug has been marked as a duplicate of bug 1520326 ***