Description of problem: When we run capsule_certs_generate on upgraded satellite(to 6.3), it generates the capsule certs file but it throws below errors: ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' [ERROR 2017-10-03 17:21:39 verbose] rpm -q puppet-agent failed! Check the output for error! [ERROR 2017-10-03 17:21:39 verbose] rpm -q puppetserver failed! Check the output for error! ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' Version-Release number of selected component (if applicable): Satellite 6.3.0 snap 18.0 How reproducible: Always Steps to Reproduce: 1. Upgrade satellite from satellite 6.2 to 6.3 2. After upgrade, attempt to generate capsule cert using capsule-certs-generate utility on satellite. Actual results: Capsule cert tar generates but the capsule-certs-generate utility throws errors: ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' [ERROR 2017-10-03 17:21:39 verbose] rpm -q puppet-agent failed! Check the output for error! [ERROR 2017-10-03 17:21:39 verbose] rpm -q puppetserver failed! Check the output for error! ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' Expected results: Capsule-certs-generate utility should generate certs tar without any errors Additional info: 1. We also observed these errors while fresh installing satellite 6.3, installer passes but same errors are raised. 2. I see that puppet-server rpm is present on the server instead of puppetserver rpm so it seems utility algorithm is searching for wrong rpm name. 3. There is no such puppet-agent rpm found in the satellite.
Created redmine issue http://projects.theforeman.org/issues/21222 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/21222 has been resolved.
Verified! Satellite 6.3.0 snap 20 Steps: Generate capsule cert on satellite Behavior: Capsule Certificate is generated without any errors mentioned in Description of big also new errors are not observed
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-2018:0336