What were you trying to do that didn't work?

Use code that uses the RHEL supplied unbound library.

Code fails to initialise, as the Redhat supplied packaging compiles the path to the root key to a bogus path.

What is the impact of this issue to you?

Redwax-tool, which depends on unbound as packaged by Redhat, is broken out the box.

Please provide the package NVR for which the bug is seen:

How reproducible is this bug?:

Always

Steps to reproduce

1. Run code that depends on unbound-libs, for example redwax-tool
2.  
3.  

Expected results

Unbound library correctly picks up the root key at the correct path /etc/unbound/root.key.

Actual results

Unbound library attempts to pick up the root key in the non existent path /opt/local/etc/unbound/root.key.

The following is logged to stderr:

[1730293231] libunbound[1442264:0] error: error opening file /opt/local/etc/unbound/root.key: No such file or directory
[1730293231] libunbound[1442264:0] error: error reading trust-anchor-file: /opt/local/etc/unbound/root.key
[1730293231] libunbound[1442264:0] error: validator: error in trustanchors config
[1730293231] libunbound[1442264:0] error: validator: could not apply configuration settings.
[1730293231] libunbound[1442264:0] error: module init for module validator failed
Could not resolve '_25._tcp.example.com': initialization failure (No such file or directory)
 

To fix this, the Redhat supplied packaging must be updated to remove /opt/local from the root key path.