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.
1. Proposed title of this feature request.
=> [RFE] While Restoring satellite, satellite-maintain \ foreman-maintain should simply skip all initial checks and start from the installer-reset step
2. What are the nature and description of the request?
A) Attempt 1 - Started restoration, due to some reason it fails. After Correcting it, goes for 2nd attempt
B) Attempt 2 - satellite-maintain \ foreman-maintain checked the connectivity with DBs. This step has to be skipped because they are already dropped in
first attempt to restore. After --whitelist="candlepin-db-up,foreman-db-up,pulpcore-db-up" goes for Third attempt
Ended with Below Error
~~~~~~
The following steps ended up in failing state:
[candlepin-db-up]
[foreman-db-up]
[pulpcore-db-up]
~~~~~~
C) Attempt 3 - satellite-maintain \ foreman-maintain stops at dropping database which is already dropped and end at "restore-installer-reset" state
[ERROR ] [root] runuser -l postgres -c 'dropdb foreman' failed! Check the output for error!
Reproducer:
- Remove all CDN repos
- Make sure that the following command fails 'dnf module enable pki-core --assumeyes'
- Run satellite-maintain restore <backupdir>
- Correct the CDN repos
- Run satellite-maintain restore <backupdir>
3. Why do you need this? (List the business requirements here).
satellite-maintain \ foreman-maintain should simply skip all initial checks and start from the "installer-reset" step
4. How would you like to achieve this? (List the functional requirements here).
satellite-maintain \ foreman-maintain should simply skip all initial checks and start from the "installer-reset" step
5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
satellite-maintain \ foreman-maintain should not fail at already checked steps and start with "installer-reset" step
6. Do you have any specific timeline dependencies and which release would they like to target (i.e. Satellite 6.8,7)?
NA
7. List any affected packages or components.
NA
8. Would you be able to assist in testing this functionality if implemented?
Yes
Additional info: This is Related to bug - https://bugzilla.redhat.com/show_bug.cgi?id=2126686 . If "installer-reset" issue is not fixed then this
Bugzilla will not be helpful
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
1. Proposed title of this feature request. => [RFE] While Restoring satellite, satellite-maintain \ foreman-maintain should simply skip all initial checks and start from the installer-reset step 2. What are the nature and description of the request? A) Attempt 1 - Started restoration, due to some reason it fails. After Correcting it, goes for 2nd attempt B) Attempt 2 - satellite-maintain \ foreman-maintain checked the connectivity with DBs. This step has to be skipped because they are already dropped in first attempt to restore. After --whitelist="candlepin-db-up,foreman-db-up,pulpcore-db-up" goes for Third attempt Ended with Below Error ~~~~~~ The following steps ended up in failing state: [candlepin-db-up] [foreman-db-up] [pulpcore-db-up] ~~~~~~ C) Attempt 3 - satellite-maintain \ foreman-maintain stops at dropping database which is already dropped and end at "restore-installer-reset" state [ERROR ] [root] runuser -l postgres -c 'dropdb foreman' failed! Check the output for error! Reproducer: - Remove all CDN repos - Make sure that the following command fails 'dnf module enable pki-core --assumeyes' - Run satellite-maintain restore <backupdir> - Correct the CDN repos - Run satellite-maintain restore <backupdir> 3. Why do you need this? (List the business requirements here). satellite-maintain \ foreman-maintain should simply skip all initial checks and start from the "installer-reset" step 4. How would you like to achieve this? (List the functional requirements here). satellite-maintain \ foreman-maintain should simply skip all initial checks and start from the "installer-reset" step 5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. satellite-maintain \ foreman-maintain should not fail at already checked steps and start with "installer-reset" step 6. Do you have any specific timeline dependencies and which release would they like to target (i.e. Satellite 6.8,7)? NA 7. List any affected packages or components. NA 8. Would you be able to assist in testing this functionality if implemented? Yes Additional info: This is Related to bug - https://bugzilla.redhat.com/show_bug.cgi?id=2126686 . If "installer-reset" issue is not fixed then this Bugzilla will not be helpful