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.

Description of problem:

The bind-chroot package contains a couple of bugs.
1) It doesn't create the /dev/null device due to a spec file copy&paste error
2) When uninstalling it leaves some empty dirs behind as they aren't listed in the files section of the spec-file.

Version-Release number of selected component (if applicable):
bind-chroot-9.7.3-8.P3.el6_2.2

How reproducible:
install package / uninstall it again

Steps to Reproduce:
1. yum install bind-chroot
2. ls -la /var/named/chroot/dev/
3. yum erase bind-chroot
4. ls -la /var/named/chroot/
  

Additional info:

The '%post chroot' section of the bind spec-file contains the following bit:

  [ -e %{chroot_prefix}/dev/zero ] || \
    /bin/mknod %{chroot_prefix}/dev/null c 1 3

the check for /dev/zero is wrong and appears to be a copy&paste error, it should obviously be /dev/null.

The 'files chroot' section is missing the following lines:
%dir %{chroot_prefix}/etc/pki
%dir %{chroot_prefix}/usr
%dir %{chroot_prefix}/%{_libdir}

It should also create:

%{chroot_prefix}/var/named/data
%{chroot_prefix}/var/named/dynamic
%{chroot_prefix}/var/named/slaves

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0830.html