Hide Forgot
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.
To be clear, the upgrade removed the capsule DNS, DHCP, and TFTP settings I had when I installed the satellite. This wasn't expected.
Moving 6.2 bugs out to sat-backlog.
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.