Verified Using: OCP 4.6.0-0.nightly-2021-07-07-181104 $ openstack port list --device-owner "trunk:subport" -f value --os-cloud standalone_028_openshift |grep DOWN 6860d51a-36fa-403c-b182-871f3ffb4b58 fa:16:3e:8c:e4:ad [{'subnet_id': '4b68133f-8691-4473-847f-7e72b5ece261', 'ip_address': '10.128.10.146'}] DOWN d1d3fa54-415a-4aec-881e-cdbc959594da fa:16:3e:55:8a:91 [{'subnet_id': '65a3e49b-e6f1-4f53-8700-3ed451c65846', 'ip_address': '10.128.49.154'}] DOWN $ oc logs kuryr-controller-74b6868f76-89fgv -n openshift-kuryr |grep -i subport 2021-07-08 07:06:55.661 1 WARNING kuryr_kubernetes.controller.drivers.nested_vlan_vif [-] Subport a1e312b6-3795-421b-85c7-2783df70f3d1 is in DOWN status for more than 129 seconds. This is a Neutron issue. Attempting to reattach the subport to trunk df5c6240-758c-4682-8e55-fd6152dbe5ef using VLAN ID 3987 to fix it.: kuryr_kubernetes.exceptions.ResourceNotReady: Resource not ready: VIFVlanNested(active=False,address=fa:16:3e:00:de:24,has_traffic_filtering=False,id=a1e312b6-3795-421b-85c7-2783df70f3d1,network=Network(4baf7cad-356c-4793-bc1c-b2131133b6d7),plugin='noop',port_profile=<?>,preserve_on_delete=False,vif_name='tapa1e312b6-37',vlan_id=3987) 2021-07-08 07:06:56.922 1 WARNING kuryr_kubernetes.controller.drivers.nested_vlan_vif [-] Reattached subport a1e312b6-3795-421b-85c7-2783df70f3d1, its state will be rechecked when event will be retried.: kuryr_kubernetes.exceptions.ResourceNotReady: Resource not ready: VIFVlanNested(active=False,address=fa:16:3e:00:de:24,has_traffic_filtering=False,id=a1e312b6-3795-421b-85c7-2783df70f3d1,network=Network(4baf7cad-356c-4793-bc1c-b2131133b6d7),plugin='noop',port_profile=<?>,preserve_on_delete=False,vif_name='tapa1e312b6-37',vlan_id=3987)
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 (OpenShift Container Platform 4.6.38 bug fix update), 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-2021:2641