Bug 1498392

Summary:	capsule upgrade failed w/ : No answer file at /etc/foreman-installer/scenarios.d/capsule-answers.yaml found, can not continue
Product:	Red Hat Satellite	Reporter:	Sachin Ghai <sghai>
Component:	Upgrades	Assignee:	Eric Helms <ehelms>
Status:	CLOSED ERRATA	QA Contact:	Lukas Pramuk <lpramuk>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.3.0	CC:	bbuckingham, ehelms, inecas, lpramuk, mbacovsk
Target Milestone:	Unspecified	Keywords:	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:	2018-02-21 16:54:37 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:
Bug Depends On:
Bug Blocks:	1458642

Description Sachin Ghai 2017-10-04 08:17:24 UTC

Description of problem:
While performing capsule upgrade from 6.2.11 -> 6.3 snap18. capsule upgrade failed at :

run: satellite-installer --scenario capsule --upgrade --certs-tar /home/CAPSULE_SERVER.redhat.com-certs.tar
 out: No answer file at /etc/foreman-installer/scenarios.d/capsule-answers.yaml found, can not continue

I can see following files under  "/etc/foreman-installer/scenarios.d/". Please note that I can see satellite-answer file generated on Oct3 but not the capsule-answers.yaml


[root@qe-capsule-upgrade-rhel7 scenarios.d]# ll
total 84
-rw-------. 1 root root  979 Aug 24 10:54 capsule-answers.yaml.rpmnew
drwxr-xr-x. 2 root root 4096 Oct  3 17:20 capsule.migrations
-rw-------. 1 root root 1943 Oct  4 03:23 capsule.yaml
-rw-------. 1 root root  823 Aug 24 10:54 capsule.yaml.rpmnew
-rw-------. 1 root root 2096 Oct  3 17:20 foreman-answers.yaml
lrwxrwxrwx. 1 root root   54 Oct  3 17:20 foreman.migrations -> /usr/share/foreman-installer/config/foreman.migrations
-rw-r--r--. 1 root root 1335 Oct  3 17:20 foreman-migrations-applied
-rw-------. 1 root root 2987 Oct  3 17:20 foreman-proxy-content-answers.yaml
drwxr-xr-x. 2 root root 4096 Oct  3 17:20 foreman-proxy-content.migrations
-rw-------. 1 root root 2549 Oct  3 17:20 foreman-proxy-content.yaml
-rw-------. 1 root root  791 Oct  3 17:20 foreman.yaml
-rw-------. 1 root root 2331 Dec 27  2016 katello-answers.yaml
-rw-------. 1 root root 2771 Sep 29 03:51 katello-answers.yaml.rpmnew
drwxr-xr-x. 2 root root 4096 Oct  3 17:20 katello.migrations
-rw-------. 1 root root 5836 Oct  3 17:20 katello.yaml
-rw-------. 1 root root  894 Sep 29 03:51 katello.yaml.rpmnew
lrwxrwxrwx. 1 root root   61 Oct  3 17:20 last_scenario.yaml -> /etc/foreman-installer/scenarios.d/foreman-proxy-content.yaml
-rw-------. 1 root root 2896 Oct  3 17:20 satellite-answers.yaml
-rw-------. 1 root root 2626 Aug 24 10:54 satellite-answers.yaml.rpmnew
drwxr-xr-x. 2 root root 4096 Oct  3 17:20 satellite.migrations
-rw-------. 1 root root 1014 Oct  3 17:20 satellite.yaml
-rw-------. 1 root root  856 Aug 24 10:54 satellite.yaml.rpmnew



Version-Release number of selected component (if applicable):
6.2.11 -> 6.3 upgrade

How reproducible:


Steps to Reproduce:
1. satellite-installer --scenario capsule --upgrade --certs-tar /home/CAPSULE_SERVER.redhat.com-certs.tar
2.
3.

Actual results:
No answer file at /etc/foreman-installer/scenarios.d/capsule-answers.yaml found, can not continue

Expected results:


Additional info:

Comment 2 Sachin Ghai 2017-10-16 07:41:21 UTC

This can be verified as I don't see the reported issue w/ snap20 upgrade.

Comment 3 Lukas Pramuk 2017-10-16 13:42:19 UTC

VERIFIED.

@satellite-capsule-6.3.0-20.0.beta.el7sat.noarch

1. Upgrade capsule 6.2.12 to 6.3.0

# yum upgrade
...

# satellite-installer --upgrade
...
Upgrade completed!

>>> capsule upgrade finished successfully

Comment 5 Satellite Program 2018-02-21 16:54:37 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, 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/RHSA-2018:0336