Bug 165379

Summary: proxy installer is installing rhns before rhn-apache, causes warning
Product: [Retired] Red Hat Network Reporter: Beth Nackashi <bnackash>
Component: RHN/Rel-EngAssignee: Mihai Ibanescu <mihai.ibanescu>
Status: CLOSED CURRENTRELEASE QA Contact: Beth Nackashi <bnackash>
Severity: medium Docs Contact:
Priority: medium    
Version: rhn400CC: rhn-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: rhn401 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-10-12 16:48:33 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: 168311    
Attachments:
Description Flags
proxy installation rhn_check -vvv output none

Description Beth Nackashi 2005-08-08 18:17:23 UTC 
Description of problem:
Proxy installer is installing rhns before rhn-apache.  This causes a warning to
be output to stdout because rhns requires the apache group that rhn-apache creates.

Version-Release number of selected component (if applicable):
up2date-4.4.36-3
rhel 3 u5 AS
i686

How reproducible:
always

Steps to Reproduce:
1.  install a proxy on RHEL 3 U5 AS or RHEL 4 U1 AS box using up2date-4.4.36-x
2. 
3.
  
Actual results:
1. "warning: group apache does not exist - using root" when preparing to install
rhns
2.  rhns is installed with group root
3.  rhn-apache is installed after rhns

Expected results:
1.  rhn-apache is installed before rhns
2.  rhns can successfully be installed with group apache

Additional info:
This will need to be cloned for rhel 4 U2 up2date as well.
Comment 1 Beth Nackashi 2005-08-08 18:17:23 UTC 
Created attachment 117551 [details]
proxy installation rhn_check -vvv output
Comment 2 Adrian Likins 2005-08-08 18:22:48 UTC 
If anything, this is either a packaging bug, or an rpm bug, since the transaction
ordering is all done by librpm based on the package info. up2date doesn't
influence the package transaction ordering.
Comment 3 Todd Warner 2005-08-08 18:28:36 UTC 
I think this is a jconnor bug... punting to him. This may be a misa bug.

Also... that "warning" is misleading. The code really *has* to be installed with
the apache group permissions. It's a warning according to RPM, but not to our
app-stack.
Comment 4 Adrian Likins 2005-08-08 18:34:29 UTC 
when did this start happening?
what are the versions of rhns/rhn-apache/httpd/etc involved and where can I find
them?

what version of rpm?
Comment 5 Adrian Likins 2005-08-08 18:42:58 UTC 
A quick glance at rhns-4.0.0-165.rhel4 doesn't show any requires on rhn-apache:

[root@test07 ~]# rpm -q --requires rhns
config(rhns) = 4.0.0-165.rhel4
python
rhnlib >= 1.8
rpm-python
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1


There doesn't seem to be anything in the packages to enfore an ordering, so this
looks to be a packaging bug.
Comment 6 Mihai Ibanescu 2005-08-09 20:19:21 UTC 
SHould be fixed in rhns-4.0.0-173 and newer.
Comment 8 Beth Nackashi 2005-09-27 23:10:56 UTC 
ok, well ... it seems to be working now anyway.  

[root@test07 log]# rpm -q rhns
rhns-4.0.0-185.rhel3
[root@test07 log]# rpm -q up2date
up2date-4.4.44-3
Comment 10 Beth Nackashi 2005-10-11 23:42:13 UTC 
reverified with 
[root@test07 ~]# rpm -q rhns
rhns-4.0.0-186.rhel4
[root@test07 ~]# rpm -q up2date
up2date-4.4.50-4
Comment 11 Beth Nackashi 2005-10-12 16:48:33 UTC 
verified these packages exist in prod:
rhns-4.0.0-186.rhel4
up2date-4.4.50-4

moving to CLOSED.