Verified on RHOS-16.2-RHEL-8-20210623.n.1. Installing 4.8.0-rc.0 which contains https://github.com/openshift/kuryr-kubernetes/pull/521 so we look for the log line on kuryr-controller pod to identify if the issue has happened: #!/bin/bash export KUBECONFIG=/home/stack/ostest/auth/kubeconfig while(true); do date -u oc get pods -n openshift-kuryr -l app=kuryr-controller -o NAME echo "trunk ports down:" source ~/shiftstackrc && openstack port list --device-owner "trunk:subport" -f value | grep DOWN echo "issue detected on kuryr-controller:" RESULT=$(oc logs -n openshift-kuryr $(oc get pods -n openshift-kuryr -l app=kuryr-controller -o NAME) | grep "This is a Neutron issue") if [[ $RESULT -eq 1 ]] then echo $RESULT fi echo "####" echo sleep 5 done The issue (w/o fix) was observed randomly on hybrid setup and on DSAL box. Therefore, we tested in both setups for verification (w fix) and the problem was not hit over several OCP installations in loop: - on DSAL box with RHOS-16.2-RHEL-8-20210623.n.1, we run 65 successful installations and neither the log line on kuryr controller or hung trunk:subports were detected during installation. (Logs on http://file.rdu.redhat.com/rlobillo/monitor_BZ1964399.log.gz) - on Hybrid setup (titan26) we run 10 successful installations and neither the log line on kuryr controller or hung trunk:subports were detected (logs on http://file.rdu.redhat.com/rlobillo/hybrid_monitor_BZ1964399.tgz).
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 (Red Hat OpenStack Platform (RHOSP) 16.2 enhancement 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/RHEA-2021:3483