Bug 517279
Summary: | BIND post install scripts overwriting data, linking to itself | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Joni <urcentral> |
Component: | bind | Assignee: | Adam Tkac <atkac> |
Status: | CLOSED ERRATA | QA Contact: | qe-baseos-daemons |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 5.5 | CC: | azelinka, bugzilla-redhat, fnadge, ovasik, ralph |
Target Milestone: | rc | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Previously, the bind-chroot-admin script could break the configuration with non-standard chroot layout . With this update, the script terminates without touching the configuration.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2011-01-13 22:25:04 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
Joni
2009-08-13 11:13:12 UTC
Main reason why bind-chroot package exists is to simplify chroot environment maintenance. If you would like to use the bind-chroot you have to follow "standard practices" on Red Hat systems. Otherwise bind-chroot package is not a good idea for you because it will continuously break your configuration. Please read https://bugzilla.redhat.com/show_bug.cgi?id=480156#c4, I wrote there how such configuration should look like. If you would like to use customized chroot then please remove bind-chroot package. I'm closing this bug but if you think I'm not right please reopen it. *** This bug has been marked as a duplicate of bug 480156 *** I don't have a problem with 'standard practices' or recommended configurations, but the problem here is not that it simply breaks my configuration. We've been keeping zonefiles in the data directory ever since we ran BIND on Red Hat EL 2.1, it worked fine in 3.x, we run this live on CentOS 4.x. The problem did not exist till the 'simplified chroot environment maintenance' was implement in 5.x. If that is not a supported configuration, again, I don't have a problem with that, we can change the configuration. But an automated update script should never, in my humble opinion; * Delete customer data (zone files) * Create invalid symlinks Even a simple check to see if the 'data' directory is a symlink to its equivalent inside the chroot, followed by an exit would already prevent this from happening. 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: Previously, the bind-chroot-admin script could break the configuration with non-standard chroot layout . With this update, the script terminates without touching the configuration. => VERIFIED Reverified after rebase: https://tcms.engineering.redhat.com/run/14317/?from_plan=2749 for bind-9.3.6-15.P1.el5. 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-0032.html |