Bug 1610371 - Candlepin stops sending messages to katello, resulting in subscription info not being updated in Satellite
Summary: Candlepin stops sending messages to katello, resulting in subscription info n...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Candlepin
Version: 6.4
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: 6.4.0
Assignee: Kevin Howell
QA Contact: Perry Gagne
URL:
Whiteboard:
Depends On: 1624447 1624449
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-31 13:43 UTC by Perry Gagne
Modified: 2019-11-05 23:31 UTC (History)
6 users (show)

Fixed In Version: candlepin-2.4.7-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1624446 1624447 1624449 (view as bug list)
Environment:
Last Closed: 2018-10-16 19:01:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
VDC showing correctly. (103.61 KB, image/png)
2018-08-07 16:02 UTC, Stephen Benjamin 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 24681 0 None None None 2018-08-22 08:52:09 UTC

Comment 4 Stephen Benjamin 2018-08-07 16:02:25 UTC 
Created attachment 1474035 [details]
VDC showing correctly.
Comment 6 Stephen Benjamin 2018-08-07 18:07:34 UTC 
Closing as WORKSFORME, as Perry and I talked on IRC and neither of us can reproduce this anymore.
Comment 11 Walden Raines 2018-08-22 08:52:08 UTC 
Created redmine issue https://projects.theforeman.org/issues/24681 from this bug
Comment 13 Kevin Howell 2018-08-31 15:38:21 UTC 
Also appears to affect 6.3. The cause is: for bug 1564087, we set the global connection overall connection TTL for connections in HornetQ/Artemis to 24 hours. However, in HornetQ 2.4.7 (in 6.3) and Artemis (Candlepin master), the "invm" connection type that we use does not use a connection ttl by default, and does not behave well when it is set globally.
Comment 14 Patrick Creech 2018-09-24 14:46:36 UTC 
snap 23, not 63
Comment 16 Bryan Kearney 2018-10-16 19:01:49 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, 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/RHSA-2018:2927
Note You need to log in before you can comment on or make changes to this bug.