Bug 483802

Summary: Directory /etc/rhn owned by two packages, group does not match
Product: [Community] Spacewalk Reporter: Jan Pazdziora (Red Hat) <jpazdziora>
Component: ServerAssignee: Dave Parker <dparker>
Status: CLOSED CURRENTRELEASE QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: medium Docs Contact:
Priority: urgent    
Version: 0.4CC: JDavis4102, jesusr, msuchy, pkilambi, psklenar
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-09-17 07:09:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 456553    

Description Jan Pazdziora (Red Hat) 2009-02-03 17:48:27 UTC
Description of problem:

spacewalk/config/spacewalk-config.spec has

%defattr(0644,root,root,0755)
[...]
%dir /etc/rhn

backend/spacewalk-backend.spec has

%define rhnconf %{_sysconfdir}/rhn
[...]
%attr(750,root,apache) %dir %{rhnconf}

So depending on the order in which the packages are installed, the group of /etc/rhn can be either root or apache. The definitions should be the same. Ideally, only one package should probably own the directory.

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

spacewalk-config-0.5.1-1
spacewalk-backend-0.5.1-1

How reproducible:

Deterministic.

Steps to Reproduce:
1. Look at the .spec's.
  
Actual results:

Different definitions.

Expected results:

Definitions the same, or directory owned by one package only.

Additional info:

Comment 1 Dave Parker 2009-03-03 19:17:12 UTC
Made spacewalk-backend require spacewalk-config, removed dir ownership from spacewalk backend, changed mode & ownership in spacewalk-config to match what spacewalk-backend was doing (the latter appeared to win the depsolver war, and works on my spacewalk instance).

Comment 2 Miroslav Suchý 2009-03-11 10:16:36 UTC
Dave, your fix made conflict in proxy. Since proxy require spacewalk-backend and spacewalk-proxy-common and spacewalk-proxy-common provide /etc/rhn and /etc/rhn/rhn.conf.
I fixed it in commit 173c946197947e0f355c74078d02e734688d4623

Comment 3 Jesus M. Rodriguez 2009-04-14 14:12:42 UTC
Spacewalk 0.5 released.

Comment 4 Miroslav Suchý 2009-05-11 12:37:25 UTC
*** Bug 500142 has been marked as a duplicate of this bug. ***

Comment 5 Miroslav Suchý 2009-09-17 07:09:56 UTC
Spacewalk 0.5 has been released for long time ago.

Comment 6 Jan Pazdziora (Red Hat) 2010-09-08 09:17:12 UTC
Note to self -- Dave's commits were 9aa225a52c5d56b92f36ecfeb0201a04e273b075 and 835466a1fa00e2e328fb9adcaaa4df8f3602a7f9.

Comment 7 JDavis4102 2012-12-31 20:57:30 UTC
I am starting to see this issue in Spacewalk 1.8.

Comment 8 JDavis4102 2013-01-02 17:28:06 UTC
(In reply to comment #7)
> I am starting to see this issue in Spacewalk 1.8.

Please disregard. It was a configuration issue on my proxy server.