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.
Description of problem:
After a system restart, Gutterball sometimes fails to start because the AMQP message broker may have not yet started yet.
Version-Release number of selected component (if applicable):
How reproducible:
90%
Steps to Reproduce:
1. Restart the entire system
2. check the status of the gutterball server to make sure that is is Ok.
Actual results:
Gutterball will fail to start up. Checking the logs shows that it couldn't connect to the AMQP message broker.
Expected results:
Gutterball should start up normally and start serving reports via the API.
Additional info:
Verified with sat6.1.1 snap11 c2.
I rebooted the system. and after reboot I can see the gutterball.
~]# curl -k https://localhost:8443/gutterball/status
{
"version" : "1.0.15.0",
"release" : "1",
"request_locale" : "en_US"