Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionMartin Bacovsky
2016-06-07 11:02:22 UTC
Description of problem:
Kafo does not reload updated scenario before running migrations. This is a problem when legacy config was migrated to scenario and installer wants to apply the migrations in one run.
Version-Release number of selected component (if applicable):
Snap 14.1
How reproducible:
Always
Steps to Reproduce:
1. Have customized installer config for e.g capsule
2. Upgrade to scenario based installer
3.
Actual results:
Answers file do not contain customized values
Expected results:
Answers file do contain customized values
Additional info:
The migration of legacy config is performed but the result is dropped.
Verified with upgrade from sat6.1.9 -> sat6.2 GA snap16 on rhel7:
I can see answer file contains customized configuration/parameters. I checked for default capsule:
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