new instance isnt associated with a security group by default
Bug #670278 reported by
Avant Vyas
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_
Problem seems to be the following line of code (on trunk) in nova/compute/
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/
Cheers,
Related branches
lp:~vishvananda/nova/lp670278
- Devin Carlen (community): Approve
- Jay Pipes (community): Approve
-
Diff: 54 lines (+24/-2)2 files modifiednova/compute/manager.py (+3/-2)
nova/tests/compute_unittest.py (+21/-0)
Changed in nova: | |
assignee: | nobody → Vish Ishaya (vishvananda) |
importance: | Undecided → High |
Changed in nova: | |
status: | New → Fix Committed |
Changed in nova: | |
milestone: | none → 2011.1 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.