new instance isnt associated with a security group by default

Bug #670278 reported by Avant Vyas
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
High
Vish Ishaya

Bug Description

when I create an instance, using euca-run.. the instance isnt associated with the default security group.. select * from security_group_instance_association returns an empty set.

Problem seems to be the following line of code (on trunk) in nova/compute/manager.py:

Line 91 : the code tries to get sec_groups from kwargs when it is already explicitly a kwarg.

(Thanks vishy for pointing this out)

I removed this line, restarted nova-api and security groups started working again. After this fix, instances were allocated to the 'default' security group correctly.

For more information/context, please contact vishy or me on irc.

Cheers,

Related branches

Changed in nova:
assignee: nobody → Vish Ishaya (vishvananda)
importance: Undecided → High
Changed in nova:
status: New → Fix Committed
Thierry Carrez (ttx)
Changed in nova:
milestone: none → 2011.1
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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