Comment 4 for bug 1354050
Revision history for this message
| Dmitry Mescheryakov (dmitrymex) wrote | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
Together with other MOS team members we had a conversation in skype chat and identified both the problem and solution:
The reason of the failure is that Neutron's migrations were not run during 5.0 environment installation. I.e. the Neutron DB was created from metadata, and not by running 'neutron-db-manage upgrade head'. To patch environment to 5.0.2, fuel runs 'neutron-db-manage upgrade head' and it fails because the DB is already created, but it does not have a migrations stamp.
The solution is to run 'neutron-db-manage stamp head' prior to patching. Note that this command _must not_ be run before initial installation, only before the upgrade.