registry team mailing list archive
-
registry team
-
Mailing list archive
-
Message #26368
[Bug 670278] [NEW] new instance isnt associated with a security group by default
Public bug reported:
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,
** Affects: nova
Importance: Undecided
Status: New
--
new instance isnt associated with a security group by default
https://bugs.launchpad.net/bugs/670278
You received this bug notification because you are a member of Registry
Administrators, which is subscribed to OpenStack.
Follow ups
References