Bug 2126696

Summary: While Restoring satellite, satellite-maintain \ foreman-maintain should simply skip all initial checks and start from the installer-reset step
Product: Red Hat Satellite Reporter: vivek singh <vivsingh>
Component: Foreman MaintainAssignee: satellite6-bugs <satellite6-bugs>
Status: NEW --- QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.11.2CC: aupadhye, ehelms, peter.vreman, saydas
Target Milestone: UnspecifiedKeywords: 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: 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:

Description vivek singh 2022-09-14 09:31:17 UTC
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

Comment 2 Sayan Das 2022-09-15 09:56:49 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