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://access.redhat.com/documentation/en-us/reference_architectures/2017/html-single/deploying_a_highly_available_red_hat_satellite_server_6_environment/
Section Number and Name:
4.5.5. Creating Pacemaker Resources
Also for the constraints
Describe the issue: The pulp_streamer service has no resource created in the cluster so the service is not started upon failover.
Suggestions for improvement:
# pcs resource create rs_pulp_streamer systemd:pulp_streamer op monitor interval=10s op start interval=0s timeout=100s op stop interval=0s timeout=100s
# pcs constraint colocation set fs_pulp fs_wwwpulp rs_pulp_streamer
# pcs constraint order set sat_vg fs_pulp fs_wwwpulp rs_pulp_workers rs_pulp_celerybeat rs_pulp_streamer
# pcs constraint order set rs_puppet rs_dhcp rs_named rs_pgsql sequential=false set rs_mongodb set rs_qpidd rs_qdrouterd sequential=false set rs_tomcat rs_pulp_workers rs_pulp_celerybeat rs_pulp_resource_manager rs_pulp_streamer rs_foreman-proxy sequential=false set rs_httpd rs_foreman-tasks sequential=false
Additional information:
This is just what I expect to be there for the pulp_streamer service to be working correctly in cluster
This bug was raised against the document "Deploying a Highly Available Red Hat Satellite Server 6 Environment", for which customers are now being asked to contact Red Hat (either their account team or consulting team) directly for assistance.
Because the product documentation team is unable to process this request, and in consultation with the Reference Architecture team, I am now closing this bug.
See the following article for more information -
https://access.redhat.com/solutions/1603283