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.
Bug 1473233 - bind/configuration: pid-file + session-keyfile doesn't work in chroot environment
Summary: bind/configuration: pid-file + session-keyfile doesn't work in chroot environ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: preupgrade-assistant-el6toel7
Version: 6.10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Petr Stodulka
QA Contact: Alois Mahdal
Jiri Hornicek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-20 09:34 UTC by Petr Sklenar
Modified: 2019-07-01 16:44 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
Manually created configuration might not work correctly with the *named-chroot* service after upgrading When you use the the *named-chroot* service and when you have your own manually created configuration files in the `/var/named/chroot/` directory, the service might not work properly on the target system after the upgrade to Red Hat Enterprise Linux 7. The `options` section in the used configuration files must contain the `session-keyfile` and `pid-file` directives, such as in the following example: session-keyfile "/run/named/session.key"; pid-file "/run/named/named.pid"; The *Preupgrade Assistant* modules do not check or fix the manually created files in the `/var/named/chroot/` directory. To work around this problem, manually insert the lines above to the `options` section. If you do not have your own manually created configuration files in `/var/named/chroot/`, the configuration files of *bind*, including the `/etc/named.conf` file, are used. These configuration files are checked and fixed by the *Preupgrade Assistant* modules.
Clone Of:
Environment:
Last Closed: 2019-07-01 16:44:31 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Petr Sklenar 2017-07-20 09:34:11 UTC 
Description of problem:

Bugfix for BZ#1456630  need more care

Version-Release number of selected component (if applicable):
preupgrade-assistant-el6toel7-0.6.68-1.el6

How reproducible:
always

Steps to Reproduce:
1. pid-file + session-keyfile doesn't work in chroot environment
2. set up named with chroot, all default
3. upgrade
4. start named-chroot service and see files

Actual results:
https://bugzilla.redhat.com/show_bug.cgi?id=1456630#c7

Expected results:
pid-file + session-keyfile works also with named-chroot

Additional info:
Comment 6 Petr Stodulka 2019-07-01 16:44:31 UTC 
Closing this bugzilla as the component is under a maintenance mode in which the maintainers are going to fix only critical bugs. If you consider the bugzilla critical, feel free to reopen the bug with an explanation.
Note You need to log in before you can comment on or make changes to this bug.