Bug 981028

Summary: Instance boot fails when security groups enabled and no network created
Product: Red Hat OpenStack Reporter: Scott Lewis <sclewis>
Component: openstack-novaAssignee: RHOS Maint <rhos-maint>
Status: CLOSED ERRATA QA Contact: Ami Jeain <ajeain>
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: afazekas, apevec, bperkins, chrisw, dallan, jkt, jliberma, jturner, ndipanov, sclewis, sgordon, yeylon
Target Milestone: asyncKeywords: ZStream
Target Release: 3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-nova-2013.1.2-4.el6ost Doc Type: Bug Fix
Doc Text:
The "default" OpenStack Networking security group is created automatically when creating a tenant network. The Compute service previously always checked for the presence of this "default" security group when launching instances. As a result launching a virtual machine instance when no tenant network had been created ended in error: SecurityGroupNotFound: Security group default not found. The Compute service has been updated to only check for the existence of the "default" security group when a tenant network for the instance to use exists.
 Story Points: ---
Clone Of: 971082 Environment:
Last Closed: 2013-07-10 15:43:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 971082    
Bug Blocks:    

Comment 2 Ami Jeain 2013-07-04 12:17:21 UTC 
#  quantum security-group-list
+--------------------------------------+---------+-------------+
| id                                   | name    | description |
+--------------------------------------+---------+-------------+
| 6bb1532c-87d7-42f5-9957-abeccda97758 | default | default     |
+--------------------------------------+---------+-------------+
Comment 3 errata-xmlrpc 2013-07-10 15:43:09 UTC 
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/RHBA-2013-1020.html