Bug 1749744
Summary: | Ports created by bulk operation are assigned default security group apart from the requested sg | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Jon Uriarte <juriarte> |
Component: | openstack-neutron | Assignee: | Nate Johnston <njohnston> |
Status: | CLOSED ERRATA | QA Contact: | Candido Campos <ccamposr> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 15.0 (Stein) | CC: | amuller, atragler, bcafarel, chrisw, dmacpher, njohnston, racedoro, scohen, skaplons |
Target Milestone: | z1 | Keywords: | Triaged, ZStream |
Target Release: | 15.0 (Stein) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openstack-neutron-14.0.3-0.20190913160457.0f4f48c.el8ost | Doc Type: | Bug Fix |
Doc Text: |
When you supplied a security group during bulk port creation, the resulting ports received both the requested security group and the tenant default security group. This fix changes the behavior so only the requested security group is assigned. This ensures the correct security group applies during bulk port creation.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2019-10-03 08:42:25 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: |
Description
Jon Uriarte
2019-09-06 11:03:00 UTC
Quick test on master devstack, I can reproduce with: $ cat bulk_secgroups.json { "ports": [ { "network_id": "226ac6be-753b-46d3-8636-5ad226297ab0", "security_groups": ["91e47ea5-3d9c-437b-a31e-0a2fd8d3181f"] } ] } $ export MY_TOKEN=$(openstack token issue -c id -f value) $ curl -H "X-Auth-Token: $MY_TOKEN" -X POST http://127.0.0.1:9696/v2.0/ports -d @bulk_secgroups.json | jq .ports[0].id "91ec92c1-4d9c-4a8b-b5d1-55769c4c75c2" openstack port show 91ec92c1-4d9c-4a8b-b5d1-55769c4c75c2|grep security_group | security_group_ids | 91e47ea5-3d9c-437b-a31e-0a2fd8d3181f, fc3f8c84-118e-46c5-8dc7-18d02ef926af $ openstack security group show default -f value -c id fc3f8c84-118e-46c5-8dc7-18d02ef926af Fix is waiting on CI upstream, and then we should be able to fast-track it's backports upstream and downstream. Verified on OSP 15 compose RHOS_TRUNK-15.0-RHEL-8-20190924.n.2 with openstack-neutron-14.0.3-0.20190923200444.5eb234b.el8ost.noarch Verified with Bernard's reproducer: $ cat bulk_secgroups.json { "ports": [ { "network_id": "ab8b704e-d5b0-441a-9b5e-1b24e7bd2822", "security_groups": ["a616bb52-b406-4da5-9540-374fde36de68", "c638097d-9713-45f4-adf5-1ef3339e71df", "e443f68c-1a50-489e-bdd4-e3c0b33b5af3"] } ] } $ export MY_TOKEN=$(openstack token issue -c id -f value) $ curl -H "X-Auth-Token: $MY_TOKEN" -X POST http://10.46.22.33:9696/v2.0/ports -d @bulk_secgroups.json | jq .ports[0].id % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 1165 100 934 100 231 679 168 0:00:01 0:00:01 --:--:-- 680 "93be83d3-6b5d-4e8e-a3da-a31bde933df0" $ openstack port show 93be83d3-6b5d-4e8e-a3da-a31bde933df0 | grep security_group | security_group_ids | a616bb52-b406-4da5-9540-374fde36de68, c638097d-9713-45f4-adf5-1ef3339e71df, e443f68c-1a50-489e-bdd4-e3c0b33b5af3 | $ openstack security group show default -f value -c id 643dea5a-ceb4-4585-86a9-aa8188ce3431 The default security group is not being assigned now to the created port. Namespace isolation is achieved now in OCP on OSP with Kuryr (verified in openshift-ansible-3.11.146). Pods created in different namespaces cannot reach each other. $ oc new-project ns1 $ oc run --image kuryr/demo pod1 $ oc new-project ns2 $ oc run --image kuryr/demo pod2 $ oc -n ns1 get pod -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE pod1-1-2c9bd 1/1 Running 0 4m 10.11.14.158 app-node-1.openshift.example.com <none> $ oc -n ns2 get pod -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE pod2-1-6xdh5 1/1 Running 0 2m 10.11.15.23 app-node-0.openshift.example.com <none> $ oc -n ns1 rsh pod1-1-2c9bd ping 10.11.15.23 -c1 PING 10.11.15.23 (10.11.15.23): 56 data bytes --- 10.11.15.23 ping statistics --- 1 packets transmitted, 0 packets received, 100% packet loss command terminated with exit code 1 $ oc -n ns2 rsh pod2-1-6xdh5 ping 10.11.14.158 -c1 PING 10.11.14.158 (10.11.14.158): 56 data bytes --- 10.11.14.158 ping statistics --- 1 packets transmitted, 0 packets received, 100% packet loss command terminated with exit code 1 Pods cannot ping between them. 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://access.redhat.com/errata/RHBA-2019:2957 |