yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #51359
[Bug 1560506] Re: Nova does not honour security group specified during nova boot
[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]
** Changed in: nova
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1560506
Title:
Nova does not honour security group specified during nova boot
Status in OpenStack Compute (nova):
Expired
Bug description:
Nova does not honour security group specified during nova boot
Description:
========
1.created a network n1
2.create a neutron port with network n1
3.create a custom security group s1 with icmp protocol
4.boot a vm with port created in step 2 and security group specified as s1
we see that first security group s1 is considered however,once vm is
active we see that it is overwritten by default security group.due to
this vm is not pingable(I do not have icmp rule in my default security
group)
While booting vm Nova should perform neutron port update as security
group is explicitly mentioned.
This issue was found in liberty,however it may be same issue in mitaka as well
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1560506/+subscriptions
References