Bug 1160885

Summary: rabbitmq wont start if ssl is required
Product: [Community] RDO Reporter: Mohammed Arafa <bugzilla>
Component: openstack-packstackAssignee: Martin Magr <mmagr>
Status: CLOSED CURRENTRELEASE QA Contact: Shai Revivo <srevivo>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: aortega, derekh, frakka, jpena, pasik, srevivo
Target Milestone: ---   
Target Release: Juno   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-packstack-8.0.0-0.7.0rc2.el7.noarch Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-18 13:52:28 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:
Attachments:
Description Flags
rabbitmq-server log with erorr
none
rabbitmq-server log after deleting rabbitmq-env.conf none

Description Mohammed Arafa 2014-11-05 21:38:22 UTC 
Description of problem:

if the answer file has this line
CONFIG_AMQP_ENABLE_SSL=n
set to yes

rabbitmq will fail to start

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


How reproducible:
every _SINGLE_ time

Steps to Reproduce:
1.see above
2.
3.

Actual results:
fail

Expected results:
should work

Additional info:
Comment 1 Matteo Fracassetti 2015-01-25 01:32:11 UTC 
During setup, packstack creates two files in /etc/rabbitmq:

- rabbitmq-env.conf
- rabbitmq.config

rabbitmq-env.conf contains only one line, like that:

 RABBITMQ_NODE_PORT=5671

 In /var/log/rabbitmq/rabbit@<hostname>.log, the issue seems due to rabbitmq-server which tries to start a second instance of rabbitmq on the same port 5671, already in use so it reports a failure:


=INFO REPORT==== 25-Jan-2015::02:05:34 ===
stopped TCP Listener on [::]:5671

=INFO REPORT==== 25-Jan-2015::02:05:34 ===
Error description:
   {could_not_start,rabbit,
       {bad_return,
           {{rabbit,start,[normal,[]]},
            {'EXIT',
                {rabbit,failure_during_boot,
                    {case_clause,{error,{already_started,<0.195.0>}}}}}}}}


 Set the value of "RABBITMQ_NODE_PORT" in rabbitmq-env.conf to another value like, for example, "5672" (non-SSL listener) or (better) simply delete the file "rabbitmq-env.conf" or delete/comment the line with "RABBITMQ_NODE_PORT" (leaving it empty) avoid the issue and rabbitmq-server can be started with SSL and no errors:

[root@openstack etc]# grep -i SSL /var/log/rabbitmq/*
/var/log/rabbitmq/rabbit:started SSL Listener on [::]:5671


 The issue occurs on Red Hat/CentOS 7 with juno as with icehouse.
Comment 2 Matteo Fracassetti 2015-01-25 01:34:54 UTC 
Created attachment 983869 [details]
rabbitmq-server log with erorr
Comment 3 Matteo Fracassetti 2015-01-25 01:36:30 UTC 
Created attachment 983870 [details]
rabbitmq-server log after deleting rabbitmq-env.conf
Comment 4 Matteo Fracassetti 2015-01-25 02:18:33 UTC 
 The value of the setting in "rabbitmq-env.conf" is managed by this line in the default answer file: 

"CONFIG_AMQP_SSL_PORT=5671"

 Unfortunately, comment out this line in the answer file while CONFIG_AMQP_ENABLE_SSL=y does not do the trick (the rabbitmq-env.conf is still created with the default value 5671) and leave it empty is not an option because "NULL" is a value not allowed for this line by packstack.

 So seems that there are no quick workaround and a patch is needed to address the issue... The bug seems related to "Bug 1147224 - Packstack install AMQP with SSL, fails to start rabbitmq service" but is it abandoned?
Comment 7 Javier Peña 2016-05-18 13:52:28 UTC 
This issue was fixed between the Icehouse and Juno releases. Closing now.