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