OpenStack Compute (nova)

Create VM with no networks with Quantum Gives SecurityGroups Exception

Bug #1191044 reported by Brent Eagles
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Medium
Brent Eagles
OpenStack Compute (nova) 2013.2 "havana"
Grizzly
Fix Released
Medium
Aaron Rosen
OpenStack Compute (nova) 2013.1.3

Bug Description

If a user tries to create a VM when Quantum/OpenStack Networking is configured and the relevant tenant has not created a network, the operation results in a SecurityGroupNotFound exception. Somewhat misleading and unexpected.

Brent Eagles (beagles)
Changed in nova:
assignee: nobody → Brent Eagles (beagles)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

Fix proposed to branch: master
Review: https://review.openstack.org/33080

Changed in nova:
status: New → In Progress
Vish Ishaya (vishvananda)
Changed in nova:
importance: Undecided → Medium
tags: added: grizzly-backport-potential
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/33080
Committed: http://github.com/openstack/nova/commit/8f3b3db9b04bb5ff7b9486dc6fc211745b983855
Submitter: Jenkins
Branch: master

commit 8f3b3db9b04bb5ff7b9486dc6fc211745b983855
Author: Brent Eagles <email address hidden>
Date: Fri Jun 14 13:21:54 2013 -0230

    Skip security group code when there is no network.

    This patch adds a simple check to the nova/quantum API that immediately
    returns an empty list if there are no configured networks available.

    Fixes bug 1191044

    Change-Id: I34ac4dd56c71f99c7ed9ff632d6dc7036d91008d

Changed in nova:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (stable/grizzly)

Fix proposed to branch: stable/grizzly
Review: https://review.openstack.org/35207

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (stable/grizzly)

Reviewed: https://review.openstack.org/35207
Committed: http://github.com/openstack/nova/commit/d367ab62720988231524accab33488ed1d6c8555
Submitter: Jenkins
Branch: stable/grizzly

commit d367ab62720988231524accab33488ed1d6c8555
Author: Brent Eagles <email address hidden>
Date: Fri Jun 14 13:21:54 2013 -0230

    Skip security group code when there is no network.

    This patch adds a simple check to the nova/quantum API that immediately
    returns an empty list if there are no configured networks available.

    Fixes bug 1191044

    Change-Id: I34ac4dd56c71f99c7ed9ff632d6dc7036d91008d
    (cherry picked from commit 8f3b3db9b04bb5ff7b9486dc6fc211745b983855)

tags: added: in-stable-grizzly
Thierry Carrez (ttx)
Changed in nova:
milestone: none → havana-2
status: Fix Committed → Fix Released
Alan Pevec (apevec)
tags: removed: grizzly-backport-potential in-stable-grizzly
Thierry Carrez (ttx)
Changed in nova:
milestone: havana-2 → 2013.2
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to nova (master)

Related fix proposed to branch: master
Review: https://review.openstack.org/139712

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to nova (master)

Reviewed: https://review.openstack.org/139712
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4c49db4c9c550271c026742e3f09bb967d0627bd
Submitter: Jenkins
Branch: master

commit 4c49db4c9c550271c026742e3f09bb967d0627bd
Author: Joe Gordon <email address hidden>
Date: Fri Dec 5 14:04:42 2014 -0500

    downgrade 'No network configured!' to debug log level

    Based on the details in bug 1191044, a user can cause the warning
    'No network configured!' if they boot an instance in a tenant that
    has no neutron networks set up.

    Tempest doesn't create a network for every test that creates a nova
    instance. The lack of a network is not a sign of something wrong with
    nova so a warning log is too much. Move to debug instead.

    This should help reduce the amount of warnings that occur on every
    tempest run.

    Also drop the exclamation mark.

    Change-Id: I6bc4e46aa5a72645c72f7232627c7aa9efd2591d
    Related-Bug: #1191044

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.