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.

Description of problem:

No dhcp capsule feature available after upgrade to 7.3

Version-Release number of selected component (if applicable): 6.2.3


How reproducible:

Always reproducible

Steps to Reproduce:
1. Upgrade the Satellite 6.2 from rhel 7.2 to 7.3
 
Actual results:

dhcp is not listed as a capsule feature.

Expected results:

dhcp feature should be enabled 

Additional info:

This issue is caused, because the permissions of /etc/dhcp folder gets changed from 755 to 750 after upgrading to rhel 7.3

does re-running the installer solves this issue?

Hello Ohad,

After changing permissions to 755 for /etc/dhcp, I ran the satellite-installer again with dhcp as true, and the dhcp feature re-eappeared after doing a refresh feature. 

Br. Mihir

Sorry for the delay, I can confirm, we set some file permissions that are replaced by RPM package during upgrade.

I wonder if extender attributes or hardlink could help here.

I think the best way to handle this (until we figure out how to properly do this in Puppet) is to error out during proxy initialization completely (rather than disabling a module). If you agree, let's change this bug accordingly.

I also think that putting this into Sat docs won't help much - this happens during regular system update rather than when doing Satellite upgrade or maintenance. Users won't be simply reading this when this happens usually.

Pretty sure this is a duplicate of BZ1156371

*** This bug has been marked as a duplicate of bug 1156371 ***