Bug 105593
Summary: | bind-chroot is missing essential zone files | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Alexandre Oliva <oliva> |
Component: | caching-nameserver | Assignee: | Daniel Walsh <dwalsh> |
Status: | CLOSED ERRATA | QA Contact: | Ben Levenson <benl> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | chris.ricker, laroche, ted.belding |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-10-22 13:32:41 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 100643 |
Description
Alexandre Oliva
2003-09-25 21:25:53 UTC
I believe this is caused because the chroot environment was installed before the cacheing nameserver. Named does not include an /etc/named.conf file. So if you install bind, bind-chroot and then install cacheing nameserver the cacheing nameserver files will not be placed in the chroot environment. The bug should be that cacheing nameserver needs to check if bind is chroot and install to the chroot directory. Dan Converted cacheing nameserver to copy its files into the chroot directory if it exists. Fixed in caching-nameserver-7_2-8 Dan I tried removing the files from the chroot, then rpm -U caching-namesever-7.2-8.noarch.rpm, and the files were still missing from the chroot. I see that the code that should copy the conf files to $ROOTDIR is in place, but it definitely doesn't get run. The only piece I don't understand (being clueless in terms of rpm building) is: if [ $1 = 0 ]; this seems wrong for a %postinstall, that should have != 0. = 0 would be appropriate for post-uninstall, to clean up. Yes I didn't fully understand this either. After further experimentation this indicates how many times a package has been installed. So the first time it would be 1 not 0. It is only 0 on an uninstall. Fixed in caching-nameserver-7.2-9 *almost* there. There's a cut&pasto here: cp -f /var/named/named.localhost.zone $ROOTDIR/var/named It shoudl be /var/named/localhost.zone, not /var/named/named.localhost.zone. Fixed caching-nameserver-7.2-10 Confirmed, thanks. After doing a clean reinstall of bind-9.2.2.P3-9.i386.rpm, bind-chroot-9.2.2.P3-9.i386.rpm, bind-utils-9.2.2.P3-9.i386.rpm, redhat-config-bind-2.0.0-18.noarch.rpm, and caching-nameserver-7.2-10.noarch.rpm on a PC running Fedora Core 1, I find that named.conf, named.custom, and rndc.key are put in /etc, not /var/named/chroot/etc; and localhost.zone, named.ca, and named.local are put in /var/named, not /var/named/chroot/var/named (see below). Maybe this bug should be reopened? Thanks! [root@villiers root]# service named stop Stopping named: rndc: connect failed: connection refused [ OK ] [root@villiers root]# rm -rf /etc/named* [root@villiers root]# rm -rf /var/named/ [root@villiers root]# rpm -Uvh *.rpm --force Preparing... ########################################### [100%] 1:bind-utils ########################################### [ 20%] 2:bind ########################################### [ 40%] 3:bind-chroot ########################################### [ 60%] 4:caching-nameserver ########################################### [ 80%] 5:redhat-config-bind ########################################### [100%] [root@villiers root]# rpm -q bind bind-9.2.2.P3-9 [root@villiers root]# rpm -q bind-chroot bind-chroot-9.2.2.P3-9 [root@villiers root]# rpm -q bind-utils bind-utils-9.2.2.P3-9 [root@villiers root]# rpm -q redhat-config-bind redhat-config-bind-2.0.0-18 [root@villiers root]# rpm -q caching-nameserver caching-nameserver-7.2-10 [root@villiers root]# ls -l /etc/named* -rw-r--r-- 1 root root 762 Oct 22 09:21 /etc/named.conf -rw-r--r-- 1 root root 241 Oct 22 10:17 /etc/named.custom [root@villiers root]# ls -l /etc/rndc.* -rw-r----- 1 root named 1101 Oct 17 12:02 /etc/rndc.conf -rw-r----- 1 root named 132 Jan 6 02:31 /etc/rndc.key [root@villiers root]# ls -l /var/named total 20 drwxr-xr-x 5 root root 4096 Jan 11 22:36 chroot -rw-r--r-- 1 named named 195 Oct 22 09:21 localhost.zone -rw-r--r-- 1 named named 2499 Oct 22 09:21 named.ca -rw-r--r-- 1 named named 433 Oct 22 09:21 named.local drwxrwx--- 2 named named 4096 Oct 17 12:02 slaves [root@villiers root]# ls -l /var/named/chroot/etc/ total 0 -rwxr-x--- 1 root named 0 Mar 24 2003 named.conf -rw-r----- 1 root named 0 Mar 13 2003 rndc.key [root@villiers root]# ls -l /var/named/chroot/var/named/ total 0 [root@villiers root]# I too think that thsi si still a bug. I'm running: # rpm -qa|grep bind bind-9.2.2.P3-9 bind-chroot-9.2.2.P3-9 bind-utils-9.2.2.P3-9 ypbind-1.12-3 redhat-config-bind-2.0.0-18 I too was missing the essential .zone files from the /var/named/chroot/var/named/ directory. Additionally, my /var/named/chroot/etc/named.conf was 0 bytes. The chroot'd environment is incomplete and does not. Anyone else care to verify? Tweeks 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 the 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-2004-568.html |