Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Prior to this update, the shadow-utils package was not listed among the package dependencies for Bacula. As a result, the bacula user and bacula group were not created when the shadow-utils package was not present on the system, and a warning message was displayed during the bacula packages installation. This bug has been fixed by adding shadow-utils to the package dependencies.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Cause
- shadow-utils wasn't listed in package dependencies
Consequence
- bacula user and group hasn't been created when shadow-utils package wasn't installed
Fix
- added shadow-utils to dependencies
Result
- user and group are created, no warning message on installation
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1,8 +1 @@
-Cause
+Prior to this update, the shadow-utils package was not listed among the package dependencies for Bacula. As a result, the bacula user and bacula group were not created when the shadow-utils package was not present on the system, and a warning message was displayed during the bacula packages installation. This bug has been fixed by adding shadow-utils to the package dependencies.-- shadow-utils wasn't listed in package dependencies
-Consequence
-- bacula user and group hasn't been created when shadow-utils package wasn't installed
-Fix
-- added shadow-utils to dependencies
-Result
-- user and group are created, no warning message on installation
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-1232.html
Description of problem: bacula-common runs '/usr/sbin/groupadd' and '/usr/sbin/useradd' in its installation scriplets, but the package doesn't depend on shadow-utils: [root@rtt5 rpms]# rpm --nogpg -q --scripts -p bacula-common-5.0.0-7.el6.s390x.rpm preinstall scriptlet (using /bin/sh): /usr/sbin/groupadd -g 133 -r bacula &>/dev/null || : /usr/sbin/useradd -u 133 -r -s /sbin/nologin -d /var/spool/bacula -M \ -c 'Bacula Backup System' -g bacula bacula &>/dev/null || : postuninstall scriptlet (using /bin/sh): #Dropped due to Guidelines #test "$1" != 0 || /usr/sbin/userdel bacula &>/dev/null || : #test "$1" != 0 || /usr/sbin/groupdel bacula &>/dev/null || : [root@rtt5 rpms]# rpm -qf /usr/sbin/groupadd shadow-utils-4.1.4.2-9.el6.s390x [root@rtt5 rpms]# rpm --nogpg -q --requires -p bacula-common-5.0.0-7.el6.s390x.rpm | grep shadow-utils [root@rtt5 rpms]# It causes warning messages in some cases: ... Installing : ca-certificates-2010.63-3.el6.noarch 36/38 Installing : openssl-1.0.0-10.el6.s390x 37/38 Installing : bacula-common-5.0.0-7.el6.s390x 38/38 warning: user bacula does not exist - using root warning: group bacula does not exist - using root warning: user bacula does not exist - using root warning: group bacula does not exist - using root Version-Release number of selected component (if applicable): bacula-common-5.0.0-7.el6 How reproducible: always Steps to Reproduce: 1. yum --installroot=/root/new_install_root install bacula-common Actual results: warning messages during installation Expected results: bacula-common depends on shadow-utils, no warning messages during installation