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.

Description of problem:

In Satellite 6.1, the capsule configuration could be located in one of 2 places depending on the deployment scenario:

1. /etc/katello-installer - for storing the 'internal' capsule configuration
2. /etc/capsule-installer - for storing the 'external' capsule configuration

In Satellite 6.2, as part of the upgrade, the legacy configuration needs to be migrated to the new scenario-based configuration.  In order to do this, it needs to be able to support pulling from either of these locations depending on whether it is a Satellite (satellite or katello) or Capsule.

Version-Release number of selected component (if applicable):

Satellite 6.2  SNAP 14.1

How reproducible:

Always

Additional Notes:

From a QA perspective, testing the upgrade of 6.1 to 6.2 Satellite & Capsule should be sufficient.  The key is to ensure that the answers from the legacy configuration above (1. & 2.) are migrated to the new location (/etc/foreman-installer/scenarios.d).

BZ#1343438 and BZ#1343084 are not related and are not blocking each other. But we need both fixed for successful capsule upgrade.

Verified!

@ Sat 6.2 Snap 17

The satellite and capsule are successfully upgraded. Also the configuration files for satellite and capsule are listed under /etc/foreman-installer/scenarios.d/
 
So moving this bug to verified as per steps/comment/note for QE mentioned in Description.

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/RHBA-2016:1501