Bug 1894044

Summary: Satellite restore gets failed for a specific customer database.
Product: Red Hat Satellite Reporter: Devendra Singh <desingh>
Component: Satellite CloneAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Vladimír Sedmík <vsedmik>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.8.0CC: pcreech
Target Milestone: 6.9.0Keywords: Regression, Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: satellite-clone-2.0.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-04-21 14:48:24 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:

Description Devendra Singh 2020-11-03 12:37:20 UTC
Description of problem: Satellite restore gets failed for a specific customer database. 

Version-Release number of selected component (if applicable):
6.7, Satellite-clone upstream master branch

How reproducible:
always

Steps to Reproduce:
1. Perform Satellite restore of a specific customer database.
2. Satellite-clone gets failed at the get candlepin password state.

{"changed": false, "msg": "Keys ['katello', 'candlepin_db_password'] were not found in etc/foreman-installer/scenarios.d/satellite-answers.yaml!"}

Actual results:
Satellite-restore gets failed at the candlepin password check state.

Expected results:
The problem should not come.

Additional info:

Comment 4 John Mitsch 2021-01-06 18:16:42 UTC
Fixed in upstream release satellite-clone-2.0.0

Comment 9 errata-xmlrpc 2021-04-21 14:48:24 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Satellite 6.9 Satellite Maintenance Release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:1312