Support for Quantum DB migrations was added in Grizzly, via the Alembic library (http://alembic.readthedocs.org/en/latest/).
Quality Engineering Management has reviewed and declined this request. You may appeal this decision by reopening this request.
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).
TCMS plan for checking the bug: https://tcms.engineering.redhat.com/plan/11710/openstackneutronupgrading-30-grizzly-quantum-to-40-havana-neutron#reviewcases
Created attachment 835831 [details] Important logs before upgrade Logs of system before upgrade
Created attachment 835835 [details] Important logs after all-at-once upgrade System logs after all-at-once upgrade
Created attachment 835836 [details] Sdiff between logs for all-at-once upgrade For easy reading, sdiff file between logs for all-at-once upgrade.
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).
Created attachment 838026 [details] Important logs before distributed upgrade Important logs before distributed upgrade
Created attachment 838027 [details] Important logs after distributed upgrade System logs after distributed upgrade
Created attachment 838028 [details] Sdiff between logs for distributed upgrade Sdiff for comfort reading for distributed upgrade
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).
Roey tested it scenario 1 & 2
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