Hide Forgot
Created attachment 1145240 [details] install.log Description of problem ====================== During anaconda installation, pegasus and cimsvr users and groups are not created properly. Version-Release number of selected component ============================================ 2:tog-pegasus-2.12.0-4.el6 How reproducible ================ Not sure; probably always Steps to Reproduce ================== 1. Schedule /CoreOS/sblim/Regression/bz974075-SAP-5-10-sblim-cmpi-base-wrong-UserModeTime-and using Beaker Actual results ============== Test fails due to missing `pegasus` user, which prevents to change credentials. (The service is still able to start up, though) Expected results ================ Test succeeds (or fails due to other reason, e.g. because it's broken, which is a known issue.) Additional info =============== Look into install.log (attached) shows a lot of errors: warning: group pegasus does not exist - using root /bin/chgrp: invalid group: `pegasus' warning: group pegasus does not exist - using root warning: group pegasus does not exist - using root warning: user cimsrvr does not exist - using root warning: group cimsrvr does not exist - using root warning: user cimsrvr does not exist - using root warning: group cimsrvr does not exist - using root (tog-pegasus-libs is installed first, then tog-pegasus in this case.) This was seen with last compose in Beaker - RHEL-6.8-20160407.0, on all archs. Other way I tried was yum installation on RHEL-6.8-20160330.0, which succeeded. For comparison, I have scheduled the same Beaker test with RHEL-6.8-20160330.0 (TJ#1295884).
Umm, the RHEL-6.8-20160330.0 compose suffers from this as well, but the RHEL6.7 GA compose, which was used for errata testing (the "official way" is last ga + erratum rpms, not full compose), did not have the issue; hence setting Regression kw. OTOH, the only commit in dist-git between rhel-6.8 and rhel-6.7 (ssl option) does not touch any related code. This looks like something else breaks our installation...
*** This bug has been marked as a duplicate of bug 1313794 ***