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.
DescriptionAmaani S Karimi
2018-05-16 08:33:38 UTC
1. Proposed title of this feature request
3. What are the nature and description of the request?
1) Having slow or unreliable network between Satellite and Capsule
2) optionally pausing VM with Sat or Caps for some short time
3) Vmotion
all the above can cause inter-qdrouterd connections drop links, what makes impossible to install a package or errata via katello agent until the topology settles down back.
as a resolution below steps is need to be done:-
increase heartbeat parameters. helloInterval specifies the frequency in seconds of sending heartbeats from this router, while helloMaxAge specifies the timeout itself - if this router does not receive hello heartbeat from a peer within this timeout, all links to that peer are dropped, changing these parameters, adding in /etc/qpid-dispatch/qdrouterd.conf as mentioned below works fine but is not persistent.
router {
mode: interior
router-id: some.hostname.example.com
helloInterval: 10
helloMaxAge: 30
}
for more information refer:- https://access.redhat.com/solutions/3440201
4. Why does the customer need this? (List the business requirements here)
When a Capsule Sync is performed often vSphere will initiate a vMotion event against the Capsule due to its increased pulp worker workload. The default qdrouterd settings only allow for a 3-second wait for a heartbeat and that is not long enough. what makes impossible to install a package or errata via katello agent until the topology settles down back. and affect production environment.
5. How would the customer like to achieve this? (List the functional requirements here)
making (helloInterval and helloMaxAge ) entries in qdrouterd.conf works fine but are not permanent/persistent during upgrade.
These options (helloInterval and helloMaxAge ) should be made tunable as per requirement using custom-hiera.yaml
6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
They'd be available for testing this during development. if needed.
7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
NO
8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
At the earliest.
9. Is the sales team involved in this request and do they have any additional input?
No
10. List any affected packages or components.
NA
11. Would the customer be able to assist in testing this functionality if implemented?
Yes
1. Proposed title of this feature request 3. What are the nature and description of the request? 1) Having slow or unreliable network between Satellite and Capsule 2) optionally pausing VM with Sat or Caps for some short time 3) Vmotion all the above can cause inter-qdrouterd connections drop links, what makes impossible to install a package or errata via katello agent until the topology settles down back. as a resolution below steps is need to be done:- increase heartbeat parameters. helloInterval specifies the frequency in seconds of sending heartbeats from this router, while helloMaxAge specifies the timeout itself - if this router does not receive hello heartbeat from a peer within this timeout, all links to that peer are dropped, changing these parameters, adding in /etc/qpid-dispatch/qdrouterd.conf as mentioned below works fine but is not persistent. router { mode: interior router-id: some.hostname.example.com helloInterval: 10 helloMaxAge: 30 } for more information refer:- https://access.redhat.com/solutions/3440201 4. Why does the customer need this? (List the business requirements here) When a Capsule Sync is performed often vSphere will initiate a vMotion event against the Capsule due to its increased pulp worker workload. The default qdrouterd settings only allow for a 3-second wait for a heartbeat and that is not long enough. what makes impossible to install a package or errata via katello agent until the topology settles down back. and affect production environment. 5. How would the customer like to achieve this? (List the functional requirements here) making (helloInterval and helloMaxAge ) entries in qdrouterd.conf works fine but are not permanent/persistent during upgrade. These options (helloInterval and helloMaxAge ) should be made tunable as per requirement using custom-hiera.yaml 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. They'd be available for testing this during development. if needed. 7. Is there already an existing RFE upstream or in Red Hat Bugzilla? NO 8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? At the earliest. 9. Is the sales team involved in this request and do they have any additional input? No 10. List any affected packages or components. NA 11. Would the customer be able to assist in testing this functionality if implemented? Yes