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 2081958 - chroot functionality isn't available in unbound-1.7.3 in RHEL8
Summary: chroot functionality isn't available in unbound-1.7.3 in RHEL8
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: unbound
Version: 8.5
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Petr Menšík
QA Contact: Petr Sklenar
URL:
Whiteboard:
Depends On: 2027735
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-05 05:26 UTC by Apurbita Mukherjee
Modified: 2022-11-08 10:52 UTC (History)
2 users (show)

Fixed In Version: unbound-1.16.0-1.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-08 09:51:08 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-121105 0 None None None 2022-05-05 05:32:34 UTC
Red Hat Product Errata RHSA-2022:7622 0 None None None 2022-11-08 09:51:26 UTC

Description Apurbita Mukherjee 2022-05-05 05:26:20 UTC 
Description of problem:
chroot functionality isn't available in unbound-1.7.3 in RHEL8

Version-Release number of selected component (if applicable):
unbound-1.7.3-17.el8

How reproducible:
Always

Steps to Reproduce:
1. Add chroot: "/etc/unbound" in configuration file /etc/unbound/unbound.conf
2. Receiving following error while running command /usr/sbin/unbound-checkconf
/etc/unbound/unbound.conf:835: error: syntax error
read /etc/unbound/unbound.conf failed: 1 errors in configuration file
3. unbound daemon not starting after enabling chroot option


Actual results:
# /usr/sbin/unbound-checkconf
/etc/unbound/unbound.conf:835: error: syntax error
read /etc/unbound/unbound.conf failed: 1 errors in configuration file

# journalctl logs of unbound:

example.com systemd[1]: Started Unbound recursive Domain Name Server.
example.com unbound[1101087]: [1101087:0] error: cannot open zonefile /etc/unbound/conf.d/corp.zone for corp.: No such file or directory
example.com unbound[1101087]: [1101087:0] fatal error: auth_zones could not be setup
example.com systemd[1]: unbound.service: Main process exited, code=exited, status=1/FAILURE
example.com systemd[1]: unbound.service: Failed with result 'exit-code'.


Expected results:
/usr/sbin/unbound-checkconf command output without any error and unbound daemon should be running fine.

Additional info:
Comment 2 Petr Menšík 2022-06-27 14:29:37 UTC 
The new version contains fixed upstream release. After rebase to recent version this issue should be fixed. But a test should be made to ensure we have chroot possibility working.

Unbound is better protected with SELinux enabled and enforced however. Chroot make sense only in cases, where SELinux cannot be used for any reason.
Comment 12 errata-xmlrpc 2022-11-08 09:51:08 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: unbound security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:7622
Note You need to log in before you can comment on or make changes to this bug.