Red Hat Bugzilla – Bug 1194767
unable to find foreman_scap_client package to list
Last modified: 2017-02-23 15:27:40 EST
Description of problem: When using puppet-foreman_scap_client rpm as puppet-module and running "puppet agent -t" . configuration fails due to unavailable package. [root@xxxx foreman_scap_client]# 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/root_home.rb Info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb Info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb Info: Caching catalog for samsung.englab.pnq.redhat.com Warning: The package type's allow_virtual parameter will be changing its default value from false to true in a future release. If you do not want to allow virtual packages, please explicitly set allow_virtual to false. (at /usr/lib/ruby/site_ruby/1.8/puppet/type.rb:816:in `set_default') Info: Applying configuration version '1424448382' Error: Execution of '/usr/bin/yum -d 0 -e 0 -y list foreman_scap_client' returned 1: Error: No matching Packages to list Error: /Stage[main]/Foreman_scap_client/Package[foreman_scap_client]/ensure: change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y list foreman_scap_client' returned 1: Error: No matching Packages to list Notice: /Stage[main]/Foreman_scap_client/File[foreman_scap_client]: Dependency Package[foreman_scap_client] has failures: true Warning: /Stage[main]/Foreman_scap_client/File[foreman_scap_client]: Skipping because of failed dependencies Notice: Finished catalog run in 1.83 seconds Version-Release number of selected component (if applicable): sat6.1 Beta snap3 How reproducible: always Shorts steps to reproduce: 1. run "puppet agent -t" on the provisioned client with foreman_scap_client puppet-class configured. Steps to Reproduce: 1. convert puppet-foreman_scap_client rpm to puppet-module by running "puppet module build" in /usr/share/puppet/modules/foreman_scap_client dir after installing the puppet-foreman_scap_client rpm. 2. create a puppet-repo and import this module 3. create cv, publish , promote 4. associate the puppet-class to a host 5. run "puppet agent -t" on the provisioned client with foreman_scap_client puppet-class configured. Actual results: Error: No matching Packages to list Expected results: puppet agent run should succeed. Additional info: And probably the package we are looking for is rubygem-foreman_scap_client and not just foreman_scap_client.
it is actually looking for foreman_scap_client, which is the client that run on the clients (hosts). May be related to https://bugzilla.redhat.com/show_bug.cgi?id=1194178 ?
I think in manifests/init.pp of the rpm puppet-foreman_scap_client , we may need to change 'foreman_scap_client' to 'rubygem-foreman_scap_client'
Fixed at: https://github.com/OpenSCAP/puppet-foreman_scap_client/pull/4 Please note that we need to sync to latest version of foreman_scap_client, before. @isimluk, can you verify and merge? Thanks.
https://github.com/OpenSCAP/puppet-foreman_scap_client/pull/4 is now merged. Pending release of a new rubygem-foreman_scap_client
Version 0.3.4 of puppet-foreman_scap_client has been released: https://forge.puppetlabs.com/isimluk/foreman_scap_client RPM Packaging change set is available through https://github.com/isimluk/foreman-packaging/commit/5c896db00345d47528dc321710d93af123fff239
The puppet module puppet-foreman_scap_client now contains rubygem-foreman_scap_client pacakge info to list. VERIFIED with sat6.1 Beta snap5
This bug is slated to be released with Satellite 6.1.
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. https://access.redhat.com/errata/RHSA-2015:1592