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