Bug 1200358 - Gutterball sometimes fails to start when system is restarted
Summary: Gutterball sometimes fails to start when system is restarted
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Reporting
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Michael Stead
QA Contact: Sachin Ghai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-10 11:59 UTC by Michael Stead
Modified: 2017-02-23 20:21 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-12 16:05:28 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Michael Stead 2015-03-10 11:59:44 UTC 
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:
Comment 1 Michael Stead 2015-03-10 12:05:49 UTC 
Awaiting review of PR https://github.com/candlepin/candlepin/pull/839
Comment 4 Sachin Ghai 2015-07-08 11:12:00 UTC 
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"
Comment 5 Bryan Kearney 2015-08-12 16:05:28 UTC 
This bug was fixed in Satellite 6.1.1 which was delivered on 12 August, 2015.
Note You need to log in before you can comment on or make changes to this bug.