Bug 1394843 - No dhcp capsule feature available after upgrade to 7.3
Summary: No dhcp capsule feature available after upgrade to 7.3
Keywords:
Status: CLOSED DUPLICATE of bug 1156371
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: DHCP & DNS
Version: 6.2.3
Hardware: x86_64
OS: Linux
high
high vote
Target Milestone: Unspecified
Assignee: Lukas Zapletal
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-14 14:57 UTC by Mihir Lele
Modified: 2019-12-16 07:23 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-13 15:25:02 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Mihir Lele 2016-11-14 14:57:19 UTC
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

Comment 3 Ohad Levy 2016-11-15 21:36:19 UTC
does re-running the installer solves this issue?

Comment 4 Mihir Lele 2016-11-16 08:42:02 UTC
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

Comment 5 Lukas Zapletal 2016-11-23 10:28:43 UTC
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.

Comment 7 Lukas Zapletal 2016-11-28 13:53:30 UTC
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.

Comment 8 Stephen Benjamin 2016-12-13 15:25:02 UTC
Pretty sure this is a duplicate of BZ1156371

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


Note You need to log in before you can comment on or make changes to this bug.