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.
DescriptionBrad Buckingham
2016-06-08 14:28:48 UTC
Description of problem:
When upgrading a Satellite or an external Capsule from 6.1 to 6.2, there are several parameters that are not getting migrated from the old configuration [1] to the new configuration [2].
This includes parameters such as:
bmc
bmc_default_provider
dhcp
dhcp_listen_on
dhcp_option_domain
dhcp_managed
dhcp_interface
dhcp_gateway
dhcp_range
dhcp_nameservers
dhcp_vendor
dhcp_config
dhcp_leases
dhcp_key_name
dhcp_key_secret
dns
dns_managed
dns_provider
dns_zone
dns_reverse
dns_interface
dns_server
dns_ttl
dns_tsig_keytab
dns_tsig_principal
dns_forwarders
virsh_network
realm
realm_provider
realm_keytab
realm_principal
freeipa_remove_dns
register_in_foreman
Version-Release number of selected component (if applicable):
Satellite 6.2 SNAP 14
How reproducible:
Always
Steps to Reproduce:
1. Install Satellite 6.1 and Capsule 6.1
2. Ensure that the configuration has several foreman proxy services configured with non-default values (e.g. dns, dhcp, realm, bnc...)
3. Upgrade the Satellite to 6.2
4. Upgrade the Capsule to 6.2
Actual results:
Upgrade may fail; however, observe that the answers file generated for the upgraded environment does not indicated that the previous configuration was migrated.
See [2] for the new files.
Expected results:
The answers from should be migrated from [1] to [2] and used as part of the upgrade process.
Additional info:
[1] /etc/katello-installer/answers.katello-installer.yaml (internal capsule)
/etc/capsule-installer/answers.capsule-installer.yaml (external capsule)
[2] /etc/foreman-installer/scenarios.d/satellite-answers.yaml (internal capsule)
/etc/foreman-installer/scenarios.d/capsule-answers.yaml (external capsule)
As a workaround, if any of the fields noted in the original description are in use on either the Satellite internal capsule or external Capsule, the values can be provided as an input during the upgrade.
E.g. enabling bmc on an external capsule
satellite-installer --scenario capsule --upgrade --bmc true
To view the list of options available prior to upgrade execute:
satellite-installer --scenario satellite --help
satellite-installer --scenario capsule --help
Verified issue with upgrade from sat6.1.9 -> sat6.2 GA snap16 on rhel7:
Issue has been reolved for internal/default capsule. I can see upgrades are now migarating the capsule answers parameters. I can see dns/dhcp/bmc features enabled on default capsule after migration. Earlier they got disabled. I can see all param correctly populated under:
"/etc/foreman-installer/scenarios.d/satellite-answers.yaml"
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
Description of problem: When upgrading a Satellite or an external Capsule from 6.1 to 6.2, there are several parameters that are not getting migrated from the old configuration [1] to the new configuration [2]. This includes parameters such as: bmc bmc_default_provider dhcp dhcp_listen_on dhcp_option_domain dhcp_managed dhcp_interface dhcp_gateway dhcp_range dhcp_nameservers dhcp_vendor dhcp_config dhcp_leases dhcp_key_name dhcp_key_secret dns dns_managed dns_provider dns_zone dns_reverse dns_interface dns_server dns_ttl dns_tsig_keytab dns_tsig_principal dns_forwarders virsh_network realm realm_provider realm_keytab realm_principal freeipa_remove_dns register_in_foreman Version-Release number of selected component (if applicable): Satellite 6.2 SNAP 14 How reproducible: Always Steps to Reproduce: 1. Install Satellite 6.1 and Capsule 6.1 2. Ensure that the configuration has several foreman proxy services configured with non-default values (e.g. dns, dhcp, realm, bnc...) 3. Upgrade the Satellite to 6.2 4. Upgrade the Capsule to 6.2 Actual results: Upgrade may fail; however, observe that the answers file generated for the upgraded environment does not indicated that the previous configuration was migrated. See [2] for the new files. Expected results: The answers from should be migrated from [1] to [2] and used as part of the upgrade process. Additional info: [1] /etc/katello-installer/answers.katello-installer.yaml (internal capsule) /etc/capsule-installer/answers.capsule-installer.yaml (external capsule) [2] /etc/foreman-installer/scenarios.d/satellite-answers.yaml (internal capsule) /etc/foreman-installer/scenarios.d/capsule-answers.yaml (external capsule)