OpenStack Compute (nova)

nova-api/compute cannot start in stable/folsom branch with quantum

Bug #1081434 reported by Akihiro Motoki
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
Undecided
Unassigned
Folsom
Fix Released
Critical
Gary Kotton
OpenStack Compute (nova) 2012.2.1

Bug Description

In Today's stable/folsom branch when Quantum enabled, nova-api and nova-compute fail to start.

Recenty 7948b7a572e33e3fd541e27f2617d832eb43b504 (Proxy floating IP calls to quantum) is backported into stable/folsom in commit 3f7788ca4310a7fa34b7687ff6e41f8de4d2cadc. This causes this bug.

"Proxy floating IP calls to quantum" requires commit 31764456bd4536c920fb1d768fbdebf93e016a8a (Stop network.api import on network import; https://review.openstack.org/#/c/13912/).

See original description
Akihiro Motoki (amotoki)
description: updated
Akihiro Motoki (amotoki)
summary: - nova-api cannot start in stable/folsom branch with quantum
+ nova-api/compute cannot start in stable/folsom branch with quantum
Akihiro Motoki (amotoki)
description: updated
Revision history for this message
Salvatore Orlando (salvatore-orlando) wrote :

It seems that all we need to do is to propose the patch pointed out by Akihiro for merge into stable/folsom.
Is that correct, Akihiro?

Revision history for this message
Salvatore Orlando (salvatore-orlando) wrote :

never mind, garyk already took care of it: https://review.openstack.org/#/c/16631/

Thierry Carrez (ttx)
Changed in nova:
status: New → Invalid
Revision history for this message
Mark McLoughlin (markmc) wrote :

https://review.openstack.org/16631 merged

Mark McLoughlin (markmc)
tags: removed: folsom-backport-potential
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.