This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2126686 - While Restoring satellite, foreman-installer failing on "installer-reset" operation when the databases are already dropped and not available
Summary: While Restoring satellite, foreman-installer failing on "installer-reset" ope...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.11.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-14 09:03 UTC by vivek singh
Modified: 2024-06-06 12:30 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 12:30:59 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-19279 0 None Migrated None 2024-06-06 12:30:58 UTC

Description vivek singh 2022-09-14 09:03:48 UTC 
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
Comment 3 Sayan Das 2022-09-15 09:56:58 UTC 
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
Comment 4 Eric Helms 2024-06-06 12:30:59 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.