Bug 1323197

Summary: erlang crashes during a compute scaled out operation. [osp9]
Product: Red Hat OpenStack Reporter: Lon Hohberger <lhh>
Component: rabbitmq-serverAssignee: Peter Lemenkov <plemenko>
Status: CLOSED ERRATA QA Contact: Udi Shkalim <ushkalim>
Severity: urgent Docs Contact:
Priority: high    
Version: 7.0 (Kilo)CC: apevec, fahmed, fdinitto, jbiao, jeckersb, jjoyce, lhh, mfuruta, morazi, mschuppe, nlevinki, ohochman, pcaruana, plemenko, rcernin, srevivo
Target Milestone: ga   
Target Release: 9.0 (Mitaka)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: rabbitmq-server-3.3.5-22.el7ost Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1319334 Environment:
Last Closed: 2016-08-11 12:15:52 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:
Bug Depends On: 1319334    
Bug Blocks:    

Comment 7 Udi Shkalim 2016-06-01 09:08:52 UTC 
The scenario: scale compute-node (N->N+1) -> check that rabbit-service is still running
worked well on my environment with director 9.0 puddle - 2016-05-26.1.
 
[root@overcloud-controller-1 ~]# rpm -qa | grep rabbit
rabbitmq-server-3.6.2-3.el7ost.noarch


post-scale:
-------------
Scale Command : openstack overcloud deploy --templates --control-scale 3 --compute-scale 2 --ceph-storage-scale 2   --neutron-network-type vxlan --neutron-tunnel-types vxlan  --ntp-server 10.5.26.10 --timeout 90 -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml -e network-environment.yaml

Stack overcloud UPDATE_COMPLETE
Overcloud Endpoint: http://10.19.184.210:5000/v2.0
Overcloud Deployed

27-     Started: [ overcloud-controller-0 overcloud-controller-1 overcloud-controller-2 ]
28: Clone Set: rabbitmq-clone [rabbitmq]
29-     Started: [ overcloud-controller-0 overcloud-controller-1 overcloud-controller-2
Comment 9 errata-xmlrpc 2016-08-11 12:15:52 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://rhn.redhat.com/errata/RHEA-2016-1597.html