fix verified : OpenStack/14.0-RHEL-7/2019-03-05.1/ [root@controller-1 ~]# docker exec -it ab35dae516fe /bin/bash ()[neutron@controller-1 /]$ rpm -qa | grep ovn puppet-ovn-13.3.1-0.20181013120724.38e2e33.el7ost.noarch python-networking-ovn-5.0.2-0.20181217155313.726820a.el7ost.no (overcloud) [stack@undercloud-0 ~]$ openstack port list | grep 10.0.1.1 | 2089b8c2-ec77-4a56-bb4d-3ed86a73f48f | rhel76_vm2_net1_10.0.0.223 | fa:16:3e:6a:de:cd | ip_address='10.0.1.15', subnet_id='5f27615e-331b-4ecc-a279-155b91be3618' | ACTIVE | | ec1b8241-64ad-49dc-9c08-b8fc1039b1cd | | fa:16:3e:f2:2d:53 | ip_address='10.0.1.1', subnet_id='5f27615e-331b-4ecc-a279-155b91be3618' | ACTIVE | (overcloud) [stack@undercloud-0 ~]$ openstack port show ec1b8241-64ad-49dc-9c08-b8fc1039b1cd +-----------------------+---------------------------------------------------------------------------------+ | Field | Value | +-----------------------+---------------------------------------------------------------------------------+ | admin_state_up | UP | | allowed_address_pairs | | | binding_host_id | | | binding_profile | | | binding_vif_details | | | binding_vif_type | unbound | | binding_vnic_type | normal | | created_at | 2019-03-13T13:30:42Z | | data_plane_status | None | | description | | | device_id | 55cbf974-3cb6-44a8-b572-bfffb113dd91 | | device_owner | network:router_interface | | dns_assignment | fqdn='host-10-0-1-1.ovn.test.', hostname='host-10-0-1-1', ip_address='10.0.1.1' | | dns_domain | None | | dns_name | | | extra_dhcp_opts | | | fixed_ips | ip_address='10.0.1.1', subnet_id='5f27615e-331b-4ecc-a279-155b91be3618' | | id | ec1b8241-64ad-49dc-9c08-b8fc1039b1cd | | mac_address | fa:16:3e:f2:2d:53 | | name | | | network_id | 6c537ab3-c704-447f-8f61-c457a8e6f02b | | port_security_enabled | False | | project_id | cdf95993d6db4815a714151ec49c0ded | | qos_policy_id | None | | revision_number | 4 | | security_group_ids | | | status | ACTIVE | | tags | | | trunk_details | None | | updated_at | 2019-03-13T13:30:44Z |
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:0585