Bug 2126686
| Summary: | While Restoring satellite, foreman-installer failing on "installer-reset" operation when the databases are already dropped and not available | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | vivek singh <vivsingh> |
| Component: | Installation | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED MIGRATED | QA Contact: | Satellite QE Team <sat-qe-bz-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.11.2 | CC: | ehelms, peter.vreman, saydas |
| Target Milestone: | Unspecified | Keywords: | MigratedToJIRA, Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2024-06-06 12:30:59 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Workaroud: # satellite-installer ## this will initialize empty databases Restore: # satellite-maintain restore --whitelist="candlepin-db-up,foreman-db-up,pulpcore-db-up" /PATH/TO/BACKUP/DIR 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, foreman-installer failing on "installer-reset" operation when the databases are already dropped and not available 2. What are the nature and description of the request? While Restoring satellite, foreman-installer failing on "installer-reset" operation when the databases are already dropped and not available If the "installer-reset" step is re-executed, then it will again try to drop the databases and will fail to say: ~~ dropdb: error: database removal failed: ERROR: database "XXXX" does not exist ~~ 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). If databases are already dropped, then "installer-reset" should not give ERROR while checking DB. Instead of this it should give WARNING and move forward 4. How would you like to achieve this? (List the functional requirements here). While Restoring satellite , the "installer-reset" step should give WARNING for dropped DBs instead of ERROR and FAIL and move forward 5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. While Restoring satellite , the "installer-reset" step should give WARNING for dropped DBs instead of ERROR and FAIL and move forward 6. Do you have any specific timeline dependencies and which release would they like to target (i.e. Satellite 6.11.3,12)? NA 7. List any affected packages or components. NA 8. Would you be able to assist in testing this functionality if implemented? Yes Actual results: "installer-reset" step Fails on already dropped DB check and stop on ERROR Expected results: "installer-reset" step should give WARNING for dropped DBs instead of ERROR and FAIL and move forward