Bug 1836779 - "foreman-maintain health check" command failed with error "Error: Unknown Puppet subcommand 'master'"
Summary: "foreman-maintain health check" command failed with error "Error: Unknown Pup...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Maintain
Version: 6.8.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: 6.8.0
Assignee: Suraj Patil
QA Contact: Jameer Pathan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-18 06:22 UTC by Devendra Singh
Modified: 2021-07-28 11:38 UTC (History)
3 users (show)

Fixed In Version: rubygem-foreman_maintain-0.6.4
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 12:38:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 28040 0 Normal Closed Error: Unknown Puppet subcommand 'master' to Check to verify no empty CA cert requests exist 2020-09-08 23:34:58 UTC
Red Hat Product Errata RHBA-2020:4365 0 None None None 2020-10-27 12:38:38 UTC

Description Devendra Singh 2020-05-18 06:22:56 UTC
Description of problem: "foreman-maintain health check" command failed with error "Error: Unknown Puppet subcommand 'master'"


Version-Release number of selected component (if applicable):
6.8

How reproducible:
always

Steps to Reproduce:
1. Install satellite 6.8
2. Trigger foreman-maintain health check  command
# foreman-maintain health check 
Running ForemanMaintain::Scenario::FilteredScenario
Failed executing puppet master --configprint ssldir, exit status 1:
 Error: Unknown Puppet subcommand 'master'
See 'puppet help' for help on available puppet subcommands
--------------------------------------------------------------------------------


Actual results:
foreman-maintain health check failed with error "Error: Unknown Puppet subcommand 'master'"

Expected results:
puppet error should not come.

Additional info:

Comment 1 Bryan Kearney 2020-05-18 16:01:35 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/28040 has been resolved.

Comment 2 Jameer Pathan 2020-06-10 10:44:43 UTC
Verified

Verified with:
- Satellite 6.8.0 snap 3
- rubygem-foreman_maintain-0.6.4-1.el7sat.noarch

Test steps:
- Run "foreman-maintain health check"
- Create empty CA cert request files.
- foreman-maintain health check --label puppet-check-no-empty-cert-requests

Obsevations:
- foreman-maintain health check command executed successfully.
- puppet-check-no-empty-cert-requests check worked as expected.
- No error related to puppet.

Comment 5 errata-xmlrpc 2020-10-27 12:38:24 UTC
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 (Satellite 6.8 Satellite Maintenance Release), 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/RHBA-2020:4365


Note You need to log in before you can comment on or make changes to this bug.