Bug 1374974

Summary:	[Neutron] [LBaaS] Test v1 to v2 migration script
Product:	Red Hat OpenStack	Reporter:	Nir Yechiel <nyechiel>
Component:	openstack-neutron-lbaas	Assignee:	Nir Magnezi <nmagnezi>
Status:	CLOSED WONTFIX	QA Contact:	Alexander Stafeyev <astafeye>
Severity:	high	Docs Contact:
Priority:	high
Version:	9.0 (Mitaka)	CC:	amedeo.salvati, amuller, apevec, jjoyce, lhh, nyechiel, tfreger
Target Milestone:	---	Keywords:	Triaged, ZStream
Target Release:	9.0 (Mitaka)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-neutron-lbaas-9.0.0-0.20160901145057.970dd37.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-07-17 14:56:14 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:

Description Nir Yechiel 2016-09-11 07:20:24 UTC

Description of problem:

LBaaS v1 is deprecated with Mitaka (RHOSP 9) and expected to be removed with Newton (RHOSP 10) in favor of the v2 API. There is a migration script to convert the DB from v1 to v2. This should allow customers which are running LBaaS v1 in RHOSP 9 to migrate to LBaaS v2 with RHOSP 10.

Script: https://review.openstack.org/#/c/289595/

Example usage: https://review.openstack.org/#/c/289595/11/tools/database-migration-from-v1-to-v2.py

Deprecation note: https://access.redhat.com/documentation/en/red-hat-openstack-platform/9/single/release-notes/#idm140025041831536

Comment 5 Alexander Stafeyev 2016-10-05 08:55:11 UTC

We tried to follow the steps in the patch in order to run the lbaas v1 to v2 (rhos9) upgrade.

We did not success : 
 - Create a revision file
 - Edit the created file and fill the content properly with this file
 - Run alembic upgrade head

I executed "neutron-db-manage revision -m "description of revision" --autogenerate" 

At this point I saw an error: 
ERROR [alembic.util.messaging] Multiple heads are present; please specify the head revision on which the new revision should be based, or perform a merge.
  FAILED: Multiple heads are present; please specify the head revision on which the new revision should be based, or perform a merge.
[
 but checking history and migration  ( neutron-db-manage check_migration and neutron-db-manage history) I saw no error.


NirM, If u can add some info regarding that from what you saw that would be great. 

tnx

Comment 6 Nir Magnezi 2016-10-05 13:04:23 UTC

@Alex,

I would say this didn't FailedQA, since you were not able to actually test the scrip in action, but rather NEEDINFO (from me).
The error you specified above is expected[1] and does not indicate the problem we ran into.

I will run some more tests and as soon as ready, I will provide the needed information

[1] http://docs.openstack.org/developer/neutron/devref/alembic_migrations.html#script-auto-generation

Comment 8 Assaf Muller 2017-03-15 20:29:32 UTC

The v2 code doesn't exist on OSP 10, so the migration will have to be run on 9. Interestingly the migration code itself is not available in OSP 9 and attempts to backport it upstream have failed, we'll have to backport it d/s only.

Comment 9 Assaf Muller 2017-07-17 14:56:14 UTC

Per agreement between PM and Engineering we won't be offering a migration path between LBaaS v1 and v2, nor between LBaaS v2 with haproxy to Octavia. We observed the customer demand and determined that it doesn't justify the return on investment, and we'd rather go all-in on Octavia to provide the best user experience possible for Octavia green-field deployments.