Puppet ENC reports not showing up

Support
,
1

Problem:
The Puppet ENC reports are not showing up in the UI for a newly built instance of Foreman/Katello.

Expected outcome:
I would expect to see them for each host that is checking in as well as under Config Management.

Foreman and Proxy versions:
Foreman and Proxy plugin versions:
foreman-3.0.1-1.el8.noarch
foreman-cli-3.0.1-1.el8.noarch
foreman-debug-3.0.1-1.el8.noarch
foreman-dynflow-sidekiq-3.0.1-1.el8.noarch
foreman.domain.com-apache-1.0-80.noarch
foreman.domain.com-foreman-client-1.0-80.noarch
foreman.domain.com-foreman-proxy-1.0-80.noarch
foreman.domain.com-foreman-proxy-client-1.0-80.noarch
foreman.domain.com-puppet-client-1.0-80.noarch
foreman.domain.com-qpid-broker-1.0-1.noarch
foreman.domain.com-qpid-router-server-1.0-1.noarch
foreman-installer-3.0.1-1.el8.noarch
foreman-installer-katello-3.0.1-1.el8.noarch
foreman-postgresql-3.0.1-1.el8.noarch
foreman-proxy-3.0.1-1.el8.noarch
foreman-release-3.0.1-1.el8.noarch
foreman-selinux-3.0.1-1.el8.noarch
foreman-service-3.0.1-1.el8.noarch
foreman-vmware-3.0.1-1.el8.noarch
katello-4.2.1-1.el8.noarch
katello-certs-tools-2.8.2-1.el8.noarch
katello-client-bootstrap-1.7.7-1.el8.noarch
katello-common-4.2.1-1.el8.noarch
katello-debug-4.2.1-1.el8.noarch
katello-default-ca-1.0-1.noarch
katello-repos-4.2.1-1.el8.noarch
katello-selinux-4.0.2-1.el8.noarch
katello-server-ca-1.0-1.noarch
qpid_router_katello_agent-qpid-router-client-1.0-1.noarch
rubygem-foreman_ansible-6.4.1-1.fm2_6.el8.noarch
rubygem-foreman_bootdisk-18.0.0-1.fm3_0.el8.noarch
rubygem-foreman_default_hostgroup-6.0.0-1.fm2_6.el8.noarch
rubygem-foreman_discovery-18.0.5-1.fm3_0.el8.noarch
rubygem-foreman_leapp-0.1.7-2.fm2_5.el8.noarch
rubygem-foreman_maintain-0.8.10-1.el8.noarch
rubygem-foreman_openscap-5.0.0-1.fm3_0.el8.noarch
rubygem-foreman_puppet-1.0.5-1.fm3_0.el8.noarch
rubygem-foreman_remote_execution-4.8.0-1.fm3_0.el8.noarch
rubygem-foreman_snapshot_management-2.0.1-1.fm2_6.el8.noarch
rubygem-foreman_statistics-1.2.0-1.fm3_0.el8.noarch
rubygem-foreman-tasks-5.1.1-1.fm3_0.el8.noarch
rubygem-foreman_templates-9.1.0-1.fm2_6.el8.noarch
rubygem-foreman_virt_who_configure-0.5.7-1.fm3_0.el8.noarch
rubygem-foreman_wreckingball-4.0.0-1.fm3_0.el8.noarch
rubygem-hammer_cli_foreman-3.0.0-1.el8.noarch
rubygem-hammer_cli_foreman_puppet-0.0.3-1.fm3_0.el8.noarch
rubygem-hammer_cli_foreman_remote_execution-0.2.2-1.fm3_0.el8.noarch
rubygem-hammer_cli_foreman_tasks-0.0.16-1.fm3_0.el8.noarch
rubygem-hammer_cli_katello-1.1.1-0.1.pre.master.20210804141838gitece0b63.el8.noarch
rubygem-katello-4.2.1-1.el8.noarch

Distribution and version:
CentOS Stream 8.5

Other relevant data:
Not sure if this is puppet runs checking in? I believe that it is however it differs from the “POST /api/reports” that documentation shows:

/var/log/foreman/production.log

2022-01-05T09:27:51 [I|app|47e3c186] Started POST “/api/config_reports” for 1.2.3.4 at 2022-01-05 09:27:51 -0500
2022-01-05T09:27:51 [I|app|47e3c186] Processing by Api::V2::ConfigReportsController#create as JSON

/var/log/puppetlabs/puppetserver/puppetserver-access.log

1.2.3.5 - - [04/Jan/2022:23:57:52 -0500] “PUT /puppet/v3/report/hostname.domain.com?environment=production HTTP/1.1” 200 17 “-” “Puppet/6.25.1 Ruby/2.5.9-p229 (x86_64-linux)” 221 154864 21

2

I re-ran the installer again (4th or 5th time) but this time with:

$ --puppet-server-reports foreman --puppet-server-storeconfigs true

And now reports are showing under Config Management but not all reports are showing under the host itself on the Metrics tab.

3

Ok so this seems to break things unless you are using PuppetDB as the storage backend. Reverting that fixed my new issues.

Highly recommend someone take some time and document this “plugin” and what the arguments do and don’t do. As of now I believe this is solved.

1 Like
4

In my case I had to correct the certificates paths the solution provided here Puppet fails with Error 500 on SERVER: Server Error: Failed when searching for node client.example.com - Red Hat Customer Portal works for me. But only after I run the foreman-installer a second time after making the changes in the foreman.yaml file.
Just save the paths

:ssl_ca: "/etc/pki/katello/puppet/puppet_client_ca.crt"
:ssl_cert: "/etc/pki/katello/puppet/puppet_client.crt"
:ssl_key: "/etc/pki/katello/puppet/puppet_client.key"

and then rerun the installer. That solves it for me.

1 Like
5

Glad you solved it as I was having the same issue on a fresh 3.1 install and managed to solve it with the installer as well. For some reason, the 3.1 installer sets the following parameters to UNDEF:

--puppet-server-foreman-ssl-ca
--puppet-server-foreman-ssl-cert
--puppet-server-foreman-ssl-key

This would appear to be the same case with 3.0 based on your versions listed above. I also did a 2.5 install and compared the install parameters and those three above are set correctly so it looks like the 3.x move to the puppet plugin doesn’t set these automatically. Once I set them with the installer, everything worked a expected.

Is this a bug or is it due to missing an install option?