Bug 1128910

Summary: celerybeat service reports incorrect configuration on startup
Product: Red Hat Satellite Reporter: Mark Lamourine <mlamouri>
Component: OtherAssignee: Katello Bug Bin <katello-bugs>
Status: CLOSED DEFERRED QA Contact: Katello QA List <katello-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.0.4CC: bbuckingham, bkearney, mmccune
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1172745 (view as bug list) Environment:
Last Closed: 2014-12-19 16:48:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1172745    

Description Mark Lamourine 2014-08-11 19:47:50 UTC
Description of problem:

Celerybeat incorrectly reports the message broker URL on startup.
The reported URL is always localhost

Version-Release number of selected component (if applicable):

Pulp 2.4

How reproducible:

Set the broker_url value in /etc/pulp/server.conf to non-default
Start the Celery service

Steps to Reproduce:
1. Set the broker_url value in /etc/pulp/server.conf to non-default
2. Start the Celery service
3. Observe the startup messages

Actual results:

celery beat v3.1.11 (Cipater) is starting.
__    -    ... __   -        _
Configuration ->
    . broker -> amqp://guest@localhost:5672//
...


Expected results:

celery beat v3.1.11 (Cipater) is starting.
__    -    ... __   -        _
Configuration ->
    . broker -> qpid://guest@myqpidhost:5672/


Additional info:

Comment 1 RHEL Program Management 2014-08-11 19:53:47 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 3 Mike McCune 2014-12-19 16:48:57 UTC
Will track this in the upstream bug only as this doesn't impact Satellite 6 directly.