Bug 150970
Summary: | Bind Upgrades Kills My Config | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Marc Perkel <marc> |
Component: | bind | Assignee: | Jason Vas Dias <jvdias> |
Status: | CLOSED WORKSFORME | QA Contact: | Ben Levenson <benl> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-03-18 16:24:48 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: |
Description
Marc Perkel
2005-03-13 04:06:55 UTC
All you need to do is uninstall the bind-chroot package - then bind-chroot would not be updated by a yum upgrade; only if bind-chroot is installed before the yum upgrade will it be updated. When bind-chroot is installed, it sets ROOTDIR in /etc/sysconfig/named to /var/named/chroot, and moves any BIND configuration files in /{etc,var/named} to $ROOTDIR/{etc,var/named} . Neither bind nor bind-chroot ever modify any pre-existing BIND configuration files. The caching-nameserver package does backup the BIND configuration files to .rpmsave files and replaces them with files for a Caching Only nameserver. If you want to maintain your own modified BIND configuration, backup your BIND configuration files and remove the caching-nameserver package. You say: "Evey time the automatic upgrades runs it shuts down my name servers": BIND, bind-chroot and caching-nameserver should always leave the server in the state it was in before upgrade; if named was running before upgrade, it should still be running after upgrade, with the same chkconfig level status . All bind upgrades must RESTART the servers, since new libraries / executables are being installed - but the state should be the same before as after the upgrade. If this fails for you - ie. if named was running before the upgrade and not afterwards - then please let me know - I've not been able to produce any problems of this sort during upgrade testing . It would be most helpful in this case if you could re-do the upgrade with the command: # rpm -Uvvv bind*.rpm 2>&1 | tee /tmp/bind-upgrade.log and append the log file to this bug. I am not able to reproduce this problem . In the absence of the further information requested, this bug is now being closed . |