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.
Bug 1313897 - Upgrading from 6.1.6 to 6.1.7 removed capsule options
Summary: Upgrading from 6.1.6 to 6.1.7 removed capsule options
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Upgrades
Version: 6.1.7
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-02 15:08 UTC by Rob Marti
Modified: 2019-09-26 13:57 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-11 13:07:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Rob Marti 2016-03-02 15:08:09 UTC 
Description of problem:
I had a Satellite at 6.1.6.  I had deployed multiple servers from this Satellite.
I upgraded to 6.1.7 by running yum update and then katello-installer upgrade.

Post upgrade when I went to Infrastructure -> Subnets -> click subnet -> Capsules -> the only options for DNS, DHCP, and TFTP were "None".  Prior to the upgrade they were all populated.

I ran

katello-installer -v -d --capsule-dns true --capsule-dns-interface eth0 --capsule-dns-zone $DOMAIN \  
--capsule-dns-forwarders 192.168.126.1 --capsule-dns-reverse 126.168.192.in-addr.arpa \  
--capsule-dhcp true --capsule-dhcp-interface eth0 --capsule-dhcp-range "192.168.126.100 192.168.126.150" \  
--capsule-dhcp-gateway 192.168.126.1 --capsule-dhcp-nameservers 192.168.126.2 \  
--capsule-tftp true --capsule-tftp-servername $(hostname)

and now the drop downs are populated with the correct information.

Version-Release number of selected component (if applicable):
Upgrading from 6.1.6 to 6.1.7

How reproducible:
Unsure - I didn't keep a snapshot if the VM to replicate

Steps to Reproduce:
1. Have a Satellite 6.1.6
2. Run yum update and katello-installer upgrade
3. Note that provisioning that depends on DHCP fails

Actual results:
Failure to provision if you rely on DHCP

Expected results:
Settings persist across upgrades

Additional info:
Let me know what logs would be useful to look at and I will upload them.
Comment 1 Rob Marti 2016-03-02 15:15:16 UTC 
To be clear, the upgrade removed the capsule DNS, DHCP, and TFTP settings I had when I installed the satellite.  This wasn't expected.
Comment 2 Bryan Kearney 2016-07-26 19:02:48 UTC 
Moving 6.2 bugs out to sat-backlog.
Comment 4 jcallaha 2017-05-11 13:07:36 UTC 
We are no longer seeing this in either 6.2->6.2.z upgrades or 6.1.11->6.2.9 upgrades. Closing this bug as a result.
Note You need to log in before you can comment on or make changes to this bug.