Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1134027

Summary:	[Docs] [Upgrade] Qpid to rabbit migration (as part of completing upgrade process)
Product:	Red Hat OpenStack	Reporter:	Dafna Ron <dron>
Component:	documentation	Assignee:	RHOS Documentation Team <rhos-docs>
Status:	CLOSED CURRENTRELEASE	QA Contact:	RHOS Documentation Team <rhos-docs>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	5.0 (RHEL 6)	CC:	adahms, ddomingo, dron, lars, srevivo
Target Milestone:	---	Keywords:	Documentation, ZStream
Target Release:	5.0 (RHEL 6)
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-08 12:37:45 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:	1134988, 1134990, 1135011
Bug Blocks:

Description Dafna Ron 2014-08-26 16:13:27 UTC

Description of problem:

I was using the below guide to migrate qpid to rabbit as part of the rhos 4.0 to rhos 5.0 upgrade process. 

https://access.redhat.com/articles/1167113

when we try to start the rabbit server we fail since qpid is still listening to the same port rabbit is trying to connect to. 

speaking to Lars, he will add some instructions and they should be added to the guide. 


failure happens when we try to start rabbit as stated in step 4: 

[root@gizmo ~(keystone_admin)]# service rabbitmq-server start
Starting rabbitmq-server: FAILED - check /var/log/rabbitmq/startup_{log, _err}
rabbitmq-server.

Comment 1 Lars Kellogg-Stedman 2014-08-27 03:03:40 UTC

Dafna,

Here's a first draft of the qpid -> rabbitmq migration instructions:

http://people.redhat.com/~lkellogg/rhos5-upgrade-docs/qpid-to-rabbitmq.html

Comment 5 Mike McCune 2016-03-28 23:26:37 UTC

This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 6 Andrew Dahms 2016-08-08 12:37:45 UTC

This bug applies to the OSP 4 to OSP 5 upgrade scenario.

Closing.