foreman_proxy::plugin::salt on debian-11-x86_64 with default settings should configure master.d/foreman.conf Failure/Error: should contain_file('/etc/salt/master.d/foreman.conf'). with_content(%r{autosign_grains_dir: /var/lib/foreman-proxy/salt/grains}). with_content(%r{autosign_file: /etc/salt/autosign.conf}). with_content(%r{user: root}). with_content(%r{netapi_enable_clients:\n - runner}). with_content(%r{external_auth:\n - pam\n - saltuser\n - \'@runner\'}) expected that the catalogue would contain File[/etc/salt/master.d/foreman.conf] with content set to /external_auth:\n - pam\n - saltuser\n - \'@runner\'/ but it is set to "# /etc/salt/master.d/foreman.config Master configuration\n#\n# This file summarizes configurations for the salt-master.\n# Have a look at the [Foreman Salt Plugin Documentation](https://theforeman.org/plugins/foreman_salt/) for detailed explanations.\n#\n# After editing this file, run the following command to active the changes:\n# systemctl restart salt-master\n\n\n##\n# Autosign\nautosign_grains_dir: /var/lib/foreman-proxy/salt/grains\nautosign_file: /etc/salt/autosign.conf\n# Uncomment the next line to make use of the autosign host name file (not recommended)\n# permissive_pki_access: True\n\n\n##\n# Salt Master service user\nuser: root\n\n\n##\n# Node classifier\nmaster_tops:\n ext_nodes: /usr/bin/foreman-node\n\n\n##\n# Pillar data access\next_pillar:\n - puppet: /usr/bin/foreman-node\n\n\n##\n# Salt API access\nexternal_auth:\n pam:\n saltuser:\n - '@runner'\n\nrest_cherrypy:\n port: 9191\n ssl_key: /etc/puppetlabs/puppet/ssl/private_keys/foo.example.com.pem\n ssl_crt: /etc/puppetlabs/puppet/ssl/certs/foo.example.com.pem\n\nnetapi_enable_clients:\n - runner\n\n\n##\n# Remote execution provider\npublisher_acl:\n foreman-proxy:\n - state.template_str\n\n\n##\n# Reactors\nreactor:\n - 'salt/auth': # Autosign reactor\n - /usr/share/foreman-proxy/salt/reactors/foreman_minion_auth.sls\n - 'salt/job/*/ret/*': # Report reactor\n - /usr/share/foreman-proxy/salt/reactors/foreman_report_upload.sls\n" Diff: @@ -1,64 +1,127 @@ -(?-mix:external_auth:\n - pam\n - saltuser\n - \'@runner\') +# /etc/salt/master.d/foreman.config Master configuration +# +# This file summarizes configurations for the salt-master. +# Have a look at the [Foreman Salt Plugin Documentation](https://theforeman.org/plugins/foreman_salt/) for detailed explanations. +# +# After editing this file, run the following command to active the changes: +# systemctl restart salt-master + + +## +# Autosign +autosign_grains_dir: /var/lib/foreman-proxy/salt/grains +autosign_file: /etc/salt/autosign.conf +# Uncomment the next line to make use of the autosign host name file (not recommended) +# permissive_pki_access: True + + +## +# Salt Master service user +user: root + + +## +# Node classifier +master_tops: + ext_nodes: /usr/bin/foreman-node + + +## +# Pillar data access +ext_pillar: + - puppet: /usr/bin/foreman-node + + +## +# Salt API access +external_auth: + pam: + saltuser: + - '@runner' + +rest_cherrypy: + port: 9191 + ssl_key: /etc/puppetlabs/puppet/ssl/private_keys/foo.example.com.pem + ssl_crt: /etc/puppetlabs/puppet/ssl/certs/foo.example.com.pem + +netapi_enable_clients: + - runner + + +## +# Remote execution provider +publisher_acl: + foreman-proxy: + - state.template_str + + +## +# Reactors +reactor: + - 'salt/auth': # Autosign reactor + - /usr/share/foreman-proxy/salt/reactors/foreman_minion_auth.sls + - 'salt/job/*/ret/*': # Report reactor + - /usr/share/foreman-proxy/salt/reactors/foreman_report_upload.sls

foreman_proxy::plugin::salt on debian-11-x86_64 with overwritten parameters should change master.d/foreman.conf parameters Failure/Error: should contain_file('/etc/salt/master.d/foreman.conf'). with_content(%r{user: example}). with_content(%r{autosign_grains_dir: /var/lib/foreman-proxy/salt/grains}). with_content(%r{autosign_file: /etc/salt/example.conf}). with_content(%r{netapi_enable_clients:\n - runner\n - local\n - ssh\n - wheel}). with_content(%r{external_auth:\n - ldap\n - saltuser\n - \'@runner\'}) expected that the catalogue would contain File[/etc/salt/master.d/foreman.conf] with content set to /external_auth:\n - ldap\n - saltuser\n - \'@runner\'/ but it is set to "# /etc/salt/master.d/foreman.config Master configuration\n#\n# This file summarizes configurations for the salt-master.\n# Have a look at the [Foreman Salt Plugin Documentation](https://theforeman.org/plugins/foreman_salt/) for detailed explanations.\n#\n# After editing this file, run the following command to active the changes:\n# systemctl restart salt-master\n\n\n##\n# Autosign\nautosign_grains_dir: /var/lib/foreman-proxy/salt/grains\nautosign_file: /etc/salt/example.conf\n# Uncomment the next line to make use of the autosign host name file (not recommended)\n# permissive_pki_access: True\n\n\n##\n# Salt Master service user\nuser: example\n\n\n##\n# Node classifier\nmaster_tops:\n ext_nodes: /usr/bin/foreman-node\n\n\n##\n# Pillar data access\next_pillar:\n - puppet: /usr/bin/foreman-node\n\n\n##\n# Salt API access\nexternal_auth:\n ldap:\n saltapi:\n - '@runner'\n\nrest_cherrypy:\n port: 9191\n ssl_key: /etc/puppetlabs/puppet/ssl/private_keys/foo.example.com.pem\n ssl_crt: /etc/puppetlabs/puppet/ssl/certs/foo.example.com.pem\n\nnetapi_enable_clients:\n - runner\n - local\n - ssh\n - wheel\n\n\n##\n# Remote execution provider\npublisher_acl:\n foreman-proxy:\n - state.template_str\n\n\n##\n# Reactors\nreactor:\n - 'salt/auth': # Autosign reactor\n - /usr/share/foreman-proxy/salt/reactors/foreman_minion_auth.sls\n - 'salt/job/*/ret/*': # Report reactor\n - /usr/share/foreman-proxy/salt/reactors/foreman_report_upload.sls\n" Diff: @@ -1,67 +1,133 @@ -(?-mix:external_auth:\n - ldap\n - saltuser\n - \'@runner\') +# /etc/salt/master.d/foreman.config Master configuration +# +# This file summarizes configurations for the salt-master. +# Have a look at the [Foreman Salt Plugin Documentation](https://theforeman.org/plugins/foreman_salt/) for detailed explanations. +# +# After editing this file, run the following command to active the changes: +# systemctl restart salt-master + + +## +# Autosign +autosign_grains_dir: /var/lib/foreman-proxy/salt/grains +autosign_file: /etc/salt/example.conf +# Uncomment the next line to make use of the autosign host name file (not recommended) +# permissive_pki_access: True + + +## +# Salt Master service user +user: example + + +## +# Node classifier +master_tops: + ext_nodes: /usr/bin/foreman-node + + +## +# Pillar data access +ext_pillar: + - puppet: /usr/bin/foreman-node + + +## +# Salt API access +external_auth: + ldap: + saltapi: + - '@runner' + +rest_cherrypy: + port: 9191 + ssl_key: /etc/puppetlabs/puppet/ssl/private_keys/foo.example.com.pem + ssl_crt: /etc/puppetlabs/puppet/ssl/certs/foo.example.com.pem + +netapi_enable_clients: + - runner + - local + - ssh + - wheel + + +## +# Remote execution provider +publisher_acl: + foreman-proxy: + - state.template_str + + +## +# Reactors +reactor: + - 'salt/auth': # Autosign reactor + - /usr/share/foreman-proxy/salt/reactors/foreman_minion_auth.sls + - 'salt/job/*/ret/*': # Report reactor + - /usr/share/foreman-proxy/salt/reactors/foreman_report_upload.sls

foreman_proxy::plugin::salt on redhat-8-x86_64 with default settings should configure master.d/foreman.conf Failure/Error: should contain_file('/etc/salt/master.d/foreman.conf'). with_content(%r{autosign_grains_dir: /var/lib/foreman-proxy/salt/grains}). with_content(%r{autosign_file: /etc/salt/autosign.conf}). with_content(%r{user: root}). with_content(%r{netapi_enable_clients:\n - runner}). with_content(%r{external_auth:\n - pam\n - saltuser\n - \'@runner\'}) expected that the catalogue would contain File[/etc/salt/master.d/foreman.conf] with content set to /external_auth:\n - pam\n - saltuser\n - \'@runner\'/ but it is set to "# /etc/salt/master.d/foreman.config Master configuration\n#\n# This file summarizes configurations for the salt-master.\n# Have a look at the [Foreman Salt Plugin Documentation](https://theforeman.org/plugins/foreman_salt/) for detailed explanations.\n#\n# After editing this file, run the following command to active the changes:\n# systemctl restart salt-master\n\n\n##\n# Autosign\nautosign_grains_dir: /var/lib/foreman-proxy/salt/grains\nautosign_file: /etc/salt/autosign.conf\n# Uncomment the next line to make use of the autosign host name file (not recommended)\n# permissive_pki_access: True\n\n\n##\n# Salt Master service user\nuser: root\n\n\n##\n# Node classifier\nmaster_tops:\n ext_nodes: /usr/bin/foreman-node\n\n\n##\n# Pillar data access\next_pillar:\n - puppet: /usr/bin/foreman-node\n\n\n##\n# Salt API access\nexternal_auth:\n pam:\n saltuser:\n - '@runner'\n\nrest_cherrypy:\n port: 9191\n ssl_key: /etc/puppetlabs/puppet/ssl/private_keys/foo.example.com.pem\n ssl_crt: /etc/puppetlabs/puppet/ssl/certs/foo.example.com.pem\n\nnetapi_enable_clients:\n - runner\n\n\n##\n# Remote execution provider\npublisher_acl:\n foreman-proxy:\n - state.template_str\n\n\n##\n# Reactors\nreactor:\n - 'salt/auth': # Autosign reactor\n - /usr/share/foreman-proxy/salt/reactors/foreman_minion_auth.sls\n - 'salt/job/*/ret/*': # Report reactor\n - /usr/share/foreman-proxy/salt/reactors/foreman_report_upload.sls\n" Diff: @@ -1,64 +1,127 @@ -(?-mix:external_auth:\n - pam\n - saltuser\n - \'@runner\') +# /etc/salt/master.d/foreman.config Master configuration +# +# This file summarizes configurations for the salt-master. +# Have a look at the [Foreman Salt Plugin Documentation](https://theforeman.org/plugins/foreman_salt/) for detailed explanations. +# +# After editing this file, run the following command to active the changes: +# systemctl restart salt-master + + +## +# Autosign +autosign_grains_dir: /var/lib/foreman-proxy/salt/grains +autosign_file: /etc/salt/autosign.conf +# Uncomment the next line to make use of the autosign host name file (not recommended) +# permissive_pki_access: True + + +## +# Salt Master service user +user: root + + +## +# Node classifier +master_tops: + ext_nodes: /usr/bin/foreman-node + + +## +# Pillar data access +ext_pillar: + - puppet: /usr/bin/foreman-node + + +## +# Salt API access +external_auth: + pam: + saltuser: + - '@runner' + +rest_cherrypy: + port: 9191 + ssl_key: /etc/puppetlabs/puppet/ssl/private_keys/foo.example.com.pem + ssl_crt: /etc/puppetlabs/puppet/ssl/certs/foo.example.com.pem + +netapi_enable_clients: + - runner + + +## +# Remote execution provider +publisher_acl: + foreman-proxy: + - state.template_str + + +## +# Reactors +reactor: + - 'salt/auth': # Autosign reactor + - /usr/share/foreman-proxy/salt/reactors/foreman_minion_auth.sls + - 'salt/job/*/ret/*': # Report reactor + - /usr/share/foreman-proxy/salt/reactors/foreman_report_upload.sls

foreman_proxy::plugin::salt on redhat-8-x86_64 with overwritten parameters should change master.d/foreman.conf parameters Failure/Error: should contain_file('/etc/salt/master.d/foreman.conf'). with_content(%r{user: example}). with_content(%r{autosign_grains_dir: /var/lib/foreman-proxy/salt/grains}). with_content(%r{autosign_file: /etc/salt/example.conf}). with_content(%r{netapi_enable_clients:\n - runner\n - local\n - ssh\n - wheel}). with_content(%r{external_auth:\n - ldap\n - saltuser\n - \'@runner\'}) expected that the catalogue would contain File[/etc/salt/master.d/foreman.conf] with content set to /external_auth:\n - ldap\n - saltuser\n - \'@runner\'/ but it is set to "# /etc/salt/master.d/foreman.config Master configuration\n#\n# This file summarizes configurations for the salt-master.\n# Have a look at the [Foreman Salt Plugin Documentation](https://theforeman.org/plugins/foreman_salt/) for detailed explanations.\n#\n# After editing this file, run the following command to active the changes:\n# systemctl restart salt-master\n\n\n##\n# Autosign\nautosign_grains_dir: /var/lib/foreman-proxy/salt/grains\nautosign_file: /etc/salt/example.conf\n# Uncomment the next line to make use of the autosign host name file (not recommended)\n# permissive_pki_access: True\n\n\n##\n# Salt Master service user\nuser: example\n\n\n##\n# Node classifier\nmaster_tops:\n ext_nodes: /usr/bin/foreman-node\n\n\n##\n# Pillar data access\next_pillar:\n - puppet: /usr/bin/foreman-node\n\n\n##\n# Salt API access\nexternal_auth:\n ldap:\n saltapi:\n - '@runner'\n\nrest_cherrypy:\n port: 9191\n ssl_key: /etc/puppetlabs/puppet/ssl/private_keys/foo.example.com.pem\n ssl_crt: /etc/puppetlabs/puppet/ssl/certs/foo.example.com.pem\n\nnetapi_enable_clients:\n - runner\n - local\n - ssh\n - wheel\n\n\n##\n# Remote execution provider\npublisher_acl:\n foreman-proxy:\n - state.template_str\n\n\n##\n# Reactors\nreactor:\n - 'salt/auth': # Autosign reactor\n - /usr/share/foreman-proxy/salt/reactors/foreman_minion_auth.sls\n - 'salt/job/*/ret/*': # Report reactor\n - /usr/share/foreman-proxy/salt/reactors/foreman_report_upload.sls\n" Diff: @@ -1,67 +1,133 @@ -(?-mix:external_auth:\n - ldap\n - saltuser\n - \'@runner\') +# /etc/salt/master.d/foreman.config Master configuration +# +# This file summarizes configurations for the salt-master. +# Have a look at the [Foreman Salt Plugin Documentation](https://theforeman.org/plugins/foreman_salt/) for detailed explanations. +# +# After editing this file, run the following command to active the changes: +# systemctl restart salt-master + + +## +# Autosign +autosign_grains_dir: /var/lib/foreman-proxy/salt/grains +autosign_file: /etc/salt/example.conf +# Uncomment the next line to make use of the autosign host name file (not recommended) +# permissive_pki_access: True + + +## +# Salt Master service user +user: example + + +## +# Node classifier +master_tops: + ext_nodes: /usr/bin/foreman-node + + +## +# Pillar data access +ext_pillar: + - puppet: /usr/bin/foreman-node + + +## +# Salt API access +external_auth: + ldap: + saltapi: + - '@runner' + +rest_cherrypy: + port: 9191 + ssl_key: /etc/puppetlabs/puppet/ssl/private_keys/foo.example.com.pem + ssl_crt: /etc/puppetlabs/puppet/ssl/certs/foo.example.com.pem + +netapi_enable_clients: + - runner + - local + - ssh + - wheel + + +## +# Remote execution provider +publisher_acl: + foreman-proxy: + - state.template_str + + +## +# Reactors +reactor: + - 'salt/auth': # Autosign reactor + - /usr/share/foreman-proxy/salt/reactors/foreman_minion_auth.sls + - 'salt/job/*/ret/*': # Report reactor + - /usr/share/foreman-proxy/salt/reactors/foreman_report_upload.sls

Process completed with exit code 1.

foreman_proxy::plugin::salt on debian-11-x86_64 with default settings should configure master.d/foreman.conf Failure/Error: should contain_file('/etc/salt/master.d/foreman.conf'). with_content(%r{autosign_grains_dir: /var/lib/foreman-proxy/salt/grains}). with_content(%r{autosign_file: /etc/salt/autosign.conf}). with_content(%r{user: root}). with_content(%r{netapi_enable_clients:\n - runner}). with_content(%r{external_auth:\n - pam\n - saltuser\n - \'@runner\'}) expected that the catalogue would contain File[/etc/salt/master.d/foreman.conf] with content set to /external_auth:\n - pam\n - saltuser\n - \'@runner\'/ but it is set to "# /etc/salt/master.d/foreman.config Master configuration\n#\n# This file summarizes configurations for the salt-master.\n# Have a look at the [Foreman Salt Plugin Documentation](https://theforeman.org/plugins/foreman_salt/) for detailed explanations.\n#\n# After editing this file, run the following command to active the changes:\n# systemctl restart salt-master\n\n\n##\n# Autosign\nautosign_grains_dir: /var/lib/foreman-proxy/salt/grains\nautosign_file: /etc/salt/autosign.conf\n# Uncomment the next line to make use of the autosign host name file (not recommended)\n# permissive_pki_access: True\n\n\n##\n# Salt Master service user\nuser: root\n\n\n##\n# Node classifier\nmaster_tops:\n ext_nodes: /usr/bin/foreman-node\n\n\n##\n# Pillar data access\next_pillar:\n - puppet: /usr/bin/foreman-node\n\n\n##\n# Salt API access\nexternal_auth:\n pam:\n saltuser:\n - '@runner'\n\nrest_cherrypy:\n port: 9191\n ssl_key: /etc/puppetlabs/puppet/ssl/private_keys/foo.example.com.pem\n ssl_crt: /etc/puppetlabs/puppet/ssl/certs/foo.example.com.pem\n\nnetapi_enable_clients:\n - runner\n\n\n##\n# Remote execution provider\npublisher_acl:\n foreman-proxy:\n - state.template_str\n\n\n##\n# Reactors\nreactor:\n - 'salt/auth': # Autosign reactor\n - /usr/share/foreman-proxy/salt/reactors/foreman_minion_auth.sls\n - 'salt/job/*/ret/*': # Report reactor\n - /usr/share/foreman-proxy/salt/reactors/foreman_report_upload.sls\n" Diff: @@ -1,64 +1,127 @@ -(?-mix:external_auth:\n - pam\n - saltuser\n - \'@runner\') +# /etc/salt/master.d/foreman.config Master configuration +# +# This file summarizes configurations for the salt-master. +# Have a look at the [Foreman Salt Plugin Documentation](https://theforeman.org/plugins/foreman_salt/) for detailed explanations. +# +# After editing this file, run the following command to active the changes: +# systemctl restart salt-master + + +## +# Autosign +autosign_grains_dir: /var/lib/foreman-proxy/salt/grains +autosign_file: /etc/salt/autosign.conf +# Uncomment the next line to make use of the autosign host name file (not recommended) +# permissive_pki_access: True + + +## +# Salt Master service user +user: root + + +## +# Node classifier +master_tops: + ext_nodes: /usr/bin/foreman-node + + +## +# Pillar data access +ext_pillar: + - puppet: /usr/bin/foreman-node + + +## +# Salt API access +external_auth: + pam: + saltuser: + - '@runner' + +rest_cherrypy: + port: 9191 + ssl_key: /etc/puppetlabs/puppet/ssl/private_keys/foo.example.com.pem + ssl_crt: /etc/puppetlabs/puppet/ssl/certs/foo.example.com.pem + +netapi_enable_clients: + - runner + + +## +# Remote execution provider +publisher_acl: + foreman-proxy: + - state.template_str + + +## +# Reactors +reactor: + - 'salt/auth': # Autosign reactor + - /usr/share/foreman-proxy/salt/reactors/foreman_minion_auth.sls + - 'salt/job/*/ret/*': # Report reactor + - /usr/share/foreman-proxy/salt/reactors/foreman_report_upload.sls

foreman_proxy::plugin::salt on debian-11-x86_64 with overwritten parameters should change master.d/foreman.conf parameters Failure/Error: should contain_file('/etc/salt/master.d/foreman.conf'). with_content(%r{user: example}). with_content(%r{autosign_grains_dir: /var/lib/foreman-proxy/salt/grains}). with_content(%r{autosign_file: /etc/salt/example.conf}). with_content(%r{netapi_enable_clients:\n - runner\n - local\n - ssh\n - wheel}). with_content(%r{external_auth:\n - ldap\n - saltuser\n - \'@runner\'}) expected that the catalogue would contain File[/etc/salt/master.d/foreman.conf] with content set to /external_auth:\n - ldap\n - saltuser\n - \'@runner\'/ but it is set to "# /etc/salt/master.d/foreman.config Master configuration\n#\n# This file summarizes configurations for the salt-master.\n# Have a look at the [Foreman Salt Plugin Documentation](https://theforeman.org/plugins/foreman_salt/) for detailed explanations.\n#\n# After editing this file, run the following command to active the changes:\n# systemctl restart salt-master\n\n\n##\n# Autosign\nautosign_grains_dir: /var/lib/foreman-proxy/salt/grains\nautosign_file: /etc/salt/example.conf\n# Uncomment the next line to make use of the autosign host name file (not recommended)\n# permissive_pki_access: True\n\n\n##\n# Salt Master service user\nuser: example\n\n\n##\n# Node classifier\nmaster_tops:\n ext_nodes: /usr/bin/foreman-node\n\n\n##\n# Pillar data access\next_pillar:\n - puppet: /usr/bin/foreman-node\n\n\n##\n# Salt API access\nexternal_auth:\n ldap:\n saltapi:\n - '@runner'\n\nrest_cherrypy:\n port: 9191\n ssl_key: /etc/puppetlabs/puppet/ssl/private_keys/foo.example.com.pem\n ssl_crt: /etc/puppetlabs/puppet/ssl/certs/foo.example.com.pem\n\nnetapi_enable_clients:\n - runner\n - local\n - ssh\n - wheel\n\n\n##\n# Remote execution provider\npublisher_acl:\n foreman-proxy:\n - state.template_str\n\n\n##\n# Reactors\nreactor:\n - 'salt/auth': # Autosign reactor\n - /usr/share/foreman-proxy/salt/reactors/foreman_minion_auth.sls\n - 'salt/job/*/ret/*': # Report reactor\n - /usr/share/foreman-proxy/salt/reactors/foreman_report_upload.sls\n" Diff: @@ -1,67 +1,133 @@ -(?-mix:external_auth:\n - ldap\n - saltuser\n - \'@runner\') +# /etc/salt/master.d/foreman.config Master configuration +# +# This file summarizes configurations for the salt-master. +# Have a look at the [Foreman Salt Plugin Documentation](https://theforeman.org/plugins/foreman_salt/) for detailed explanations. +# +# After editing this file, run the following command to active the changes: +# systemctl restart salt-master + + +## +# Autosign +autosign_grains_dir: /var/lib/foreman-proxy/salt/grains +autosign_file: /etc/salt/example.conf +# Uncomment the next line to make use of the autosign host name file (not recommended) +# permissive_pki_access: True + + +## +# Salt Master service user +user: example + + +## +# Node classifier +master_tops: + ext_nodes: /usr/bin/foreman-node + + +## +# Pillar data access +ext_pillar: + - puppet: /usr/bin/foreman-node + + +## +# Salt API access +external_auth: + ldap: + saltapi: + - '@runner' + +rest_cherrypy: + port: 9191 + ssl_key: /etc/puppetlabs/puppet/ssl/private_keys/foo.example.com.pem + ssl_crt: /etc/puppetlabs/puppet/ssl/certs/foo.example.com.pem + +netapi_enable_clients: + - runner + - local + - ssh + - wheel + + +## +# Remote execution provider +publisher_acl: + foreman-proxy: + - state.template_str + + +## +# Reactors +reactor: + - 'salt/auth': # Autosign reactor + - /usr/share/foreman-proxy/salt/reactors/foreman_minion_auth.sls + - 'salt/job/*/ret/*': # Report reactor + - /usr/share/foreman-proxy/salt/reactors/foreman_report_upload.sls

foreman_proxy::plugin::salt on redhat-8-x86_64 with default settings should configure master.d/foreman.conf Failure/Error: should contain_file('/etc/salt/master.d/foreman.conf'). with_content(%r{autosign_grains_dir: /var/lib/foreman-proxy/salt/grains}). with_content(%r{autosign_file: /etc/salt/autosign.conf}). with_content(%r{user: root}). with_content(%r{netapi_enable_clients:\n - runner}). with_content(%r{external_auth:\n - pam\n - saltuser\n - \'@runner\'}) expected that the catalogue would contain File[/etc/salt/master.d/foreman.conf] with content set to /external_auth:\n - pam\n - saltuser\n - \'@runner\'/ but it is set to "# /etc/salt/master.d/foreman.config Master configuration\n#\n# This file summarizes configurations for the salt-master.\n# Have a look at the [Foreman Salt Plugin Documentation](https://theforeman.org/plugins/foreman_salt/) for detailed explanations.\n#\n# After editing this file, run the following command to active the changes:\n# systemctl restart salt-master\n\n\n##\n# Autosign\nautosign_grains_dir: /var/lib/foreman-proxy/salt/grains\nautosign_file: /etc/salt/autosign.conf\n# Uncomment the next line to make use of the autosign host name file (not recommended)\n# permissive_pki_access: True\n\n\n##\n# Salt Master service user\nuser: root\n\n\n##\n# Node classifier\nmaster_tops:\n ext_nodes: /usr/bin/foreman-node\n\n\n##\n# Pillar data access\next_pillar:\n - puppet: /usr/bin/foreman-node\n\n\n##\n# Salt API access\nexternal_auth:\n pam:\n saltuser:\n - '@runner'\n\nrest_cherrypy:\n port: 9191\n ssl_key: /etc/puppetlabs/puppet/ssl/private_keys/foo.example.com.pem\n ssl_crt: /etc/puppetlabs/puppet/ssl/certs/foo.example.com.pem\n\nnetapi_enable_clients:\n - runner\n\n\n##\n# Remote execution provider\npublisher_acl:\n foreman-proxy:\n - state.template_str\n\n\n##\n# Reactors\nreactor:\n - 'salt/auth': # Autosign reactor\n - /usr/share/foreman-proxy/salt/reactors/foreman_minion_auth.sls\n - 'salt/job/*/ret/*': # Report reactor\n - /usr/share/foreman-proxy/salt/reactors/foreman_report_upload.sls\n" Diff: @@ -1,64 +1,127 @@ -(?-mix:external_auth:\n - pam\n - saltuser\n - \'@runner\') +# /etc/salt/master.d/foreman.config Master configuration +# +# This file summarizes configurations for the salt-master. +# Have a look at the [Foreman Salt Plugin Documentation](https://theforeman.org/plugins/foreman_salt/) for detailed explanations. +# +# After editing this file, run the following command to active the changes: +# systemctl restart salt-master + + +## +# Autosign +autosign_grains_dir: /var/lib/foreman-proxy/salt/grains +autosign_file: /etc/salt/autosign.conf +# Uncomment the next line to make use of the autosign host name file (not recommended) +# permissive_pki_access: True + + +## +# Salt Master service user +user: root + + +## +# Node classifier +master_tops: + ext_nodes: /usr/bin/foreman-node + + +## +# Pillar data access +ext_pillar: + - puppet: /usr/bin/foreman-node + + +## +# Salt API access +external_auth: + pam: + saltuser: + - '@runner' + +rest_cherrypy: + port: 9191 + ssl_key: /etc/puppetlabs/puppet/ssl/private_keys/foo.example.com.pem + ssl_crt: /etc/puppetlabs/puppet/ssl/certs/foo.example.com.pem + +netapi_enable_clients: + - runner + + +## +# Remote execution provider +publisher_acl: + foreman-proxy: + - state.template_str + + +## +# Reactors +reactor: + - 'salt/auth': # Autosign reactor + - /usr/share/foreman-proxy/salt/reactors/foreman_minion_auth.sls + - 'salt/job/*/ret/*': # Report reactor + - /usr/share/foreman-proxy/salt/reactors/foreman_report_upload.sls

foreman_proxy::plugin::salt on redhat-8-x86_64 with overwritten parameters should change master.d/foreman.conf parameters Failure/Error: should contain_file('/etc/salt/master.d/foreman.conf'). with_content(%r{user: example}). with_content(%r{autosign_grains_dir: /var/lib/foreman-proxy/salt/grains}). with_content(%r{autosign_file: /etc/salt/example.conf}). with_content(%r{netapi_enable_clients:\n - runner\n - local\n - ssh\n - wheel}). with_content(%r{external_auth:\n - ldap\n - saltuser\n - \'@runner\'}) expected that the catalogue would contain File[/etc/salt/master.d/foreman.conf] with content set to /external_auth:\n - ldap\n - saltuser\n - \'@runner\'/ but it is set to "# /etc/salt/master.d/foreman.config Master configuration\n#\n# This file summarizes configurations for the salt-master.\n# Have a look at the [Foreman Salt Plugin Documentation](https://theforeman.org/plugins/foreman_salt/) for detailed explanations.\n#\n# After editing this file, run the following command to active the changes:\n# systemctl restart salt-master\n\n\n##\n# Autosign\nautosign_grains_dir: /var/lib/foreman-proxy/salt/grains\nautosign_file: /etc/salt/example.conf\n# Uncomment the next line to make use of the autosign host name file (not recommended)\n# permissive_pki_access: True\n\n\n##\n# Salt Master service user\nuser: example\n\n\n##\n# Node classifier\nmaster_tops:\n ext_nodes: /usr/bin/foreman-node\n\n\n##\n# Pillar data access\next_pillar:\n - puppet: /usr/bin/foreman-node\n\n\n##\n# Salt API access\nexternal_auth:\n ldap:\n saltapi:\n - '@runner'\n\nrest_cherrypy:\n port: 9191\n ssl_key: /etc/puppetlabs/puppet/ssl/private_keys/foo.example.com.pem\n ssl_crt: /etc/puppetlabs/puppet/ssl/certs/foo.example.com.pem\n\nnetapi_enable_clients:\n - runner\n - local\n - ssh\n - wheel\n\n\n##\n# Remote execution provider\npublisher_acl:\n foreman-proxy:\n - state.template_str\n\n\n##\n# Reactors\nreactor:\n - 'salt/auth': # Autosign reactor\n - /usr/share/foreman-proxy/salt/reactors/foreman_minion_auth.sls\n - 'salt/job/*/ret/*': # Report reactor\n - /usr/share/foreman-proxy/salt/reactors/foreman_report_upload.sls\n" Diff: @@ -1,67 +1,133 @@ -(?-mix:external_auth:\n - ldap\n - saltuser\n - \'@runner\') +# /etc/salt/master.d/foreman.config Master configuration +# +# This file summarizes configurations for the salt-master. +# Have a look at the [Foreman Salt Plugin Documentation](https://theforeman.org/plugins/foreman_salt/) for detailed explanations. +# +# After editing this file, run the following command to active the changes: +# systemctl restart salt-master + + +## +# Autosign +autosign_grains_dir: /var/lib/foreman-proxy/salt/grains +autosign_file: /etc/salt/example.conf +# Uncomment the next line to make use of the autosign host name file (not recommended) +# permissive_pki_access: True + + +## +# Salt Master service user +user: example + + +## +# Node classifier +master_tops: + ext_nodes: /usr/bin/foreman-node + + +## +# Pillar data access +ext_pillar: + - puppet: /usr/bin/foreman-node + + +## +# Salt API access +external_auth: + ldap: + saltapi: + - '@runner' + +rest_cherrypy: + port: 9191 + ssl_key: /etc/puppetlabs/puppet/ssl/private_keys/foo.example.com.pem + ssl_crt: /etc/puppetlabs/puppet/ssl/certs/foo.example.com.pem + +netapi_enable_clients: + - runner + - local + - ssh + - wheel + + +## +# Remote execution provider +publisher_acl: + foreman-proxy: + - state.template_str + + +## +# Reactors +reactor: + - 'salt/auth': # Autosign reactor + - /usr/share/foreman-proxy/salt/reactors/foreman_minion_auth.sls + - 'salt/job/*/ret/*': # Report reactor + - /usr/share/foreman-proxy/salt/reactors/foreman_report_upload.sls

Process completed with exit code 1.

Scenario: install foreman-proxy applies with no errors Failure/Error: raise CommandFailure, "Host '#{self}' exited with #{result.exit_code} running:\n #{cmdline}\nLast #{@options[:trace_limit]} lines of output were:\n#{result.formatted_output(@options[:trace_limit])}" Beaker::Host::CommandFailure: Host 'ubuntu2004-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_132634845.zcWZDB.pp Last 10 lines of output were: �[mNotice: /Stage[main]/Foreman_proxy::Module::Registration/Foreman_proxy::Module[registration]/Foreman_proxy::Settings_file[registration]/File[/etc/foreman-proxy/settings.d/registration.yml]/content: content changed '{sha256}0ff33aa71af9054db8c2c1a498ef8dfc869976d812105ee5c2d90579ab25fdf3' to '{sha256}1c4f7110c2a4933b802919017e614d7354b310533967402255a2581a32d0fb9c' �[mNotice: /Stage[main]/Foreman_proxy::Module::Registration/Foreman_proxy::Module[registration]/Foreman_proxy::Settings_file[registration]/File[/etc/foreman-proxy/settings.d/registration.yml]/group: group changed 'root' to 'foreman-proxy' �[mNotice: /Stage[main]/Foreman_proxy::Module::Registration/Foreman_proxy::Module[registration]/Foreman_proxy::Settings_file[registration]/File[/etc/foreman-proxy/settings.d/registration.yml]/mode: mode changed '0644' to '0640' Info: Foreman_proxy::Settings_file[registration]: Scheduling refresh of Class[Foreman_proxy::Service] Info: Class[Foreman_proxy::Config]: Scheduling refresh of Class[Foreman_proxy::Service] Info: Class[Foreman_proxy::Service]: Scheduling refresh of Service[foreman-proxy] �[mNotice: /Stage[main]/Foreman_proxy::Service/Service[foreman-proxy]: Triggered 'refresh' from 1 event Info: Class[Foreman_proxy::Service]: Scheduling refresh of Class[Foreman_proxy::Register] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 8.69 seconds Shared Example Group: "an idempotent resource" called from ./vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-3.2.0/lib/voxpupuli/acceptance/examples.rb:14 Shared Example Group: "the example" called from ./spec/acceptance/dns_spec.rb:8

Scenario: install foreman-proxy applies a second time without changes Failure/Error: raise CommandFailure, "Host '#{self}' exited with #{result.exit_code} running:\n #{cmdline}\nLast #{@options[:trace_limit]} lines of output were:\n#{result.formatted_output(@options[:trace_limit])}" Beaker::Host::CommandFailure: Host 'ubuntu2004-64-puppet8.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_132649107.ckvDcR.pp Last 10 lines of output were: Error: Execution of '/usr/sbin/named-checkconf /etc/bind/zones.conf20240920-6633-17zkcj7' returned 1: Error: Could not execute posix command: No such file or directory - /usr/sbin/named-checkconf Error: /Stage[main]/Dns::Config/Concat[/etc/bind/zones.conf]/File[/etc/bind/zones.conf]/ensure: change from 'absent' to 'file' failed: Execution of '/usr/sbin/named-checkconf /etc/bind/zones.conf20240920-6633-17zkcj7' returned 1: Error: Could not execute posix command: No such file or directory - /usr/sbin/named-checkconf Info: Computing checksum on file /etc/bind/named.conf Info: /Stage[main]/Dns::Config/Concat[/etc/bind/named.conf]/File[/etc/bind/named.conf]: Filebucketed /etc/bind/named.conf to puppet with sum b2e8347dd7442eb1f1452e40fa47331694c8660d3f0a4ad41500c0f020d38930 Error: Execution of '/usr/sbin/named-checkconf /etc/bind/named.conf20240920-6633-1arojz7' returned 1: Error: Could not execute posix command: No such file or directory - /usr/sbin/named-checkconf Error: /Stage[main]/Dns::Config/Concat[/etc/bind/named.conf]/File[/etc/bind/named.conf]/content: change from '{sha256}b2e8347dd7442eb1f1452e40fa47331694c8660d3f0a4ad41500c0f020d38930' to '{sha256}f79c20c31aaed9ee8c81d0b583cb664e665d9c62d3b466f75de064d769130bc8' failed: Execution of '/usr/sbin/named-checkconf /etc/bind/named.conf20240920-6633-1arojz7' returned 1: Error: Could not execute posix command: No such file or directory - /usr/sbin/named-checkconf �[mNotice: /Stage[main]/Dns::Service/Service[bind9]: Dependency File[/etc/bind/zones.conf] has failures: true �[mNotice: /Stage[main]/Dns::Service/Service[bind9]: Dependency File[/etc/bind/named.conf] has failures: true Warning: /Stage[main]/Dns::Service/Service[bind9]: Skipping because of failed dependencies �[mNotice: Applied catalog in 1.08 seconds Shared Example Group: "an idempotent resource" called from ./vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-3.2.0/lib/voxpupuli/acceptance/examples.rb:14 Shared Example Group: "the example" called from ./spec/acceptance/dns_spec.rb:8

Scenario: install foreman-proxy forward dns Command "dig +short SOA example.com @localhost" stdout is expected to match /ubuntu2004-64-puppet8.example.com\. root\.example\.com\. \d+ 86400 3600 604800 3600\n/ Failure/Error: its(:stdout) { is_expected.to match(/#{host_inventory['fqdn']}\. root\.example\.com\. \d+ 86400 3600 604800 3600\n/) } expected ";; communications error to 127.0.0.1#53: connection refused\n;; communications error to 127.0.0.1#53...ed\n;; communications error to 127.0.0.1#53: connection refused\n;; no servers could be reached\n\n" to match /ubuntu2004-64-puppet8.example.com\. root\.example\.com\. \d+ 86400 3600 604800 3600\n/ Diff: @@ -1,6 +1,11 @@ -/ubuntu2004-64-puppet8.example.com\. root\.example\.com\. \d+ 86400 3600 604800 3600\n/ +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; no servers could be reached

Scenario: install foreman-proxy forward dns Command "dig +short A integration.example.com @localhost" stdout is expected to eq "192.0.2.100\n" Failure/Error: its(:stdout) { is_expected.to eq("192.0.2.100\n") } expected: "192.0.2.100\n" got: ";; communications error to 127.0.0.1#53: connection refused\n;; communications error to 127.0.0.1#53...ed\n;; communications error to 127.0.0.1#53: connection refused\n;; no servers could be reached\n\n" (compared using ==) Diff: @@ -1,6 +1,11 @@ -192.0.2.100 +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; no servers could be reached

Scenario: install foreman-proxy forward dns Command "dig +short A integration.example.com @localhost" stdout is expected to eq "" Failure/Error: its(:stdout) { is_expected.to eq('') } expected: "" got: ";; communications error to 127.0.0.1#53: connection refused\n;; communications error to 127.0.0.1#53...ed\n;; communications error to 127.0.0.1#53: connection refused\n;; no servers could be reached\n\n" (compared using ==) Diff: @@ -1,6 +1,12 @@ +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; no servers could be reached

Scenario: install foreman-proxy reverse dns Command "dig +short SOA 2.0.192.in-addr.arpa @localhost" stdout is expected to match /ubuntu2004-64-puppet8.example.com\. root\.2\.0\.192\.in-addr\.arpa\. \d+ 86400 3600 604800 3600\n/ Failure/Error: its(:stdout) { is_expected.to match(/#{host_inventory['fqdn']}\. root\.2\.0\.192\.in-addr\.arpa\. \d+ 86400 3600 604800 3600\n/) } expected ";; communications error to 127.0.0.1#53: connection refused\n;; communications error to 127.0.0.1#53...ed\n;; communications error to 127.0.0.1#53: connection refused\n;; no servers could be reached\n\n" to match /ubuntu2004-64-puppet8.example.com\. root\.2\.0\.192\.in-addr\.arpa\. \d+ 86400 3600 604800 3600\n/ Diff: @@ -1,6 +1,11 @@ -/ubuntu2004-64-puppet8.example.com\. root\.2\.0\.192\.in-addr\.arpa\. \d+ 86400 3600 604800 3600\n/ +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; no servers could be reached

Scenario: install foreman-proxy reverse dns Command "dig +short -x 192.0.2.100 @localhost" stdout is expected to eq "integration.example.com.\n" Failure/Error: its(:stdout) { is_expected.to eq("integration.example.com.\n") } expected: "integration.example.com.\n" got: ";; communications error to 127.0.0.1#53: connection refused\n;; communications error to 127.0.0.1#53...ed\n;; communications error to 127.0.0.1#53: connection refused\n;; no servers could be reached\n\n" (compared using ==) Diff: @@ -1,6 +1,11 @@ -integration.example.com. +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; no servers could be reached

Scenario: install foreman-proxy reverse dns Command "dig +short -x 192.0.2.100 @localhost" stdout is expected to eq "" Failure/Error: its(:stdout) { is_expected.to eq('') } expected: "" got: ";; communications error to 127.0.0.1#53: connection refused\n;; communications error to 127.0.0.1#53...ed\n;; communications error to 127.0.0.1#53: connection refused\n;; no servers could be reached\n\n" (compared using ==) Diff: @@ -1,6 +1,12 @@ +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; no servers could be reached

Process completed with exit code 1.

Scenario: install foreman-proxy applies with no errors Failure/Error: raise CommandFailure, "Host '#{self}' exited with #{result.exit_code} running:\n #{cmdline}\nLast #{@options[:trace_limit]} lines of output were:\n#{result.formatted_output(@options[:trace_limit])}" Beaker::Host::CommandFailure: Host 'ubuntu2004-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_132641320.f3HKvc.pp Last 10 lines of output were: �[mNotice: /Stage[main]/Foreman_proxy::Module::Registration/Foreman_proxy::Module[registration]/Foreman_proxy::Settings_file[registration]/File[/etc/foreman-proxy/settings.d/registration.yml]/content: content changed '{sha256}0ff33aa71af9054db8c2c1a498ef8dfc869976d812105ee5c2d90579ab25fdf3' to '{sha256}1c4f7110c2a4933b802919017e614d7354b310533967402255a2581a32d0fb9c' �[mNotice: /Stage[main]/Foreman_proxy::Module::Registration/Foreman_proxy::Module[registration]/Foreman_proxy::Settings_file[registration]/File[/etc/foreman-proxy/settings.d/registration.yml]/group: group changed 'root' to 'foreman-proxy' �[mNotice: /Stage[main]/Foreman_proxy::Module::Registration/Foreman_proxy::Module[registration]/Foreman_proxy::Settings_file[registration]/File[/etc/foreman-proxy/settings.d/registration.yml]/mode: mode changed '0644' to '0640' Info: Foreman_proxy::Settings_file[registration]: Scheduling refresh of Class[Foreman_proxy::Service] Info: Class[Foreman_proxy::Config]: Scheduling refresh of Class[Foreman_proxy::Service] Info: Class[Foreman_proxy::Service]: Scheduling refresh of Service[foreman-proxy] �[mNotice: /Stage[main]/Foreman_proxy::Service/Service[foreman-proxy]: Triggered 'refresh' from 1 event Info: Class[Foreman_proxy::Service]: Scheduling refresh of Class[Foreman_proxy::Register] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 9.10 seconds Shared Example Group: "an idempotent resource" called from ./vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-3.2.0/lib/voxpupuli/acceptance/examples.rb:14 Shared Example Group: "the example" called from ./spec/acceptance/dns_spec.rb:8

Scenario: install foreman-proxy applies a second time without changes Failure/Error: raise CommandFailure, "Host '#{self}' exited with #{result.exit_code} running:\n #{cmdline}\nLast #{@options[:trace_limit]} lines of output were:\n#{result.formatted_output(@options[:trace_limit])}" Beaker::Host::CommandFailure: Host 'ubuntu2004-64-puppet7.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_132655775.HmW8BS.pp Last 10 lines of output were: Error: Execution of '/usr/sbin/named-checkconf /etc/bind/zones.conf20240920-6680-3d1qb' returned 1: Error: Could not execute posix command: No such file or directory - /usr/sbin/named-checkconf Error: /Stage[main]/Dns::Config/Concat[/etc/bind/zones.conf]/File[/etc/bind/zones.conf]/ensure: change from 'absent' to 'file' failed: Execution of '/usr/sbin/named-checkconf /etc/bind/zones.conf20240920-6680-3d1qb' returned 1: Error: Could not execute posix command: No such file or directory - /usr/sbin/named-checkconf Info: Computing checksum on file /etc/bind/named.conf Info: /Stage[main]/Dns::Config/Concat[/etc/bind/named.conf]/File[/etc/bind/named.conf]: Filebucketed /etc/bind/named.conf to puppet with sum b2e8347dd7442eb1f1452e40fa47331694c8660d3f0a4ad41500c0f020d38930 Error: Execution of '/usr/sbin/named-checkconf /etc/bind/named.conf20240920-6680-1lhqb04' returned 1: Error: Could not execute posix command: No such file or directory - /usr/sbin/named-checkconf Error: /Stage[main]/Dns::Config/Concat[/etc/bind/named.conf]/File[/etc/bind/named.conf]/content: change from '{sha256}b2e8347dd7442eb1f1452e40fa47331694c8660d3f0a4ad41500c0f020d38930' to '{sha256}f79c20c31aaed9ee8c81d0b583cb664e665d9c62d3b466f75de064d769130bc8' failed: Execution of '/usr/sbin/named-checkconf /etc/bind/named.conf20240920-6680-1lhqb04' returned 1: Error: Could not execute posix command: No such file or directory - /usr/sbin/named-checkconf �[mNotice: /Stage[main]/Dns::Service/Service[bind9]: Dependency File[/etc/bind/zones.conf] has failures: true �[mNotice: /Stage[main]/Dns::Service/Service[bind9]: Dependency File[/etc/bind/named.conf] has failures: true Warning: /Stage[main]/Dns::Service/Service[bind9]: Skipping because of failed dependencies �[mNotice: Applied catalog in 1.15 seconds Shared Example Group: "an idempotent resource" called from ./vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-3.2.0/lib/voxpupuli/acceptance/examples.rb:14 Shared Example Group: "the example" called from ./spec/acceptance/dns_spec.rb:8

Scenario: install foreman-proxy forward dns Command "dig +short SOA example.com @localhost" stdout is expected to match /ubuntu2004-64-puppet7.example.com\. root\.example\.com\. \d+ 86400 3600 604800 3600\n/ Failure/Error: its(:stdout) { is_expected.to match(/#{host_inventory['fqdn']}\. root\.example\.com\. \d+ 86400 3600 604800 3600\n/) } expected ";; communications error to 127.0.0.1#53: connection refused\n;; communications error to 127.0.0.1#53...ed\n;; communications error to 127.0.0.1#53: connection refused\n;; no servers could be reached\n\n" to match /ubuntu2004-64-puppet7.example.com\. root\.example\.com\. \d+ 86400 3600 604800 3600\n/ Diff: @@ -1,6 +1,11 @@ -/ubuntu2004-64-puppet7.example.com\. root\.example\.com\. \d+ 86400 3600 604800 3600\n/ +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; no servers could be reached

Scenario: install foreman-proxy forward dns Command "dig +short A integration.example.com @localhost" stdout is expected to eq "192.0.2.100\n" Failure/Error: its(:stdout) { is_expected.to eq("192.0.2.100\n") } expected: "192.0.2.100\n" got: ";; communications error to 127.0.0.1#53: connection refused\n;; communications error to 127.0.0.1#53...ed\n;; communications error to 127.0.0.1#53: connection refused\n;; no servers could be reached\n\n" (compared using ==) Diff: @@ -1,6 +1,11 @@ -192.0.2.100 +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; no servers could be reached

Scenario: install foreman-proxy forward dns Command "dig +short A integration.example.com @localhost" stdout is expected to eq "" Failure/Error: its(:stdout) { is_expected.to eq('') } expected: "" got: ";; communications error to 127.0.0.1#53: connection refused\n;; communications error to 127.0.0.1#53...ed\n;; communications error to 127.0.0.1#53: connection refused\n;; no servers could be reached\n\n" (compared using ==) Diff: @@ -1,6 +1,12 @@ +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; no servers could be reached

Scenario: install foreman-proxy reverse dns Command "dig +short SOA 2.0.192.in-addr.arpa @localhost" stdout is expected to match /ubuntu2004-64-puppet7.example.com\. root\.2\.0\.192\.in-addr\.arpa\. \d+ 86400 3600 604800 3600\n/ Failure/Error: its(:stdout) { is_expected.to match(/#{host_inventory['fqdn']}\. root\.2\.0\.192\.in-addr\.arpa\. \d+ 86400 3600 604800 3600\n/) } expected ";; communications error to 127.0.0.1#53: connection refused\n;; communications error to 127.0.0.1#53...ed\n;; communications error to 127.0.0.1#53: connection refused\n;; no servers could be reached\n\n" to match /ubuntu2004-64-puppet7.example.com\. root\.2\.0\.192\.in-addr\.arpa\. \d+ 86400 3600 604800 3600\n/ Diff: @@ -1,6 +1,11 @@ -/ubuntu2004-64-puppet7.example.com\. root\.2\.0\.192\.in-addr\.arpa\. \d+ 86400 3600 604800 3600\n/ +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; no servers could be reached

Scenario: install foreman-proxy reverse dns Command "dig +short -x 192.0.2.100 @localhost" stdout is expected to eq "integration.example.com.\n" Failure/Error: its(:stdout) { is_expected.to eq("integration.example.com.\n") } expected: "integration.example.com.\n" got: ";; communications error to 127.0.0.1#53: connection refused\n;; communications error to 127.0.0.1#53...ed\n;; communications error to 127.0.0.1#53: connection refused\n;; no servers could be reached\n\n" (compared using ==) Diff: @@ -1,6 +1,11 @@ -integration.example.com. +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; no servers could be reached

Scenario: install foreman-proxy reverse dns Command "dig +short -x 192.0.2.100 @localhost" stdout is expected to eq "" Failure/Error: its(:stdout) { is_expected.to eq('') } expected: "" got: ";; communications error to 127.0.0.1#53: connection refused\n;; communications error to 127.0.0.1#53...ed\n;; communications error to 127.0.0.1#53: connection refused\n;; no servers could be reached\n\n" (compared using ==) Diff: @@ -1,6 +1,12 @@ +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; communications error to 127.0.0.1#53: connection refused +;; no servers could be reached

Process completed with exit code 1.

Process completed with exit code 1.

Skipping EOL operating system CentOS 8

Skipping EOL operating system Debian 11

Skipping EOL operating system FreeBSD 11