OSPCIX-683 - Fix unbound.service startup error

[hjensas]

Unbound fails to start, error message:

  unbound[1636]: [1636:0] fatal error: sd_notify failed
    /run/systemd/notify: No such file or directory.
    Make sure that unbound has access/permission to use
    the socket presented by systemd.

Adding chroot: "" in the server section of unbound.conf fixes the issue.

Jira: OSPCIX-683

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign lewisdenny for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[softwarefactory-project-zuul]

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/026b8522307e4fcca8df31e6206acaac

✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 49m 12s
✔️ podified-multinode-edpm-deployment-crc SUCCESS in 1h 18m 50s
❌ cifmw-crc-podified-edpm-baremetal FAILURE in 1h 32m 23s
✔️ noop SUCCESS in 0s
✔️ cifmw-pod-ansible-test SUCCESS in 8m 25s
✔️ cifmw-pod-k8s-snippets-source SUCCESS in 4m 30s
✔️ cifmw-pod-pre-commit SUCCESS in 7m 29s
✔️ cifmw-architecture-validate-hci SUCCESS in 5m 10s
✔️ build-push-container-cifmw-client SUCCESS in 23m 29s
❌ cifmw-molecule-ci_gen_kustomize_values FAILURE in 6m 49s
✔️ cifmw-molecule-nat64_appliance SUCCESS in 19m 53s

[hjensas]

/cherry-pick 18.0-fr1

[openshift-cherrypick-robot]

@hjensas: new pull request created: #2755

Details

In response to this:

/cherry-pick 18.0-fr1

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.