Bug 1331420
Summary: | backport to kilo: nova should not add default security group to quantum unless api-request had it | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Sahid Ferdjaoui <sferdjao> |
Component: | openstack-nova | Assignee: | Sahid Ferdjaoui <sferdjao> |
Status: | CLOSED ERRATA | QA Contact: | Prasanth Anbalagan <panbalag> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 9.0 (Mitaka) | CC: | berrange, bschmaus, dasmith, dcadzow, dmaley, ebarrera, eglynn, jschluet, kchamart, kimi.zhang, majopela, mlopes, nlevinki, panbalag, sbauza, scorcora, sferdjao, sgordon, skinjo, srevivo, tbowling, vromanso |
Target Milestone: | ga | Keywords: | FeatureBackport |
Target Release: | 9.0 (Mitaka) | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | openstack-nova-13.0.0-2.el7ost | Doc Type: | Bug Fix |
Doc Text: |
Previously, when booting instances, the nova API automatically added a default security group if nothing was specified, which should not be done on a network with option 'port_security_enabled=False'
Consequently, the boot process would fail for users booting an instance that was attached to a network with port security disabled.
With this update, nova no longer adds a default security group to a port created for an instance on a network with port_security_enabled=False
As a result, the boot process works as expected, and the port attached to the instance does not have a default security group attached.
NOTE: a known bug in the dashboard still indicates that a default security group is attached to the instance, but this only occurs during the first attempt at booting the instance.
|
Story Points: | --- |
Clone Of: | 1331418 | Environment: | |
Last Closed: | 2016-08-11 12:18:01 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: | 1291210, 1331418 | ||
Bug Blocks: |
Comment 2
Prasanth Anbalagan
2016-05-18 19:08:14 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. https://rhn.redhat.com/errata/RHEA-2016-1597.html |