Red Hat Bugzilla – Bug 1315820
Provide separate puppet module for Insights to use on Capsules
Last modified: 2017-12-14 09:30:25 EST
Customer SFDC case number 01583479
Clients registered to Capsules fail to apply the "access_insights" puppet class used to register to Insights :
puppet agent -t
Info: Retrieving plugin
Info: Loading facts in /var/lib/puppet/lib/facter/pe_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/package_provider.rb
Info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb
Info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb
Info: Loading facts in /var/lib/puppet/lib/facter/ssh_server_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/service_provider.rb
Info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb
Info: Loading facts in /var/lib/puppet/lib/facter/ssh_client_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/rh_certificates.rb
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class access_insights_client for
This is because the Insights puppet module is bundled with the Red Hat Access plugin and is installed on the main Satellite server only, and does not exist in the Capsule environment.
A separate puppet module already exists [1,2] but was never officially released.
Since the Red Hat Insights Plugin is installed by default on the main server,
it would be ideal to have the puppet rpm installed on capsule by default.
There is another related problem to availaibility of insights in the capsules.
The environment is not switched, as it is done instead in the clients attached to the capsule.
[root@capsule ~]# puppet master --configprint modulepath --environment production
[root@capsule ~]# puppet master --configprint modulepath --environment KT_V_TS_QA_RHEL7_Rolling_7 /etc/puppet/environments/KT_V_TS_QA_RHEL7_Rolling_7/modules:/etc/puppet/environments/common:/etc/puppet/modules:/usr/share/puppet/modules
The modulepath is empty, and that is imo the problem.
Is maybe the problem linked to: http://projects.theforeman.org/issues/7277 Even if the version of puppet seems not affected:
[root@capsule ~]# rpm -q puppet puppet-3.6.2-4.el7sat.noarch
*** Bug 1332672 has been marked as a duplicate of this bug. ***
Builds for RPM are in brew:
Verified in Satellite 6.2.7 Snap 2.
The package redhat-access-insights-puppet is now provided by the Satellite Capsule repo. Below you can see it installed on the capsule as well as a successful registration to insights from a client that is registered to the capsule. Also see the attached screenshot of the client successfully showing up in the UI.
-bash-4.2# yum install redhat-access-insights-puppet
Loaded plugins: product-id, search-disabled-repos, subscription-manager
Default_Organization_627_rhel7_capsule | 2.1 kB 00:00:00
rhel-7-server-optional-rpms | 2.0 kB 00:00:00
rhel-7-server-rh-common-rpms | 2.1 kB 00:00:00
rhel-7-server-rpms | 2.0 kB 00:00:00
--> Running transaction check
---> Package redhat-access-insights-puppet.noarch 0:0.0.8-1.el7sat will be installed
--> Finished Dependency Resolution
Package Arch Version Repository Size
redhat-access-insights-puppet noarch 0.0.8-1.el7sat Default_Organization_627_rhel7_capsule 5.9 k
Install 1 Package
Total download size: 5.9 k
Installed size: 7.9 k
Is this ok [y/d/N]: y
redhat-access-insights-puppet-0.0.8-1.el7sat.noarch.rpm | 5.9 kB 00:00:02
Running transaction check
Running transaction test
Transaction test succeeded
Installing : redhat-access-insights-puppet-0.0.8-1.el7sat.noarch 1/1
Verifying : redhat-access-insights-puppet-0.0.8-1.el7sat.noarch 1/1
Client registered to capsule
[root@cloud-qe-20 ~]# redhat-access-insights --register
Successfully registered cloud-qe-20.idmqe.lab.eng.bos.redhat.com
Automatic daily scheduling for Insights has been enabled.
Starting to collect Insights data
Uploading Insights data, this may take a few minutes
Upload completed successfully!
[root@cloud-qe-20 ~]# cat /etc/rhsm/rhsm.conf | grep ytt
hostname = yttrium.idmqe.lab.eng.bos.redhat.com
Created attachment 1243029 [details]
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.