Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionJustin Sherrill
2017-11-10 19:36:04 UTC
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.
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.
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).