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.
DescriptionBenjamin Chardi
2014-07-25 12:23:46 UTC
Description of problem:
We are building a Satellite6 HA environment for a customer that is going to manage around 8k RHEL servers. Our setting is running providing capsule load balanced services (puppetmaster + yum repos) to clients. In that scenario if one capsule goes down, the client connect to another capsule member of the cluster and the service is provided.
Puppet applies on our clients are done through running puppetruns from Foreman, an at this point this feature is not in HA.
In order to provide HA for puppetruns executed from Foreman (WEB or API) it will be very useful if Foreman is able to assing a list of capsules (instead of just one capsule as now) to a puppet client in order to run puppetruns on that client through the capsule from Foreman.
In the actual setting just one capsule can be assigned to one host, in that case if that capsule is down the puppetrun will fail.
If Foreman can is able to try in failover fashion puppetruns through a list of capsules then HA for puppetruns will be archived.
Comment 1RHEL Program Management
2014-07-25 12:43:44 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 3Daniel Lobato Garcia
2014-07-28 06:55:55 UTC
Just to clarify, "puppetruns" -> "puppet runs triggered through the smart proxy"
Comment 4Daniel Lobato Garcia
2014-07-28 06:56:09 UTC
Just to clarify, "puppetruns" -> "puppet runs triggered through the smart proxy"
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.