Bug 1045034 - Review Request: openstack-neutron - check whether db needs to be upgraded
Summary: Review Request: openstack-neutron - check whether db needs to be upgraded
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: openstack-neutron
Version: 22
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Miguel Angel Ajo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-19 13:43 UTC by Jakub Libosvar
Modified: 2015-10-20 08:13 UTC (History)
7 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2015-10-20 08:13:18 UTC


Attachments (Terms of Use)
Patch for havana branch (6.83 KB, patch)
2014-01-16 15:12 UTC, Jakub Libosvar
no flags Details | Diff
Patch for icehouse branch (6.84 KB, patch)
2014-01-16 15:13 UTC, Jakub Libosvar
no flags Details | Diff
Patch for f20 branch (6.18 KB, patch)
2014-01-16 15:13 UTC, Jakub Libosvar
no flags Details | Diff

Description Jakub Libosvar 2013-12-19 13:43:56 UTC
Spec URL: http://mmagr.fedorapeople.org/downloads/jlibosva/el6/openstack-neutron.spec
SRPM URL: http://mmagr.fedorapeople.org/downloads/jlibosva/el6/openstack-neutron-2013.2-13.el6.src.rpm
Description: If neutron is upgraded from previous release (Grizzly) there
    needs to be run db upgrade before services are started. Starting
    services without upgrading db may lead into inconsistent behavior.
    Neutron service will not start if db is still from previous release
    while packages are from current release.
Fedora Account System Username: jlibosva

Comment 1 Michael S. 2013-12-25 10:30:51 UTC
That's not a new package, that's a patch against openstack-neutron so I reassign to the correct product. Could you please give the patch rather than the full spec, so people can review the change more easily ?

Comment 2 Jakub Libosvar 2014-01-16 15:12:51 UTC
Created attachment 851141 [details]
Patch for havana branch

Comment 3 Jakub Libosvar 2014-01-16 15:13:25 UTC
Created attachment 851142 [details]
Patch for icehouse branch

Comment 4 Jakub Libosvar 2014-01-16 15:13:52 UTC
Created attachment 851143 [details]
Patch for f20 branch

Comment 5 Miguel Angel Ajo 2014-03-11 15:04:29 UTC
OK, done for el6-havana http://koji.fedoraproject.org/koji/taskinfo?taskID=6621847

f20-havana, el6-icehouse, and f21-icehouse missing.

Comment 7 Ihar Hrachyshka 2014-10-20 10:19:45 UTC
Quoting Jakub from an email on the same topic:

"This script is added there because of upgrade from Grizzly to Havana.
Packstack in Grizzly didn't use neutron-db-manage to create schema and
thus following neutron-db-manage upgrade head failed due to absence of
stamp in database (i.e. alembic didn't know from which version it should
migrate).

In Icehouse when upgrading from Havana, user already has alembic stamp
(if it was deployed by packstack, it has stamp. If it is upgraded,
someone needed to provide stamp manually due to neutron-db-check) in
database so we don't need this script anymore."

I guess you can close the bug.

Comment 8 Jaroslav Reznik 2015-03-03 15:20:21 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 9 Miguel Angel Ajo 2015-10-20 08:13:18 UTC
Ok, closing this, as I understand we don't need it anymore.

(In reply to Ihar Hrachyshka from comment #7)
> Quoting Jakub from an email on the same topic:
> 
> "This script is added there because of upgrade from Grizzly to Havana.
> Packstack in Grizzly didn't use neutron-db-manage to create schema and
> thus following neutron-db-manage upgrade head failed due to absence of
> stamp in database (i.e. alembic didn't know from which version it should
> migrate).
> 
> In Icehouse when upgrading from Havana, user already has alembic stamp
> (if it was deployed by packstack, it has stamp. If it is upgraded,
> someone needed to provide stamp manually due to neutron-db-check) in
> database so we don't need this script anymore."
> 
> I guess you can close the bug.


Note You need to log in before you can comment on or make changes to this bug.