Back to bug 1331420
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Sahid Ferdjaoui | 2016-04-28 13:44:33 UTC | Status | NEW | ASSIGNED |
| Target Release | 7.0 (Kilo) | 9.0 (Mitaka) | ||
| Assignee | eglynn | sferdjao | ||
| Target Milestone | async | ga | ||
| Sahid Ferdjaoui | 2016-04-29 14:15:01 UTC | Status | ASSIGNED | MODIFIED |
| Fixed In Version | openstack-nova-13.0.0-2.el7ost | |||
| Jon Schlueter | 2016-05-03 16:02:44 UTC | Keywords | ZStream | |
| errata-xmlrpc | 2016-05-04 13:01:50 UTC | Status | MODIFIED | ON_QA |
| Prasanth Anbalagan | 2016-05-18 19:08:14 UTC | Status | ON_QA | VERIFIED |
| Sahid Ferdjaoui | 2016-07-22 15:10:12 UTC | Doc Text | Cause: Users want to boot in instance attached to a network with port security disable. When booting instances, Nova API automatically adds a default security group if nothing is specified which should not be done on a network with option 'port_security_enabled=False' Consequence: The boot process fails Fix: Make Nova to avoid adding a default security groups to a port created for an instance on a network with port_security_enabled=False Result: The boot process works as expected and the port attached to the instance does not have a default security groups attached. NOTE: a knowing bug in UI still indicates that a default security groups is attached to the instance but only the fist time, in return of the command to boot the instance. |
|
| errata-xmlrpc | 2016-08-11 01:52:03 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-08-11 12:18:01 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-08-11 08:18:01 UTC | |||
| Martin Lopes | 2016-08-15 04:13:16 UTC | CC | mlopes | |
| Doc Text | Cause: Users want to boot in instance attached to a network with port security disable. When booting instances, Nova API automatically adds a default security group if nothing is specified which should not be done on a network with option 'port_security_enabled=False' Consequence: The boot process fails Fix: Make Nova to avoid adding a default security groups to a port created for an instance on a network with port_security_enabled=False Result: The boot process works as expected and the port attached to the instance does not have a default security groups attached. NOTE: a knowing bug in UI still indicates that a default security groups is attached to the instance but only the fist time, in return of the command to boot the instance. | 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. |
||
| Derek | 2019-02-17 03:58:47 UTC | Keywords | FeatureBackport | |
| CC | dcadzow | |||
| Russell Bryant | 2019-09-09 16:57:58 UTC | CC | rbryant |
Back to bug 1331420