-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
6.6.0
-
0
-
False
-
-
False
-
CLOSED
-
850
-
Important
-
None
Description of problem:
----------------------
Enabling DNS proxy feature on Red Hat Satellite 6.6 is failing with the following errors which can be found in the "satellite.log" file -
[ERROR 2019-11-25T15:53:33 main] Errors encountered during run:
[ERROR 2019-11-25T15:53:33 main] Proxy fcn-sat-p001.fairconnect.internal has failed to load one or more features (DNS), check /var/log/foreman-proxy/proxy.log for configuration errors
[ERROR 2019-11-25T15:53:33 main] /usr/share/foreman-installer/modules/foreman/lib/puppet/provider/foreman_smartproxy/rest_v3.rb:70:in `validate_features!'
[ERROR 2019-11-25T15:53:33 main] /usr/share/foreman-installer/modules/foreman/lib/puppet/provider/foreman_smartproxy/rest_v3.rb:59:in `refresh_features!'
.....
[ERROR 2019-11-25T15:53:33 main] /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[fcn-sat-p001.fairconnect.internal]/features: change from ["Ansible", "Discovery", "Dynflow", "HTTPBoot", "Logs", "Openscap", "Pulp", "Puppet", "Puppet CA", "SSH", "TFTP", "Templates"] to ["Ansible", "DNS", "Discovery", "Dynflow", "HTTPBoot", "Logs", "Openscap", "Puppet", "Puppet CA", "TFTP", "Templates"] failed: Proxy fcn-sat-p001.fairconnect.internal has failed to load one or more features (DNS), check /var/log/foreman-proxy/proxy.log for configuration errors
[DEBUG 2019-11-25T15:53:33 main] Cleaning /tmp/kafo_puppet20191125-17450-kdmi0l.conf
[DEBUG 2019-11-25T15:53:33 main] Cleaning /tmp/kafo_hiera20191125-17450-s4v93c
Version-Release number of selected component (if applicable):
------------------------------------------------------------
Red Hat Satellite 6.6
How reproducible:
----------------
Probably easily
Steps to Reproduce:
------------------
1. The error is produced when the customer executes the following command on Red Hat Satellite 6.6 -
- satellite-installer --scenario satellite \
--foreman-initial-organization "UMB" \
--foreman-initial-location "DC" \
--foreman-initial-admin-username admin \
--foreman-initial-admin-password XXX \
--foreman-proxy-dns-managed=false \
--foreman-proxy-dhcp-managed=false \
--enable-foreman-compute-vmware
2. The customer then tried to configure the external DNS server by following the official document and the following command which fails as well -
- satellite-installer --foreman-proxy-dns=true \
--foreman-proxy-dns-managed=false \
--foreman-proxy-dns-provider=nsupdate \
--foreman-proxy-dns-server="10.20.1.31" \
--foreman-proxy-keyfile=/etc/rndc.key \
--foreman-proxy-dns-ttl=86400
This second command produces the error specified above.
Actual results:
--------------
The command fails with the following errors in "satellite.log" file -
[ERROR 2019-11-25T15:53:33 main] Errors encountered during run:
[ERROR 2019-11-25T15:53:33 main] Proxy fcn-sat-p001.fairconnect.internal has failed to load one or more features (DNS), check /var/log/foreman-proxy/proxy.log for configuration errors
[ERROR 2019-11-25T15:53:33 main] /usr/share/foreman-installer/modules/foreman/lib/puppet/provider/foreman_smartproxy/rest_v3.rb:70:in `validate_features!'
[ERROR 2019-11-25T15:53:33 main] /usr/share/foreman-installer/modules/foreman/lib/puppet/provider/foreman_smartproxy/rest_v3.rb:59:in `refresh_features!'
.....
[ERROR 2019-11-25T15:53:33 main] /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[fcn-sat-p001.fairconnect.internal]/features: change from ["Ansible", "Discovery", "Dynflow", "HTTPBoot", "Logs", "Openscap", "Pulp", "Puppet", "Puppet CA", "SSH", "TFTP", "Templates"] to ["Ansible", "DNS", "Discovery", "Dynflow", "HTTPBoot", "Logs", "Openscap", "Puppet", "Puppet CA", "TFTP", "Templates"] failed: Proxy fcn-sat-p001.fairconnect.internal has failed to load one or more features (DNS), check /var/log/foreman-proxy/proxy.log for configuration errors
[DEBUG 2019-11-25T15:53:33 main] Cleaning /tmp/kafo_puppet20191125-17450-kdmi0l.conf
[DEBUG 2019-11-25T15:53:33 main] Cleaning /tmp/kafo_hiera20191125-17450-s4v93c
Expected results:
----------------
The command should complete its execution successfully.
Additional info:
---------------
The customer has applied the following workaround to resolve the issue -
1. # chmod 644 /etc/rndc.key
2. # satellite-installer --foreman-proxy-dns=true --foreman-proxy-dns-server="XXX.XXX.XXX.XXX"
May be the permission with 640 and the group=named is not working as described in the following official document -
- external trackers