Description of problem: A common enterprise environment will have a centralised user identity service. Thus users and groups that the Spacewalk packages need may well already exist in the centralised auth database. Some Spacewalk packages do not take this schenario into account. How reproducible: Deterministic. Steps to Reproduce: 1. Install Spacewalk on a host that is configured to use a centralised authentication service where the oracle, apache, tomcat5, nocpulse, and nocops users and their groups already exist. 2. Run spacewalk-setup. Actual results: Error message like "The user 'apache' must be locally defined. Expected results: No error during package installation nor during spacewalk-setup. Additional info: This is related to Satellite bug 391771.
Commits e720a6ac7ebc50f28b74ff5d1a655eb127acec1c and 17d4875e2663c2b948ce061820c57a25aa1ac09c fix spacewalk-setup.
Commits 415f85c78228ed9491f36ca5bdb1d7341d7721a8 and 87734e82b8fc4cf2c0fe4087a2e780db65a6221f fix NPusers.
I'm pretty sure the code got to Spacewalk 0.3's packages, in one form or another (there were more changes to the code later on). Moving ON_QA.
Spacewalk has been released for some time.