Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Document URL: 

https://dxp-docp-prod.apps.ext-waf.spoke.prod.us-west-2.aws.paas.redhat.com/documentation/en-us/red_hat_satellite/6.14/html-single/administering_red_hat_satellite/index?lb_target=preview#Monitoring_Puppet_admin


Section Number and Name: 

16.4.3. Monitoring Puppet


Describe the issue:  

With Satellite-6.14, the puppet is by default disabled and there is no service called "puppetserver" running on Satellite and Capsule. The user needs to explicitly enable the puppet service on both Satellite and Capsule if needed. 

(i) The steps mentioned in Section 16.4.3. Monitoring Puppet are not valid because there is no Puppet tab within ' Satellite WebUI -> Infrastructure -> Capsules ' page.

(ii) The steps mentioned in Section 15.2.12. Increasing the Logging Level For Puppet Server are also not valid because there is no service called "puppetserver" running on Satellite or Capsule.


Suggestions for improvement: There should be a NOTE mentioning that the puppet is by default disabled and needs to be manually enabled.


Additional information: The NOTE should also be added to the Section "3.8. Installing and Configuring Puppet Agent Manually" in documentation: https://dxp-docp-prod.apps.ext-waf.spoke.prod.us-west-2.aws.paas.redhat.com/documentation/en-us/red_hat_satellite/6.14/html-single/managing_hosts/index?lb_target=preview#Installing_and_Configuring_Puppet_Agent_Manually_managing-hosts

https://github.com/theforeman/foreman-documentation/pull/2308
https://github.com/theforeman/foreman-documentation/pull/2309

Published:

- https://access.redhat.com/documentation/en-us/red_hat_satellite/6.14/html-single/administering_red_hat_satellite/index#Monitoring_Puppet_admin
- https://access.redhat.com/documentation/en-us/red_hat_satellite/6.14/html-single/administering_red_hat_satellite/index#increasing_the_logging_level_for_puppet_server
- https://access.redhat.com/documentation/en-us/red_hat_satellite/6.14/html-single/managing_hosts/index#installing-and-configuring-puppet-agent-during-host-registration_managing-hosts
- https://access.redhat.com/documentation/en-us/red_hat_satellite/6.14/html-single/managing_hosts/index#Installing_and_Configuring_Puppet_Agent_Manually_managing-hosts
- https://access.redhat.com/documentation/en-us/red_hat_satellite/6.14/html-single/managing_configurations_using_puppet_integration_in_red_hat_satellite/index#Installing_and_Configuring_Puppet_Agent_during_Host_Provisioning_managing-configurations-puppet