Another report from a customer with possible workaround: I have experimented with a possible workaround. It is kind of complicated, but I think it resolves their issue. First, I identified the rpms which create files in /home/nocpulse with: find /home/nocpulse -exec rpm -qf {} \; | sort | uniq and end up with: RPMS="ConfigPusher-general-1.2.0-3.rhel4 MessageQueue-3.26.0-3.rhel4 NOCpulsePlugins-2.208.0-27.rhel4 np-config-2.110.3-3.rhel4 perl-NOCpulse-Probe-1.183.1-18.rhel4 perl-NOCpulse-Scheduler-1.58.4-4.rhel4 ProgAGoGo-1.11.0-3.rhel4 SatConfig-bootstrap-1.11.0-5.rhel4 SatConfig-dbsynch-1.3.0-2.rhel4 SatConfig-installer-3.24.0-4.rhel4 SputLite-client-0.48.0-2.rhel4 ssl_bridge-1.9.0-3.rhel4 tsdb-1.27.13-13.rhel4" then, mounting the Satellite media and changing to the RPMS directory: * Disable monitoring # service rhn-satellite stop # useradd nocpulse # for RPM in $RPMS; do rpm -e --nodeps $RPM; rpm -Uhv ${RPM}.noarch.rpm; done # service rhn-satellite start * Enable monitoring # service rhn-satellite restart This was the only way I could think of freshening the contents of /home/nocpulse/* because a lot of the files are created with preinstall scripts. I can't find any other reference to UID 502 in the satellite code so I'm wondering if this is a reasonable workaround?
Taking from Mike's queue. Putting ? exception for 5.1.0. Not sure how hard it will be to QA it properly thou.
I checked in a fix that removes the -u 502 and built an RPM into the playpen-monitoring-3AS collection just to test. The RPM can be found here: http://vault.rhndev.redhat.com/repo/repository/NPusers/NPusers-1.17.11-5.noarch.rpm If you want the RPM in 510 just promote from playpen -> 510
Promoted: ./promote playpen-monitoring-3AS monitoring-5.1-4AS NPusers
Moving ON_QA, prompted by: Satellite 5.1.0-24 and Proxy 5.1.0-15 Content now available on webqa Channels. Satellite 5.1.0-24 ISOs are now available as rhn-satellite-5.1.0-24-redhat-linux-as-* @: http://barn.rhndev.redhat.com/satellite-isos/devel/satellite-5.1/
The release note might go like: The nocpulse user no longer requires UID 502 to be free.
Thanks, Jan, Here's a suggested note. Let me know if it's okay. An issue was fixed where the nocpulse user was not created if a user with the UID 502 already existed.
Yes, nice.
1. Before installing Satellite, create user with uid 502: adduser -u 502 test502 2. Run Satellite installation. 3. It should fail with 5.0.1 and should not fail with 5.1.0.
verified build 28 test502:x:502:502::/home/test502:/bin/bash apache:x:48:48:Apache:/var/www:/sbin/nologin nocpulse:x:503:503:NOCpulse user:/home/nocpulse:/bin/bash nocops:x:504:504:NOCpulse Ops:/home/nocops:/bin/bash jabberd:x:100:101:Jabber Daemon:/:/bin/false oracle:x:101:103:Oracle Server:/opt/apps/oracle:/bin/bash tomcat:x:91:91:Tomcat:/usr/share/tomcat5:/bin/sh
5.1 Sat GA so Closed for Current Release.