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.
I've encountered several upgrade errors at customers or redhatters when
DHCP and/or DNS configuration simply disappears after Satellite upgrade.
When our users add or modify subnets or domains, our installer overwrite
the configuration with the initial one. Since our installer is limited
and only supports definition of one subnet/domain, all the others are
deleted and users need to restore those configurations from backups.
Purpose of this BZ:
Big warning comments in both /etc/zones.conf and /etc/dhcp/dhcpd.conf
files telling users that upgrade process will rewrite these files. I
think we already do this upstream. Unfortunately our upstream warning is
too short IMHO:
### File managed with puppet ###
I think we need to add extra information there for Satellite. In upstream, upgrade process never calls installer again, therefore this short notice is sufficient.
This bug is being tracked upstream, and will no longer be tracked in the downstream product. When the upstream issue is fixed, the next Satellite release will contain the fix. I am closing this out as deferred. If you feel this is not correct, please feel free to open with additional information.