Bug 958568

Summary: Upgrades from RHOS 3.0 Quantum to RHOS 4.0 Neutron (configuration, database migrations)
Product: Red Hat OpenStack Reporter: Maru Newby <mnewby>
Component: openstack-neutronAssignee: Jakub Libosvar <jlibosva>
Status: CLOSED ERRATA QA Contact: Roey Dekel <rdekel>
Severity: medium Docs Contact:
Priority: high    
Version: 3.0CC: aberezin, chrisw, jkt, jlibosva, jruzicka, kbasil, lpeer, mnewby, oblaut, sclewis, sgordon
Target Milestone: rcKeywords: FutureFeature, Reopened
Target Release: 4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-neutron-2013.2-4 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-20 00:01:48 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: 989729, 989731, 989732    
Bug Blocks: 975499, 1005583    
Attachments:
Description Flags
Important logs before upgrade
none
Important logs after all-at-once upgrade
none
Sdiff between logs for all-at-once upgrade
none
Important logs before distributed upgrade
none
Important logs after distributed upgrade
none
Sdiff between logs for distributed upgrade none

Description Maru Newby 2013-05-01 20:30:56 UTC
Support for Quantum DB migrations was added in Grizzly, via the Alembic library (http://alembic.readthedocs.org/en/latest/).

Comment 10 RHEL Program Management 2013-08-07 13:06:30 UTC
Quality Engineering Management has reviewed and declined this request.
You may appeal this decision by reopening this request.

Comment 13 Maru Newby 2013-09-17 07:44:32 UTC
There is a working group planning on documenting the upgrade path in the RDO wiki.  There does not appear to be sufficient resources to pursue an automated solution this cycle.  Validation of the Neutron upgrade, therefore, will need to be undertaken according to the documentation in question (once it exists).

Comment 22 Roey Dekel 2013-12-12 14:29:55 UTC
Created attachment 835831 [details]
Important logs before upgrade

Logs of system before upgrade

Comment 23 Roey Dekel 2013-12-12 14:31:35 UTC
Created attachment 835835 [details]
Important logs after all-at-once upgrade

System logs after all-at-once upgrade

Comment 24 Roey Dekel 2013-12-12 14:33:09 UTC
Created attachment 835836 [details]
Sdiff between logs for all-at-once upgrade

For easy reading, sdiff file between logs for all-at-once upgrade.

Comment 25 Roey Dekel 2013-12-12 14:41:11 UTC
All-at-once upgrade:
====================
Verified on Grizzly -> Havana with  :

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
Grizzly Puddle: 2013-11-14.2
Havana Puddle: 2013-12-11.1

Results:
--------
As can be seen in the attachments the upgrade works in this case. instances worked and had connection (ingress and egress).

Comment 26 Roey Dekel 2013-12-17 23:13:25 UTC
Created attachment 838026 [details]
Important logs before distributed upgrade

Important logs before distributed upgrade

Comment 27 Roey Dekel 2013-12-17 23:14:29 UTC
Created attachment 838027 [details]
Important logs after distributed upgrade

System logs after distributed upgrade

Comment 28 Roey Dekel 2013-12-17 23:15:52 UTC
Created attachment 838028 [details]
Sdiff between logs for distributed upgrade

Sdiff for comfort reading for distributed upgrade

Comment 29 Roey Dekel 2013-12-17 23:18:07 UTC
Distributed upgrade:
====================
Verified on Grizzly -> Havana with  :

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
Grizzly Puddle: 2013-11-14.2
Havana Puddle: 2013-12-16.1

Results:
--------
As can be seen in the attachments the upgrade works in this case. instances worked and had connection (ingress and egress).

Comment 30 Ofer Blaut 2013-12-18 12:57:44 UTC
Roey tested it  scenario 1 & 2

Comment 32 errata-xmlrpc 2013-12-20 00:01:48 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.

http://rhn.redhat.com/errata/RHEA-2013-1859.html