Bug 1429656 - feature request for bind-chroot package file - allow arbitrary chroot dirs/files
Summary: feature request for bind-chroot package file - allow arbitrary chroot dirs/files
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: bind
Version: rawhide
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Petr Menšík
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1497646
TreeView+ depends on / blocked
 
Reported: 2017-03-06 19:18 UTC by unixstaff
Modified: 2018-07-18 18:31 UTC (History)
6 users (show)

Fixed In Version: bind-9.11.4-1.fc28
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-18 18:31:37 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description unixstaff 2017-03-06 19:18:08 UTC
Fedora docs said to come here for a feature request, so attempting...

setup-named-chroot.sh is a helper that gets called by systemd for chrooting named (as you know).  In it, ROOTDIR_MOUNT is hardcoded to a specific set of files, dirs.  This generally works fine, but doesn't allow for certain situations where other directories (samba libaries, i've heard?, but for us it's some files needed for our anycast bind configuration and run).

I'm requesting an enhancement to allow this list to come from an external source (say sysconfig/named or a sysconfig/named-chroot maybe).  This seems like a reasonable feature, if people have external-to-chroot stuff they can't put in a preset dir.  I've tried manually adding what we need to setup-named-chroot.sh, but of course every patch overwrites the file/change.  Putting this in sysconfig (or another solution) would prevent this from happening.

Could test for pre-existence and do default if not, or add on reference or something, or just allow ROOTDIR_MOUNT list in config.

Currently on RHEL7, "fc19/20", but this enhancement can be applied anywhere appropriate.  Listing under rawhide, as I assume this would be your logical choice?  (but for eventual RHEL8, I am biased to see it in an earlier fedora)

Thanks for your consideration.

Comment 1 unixstaff 2017-03-06 19:20:06 UTC
Apologies if this is not the appropriate method for requesting an enhancement.

Comment 2 Petr Menšík 2017-03-16 14:25:31 UTC
Hi,

I think this is correct way to request feature request. I fact I was thinking the same when doing a change for support of WKS records. It is easy to modify it on RHEL-6, because it is in /etc. But systemd named-chroot-setup.service calls shell script in /usr/libexec, which should not be modified.

The best place for additional files would be in /etc/sysconfig/named, but we wanted to get rid of that file in the future. I will look for best place or custom files list.

Comment 3 unixstaff 2017-03-16 16:59:20 UTC
Thanks for the info, Petr.  Out of curiosity, why get rid of /etc/sysconfig/named?  It seems like the perfect place to set OS side (non-named) type configurations for applications?

Anyway, thanks for the consideration!!

Comment 4 Fedora Update System 2018-07-15 22:03:07 UTC
dhcp-4.3.6-21.fc28 dnsperf-2.1.0.0-17.fc28 bind-dyndb-ldap-11.1-12.fc28 bind-9.11.4-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-be34943e96

Comment 5 Fedora Update System 2018-07-16 20:29:30 UTC
bind-9.11.4-1.fc28, bind-dyndb-ldap-11.1-12.fc28, dhcp-4.3.6-21.fc28, dnsperf-2.1.0.0-17.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-be34943e96

Comment 6 Fedora Update System 2018-07-18 18:31:37 UTC
bind-9.11.4-1.fc28, bind-dyndb-ldap-11.1-12.fc28, dhcp-4.3.6-21.fc28, dnsperf-2.1.0.0-17.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.