Bug 1964399 - OCP installation with kuryr failure - network operator degraded
Summary: OCP installation with kuryr failure - network operator degraded
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-networking-ovn
Version: 16.2 (Train)
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: Alpha
: 16.2 (Train on RHEL 8.4)
Assignee: Kamil Sambor
QA Contact: rlobillo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-25 12:08 UTC by Kamil Sambor
Modified: 2021-09-15 07:15 UTC (History)
22 users (show)

Fixed In Version: python-networking-ovn-7.4.2-2.20210601204817.el8ost.4
Doc Type: If docs needed, set a value
Doc Text:
-
Clone Of: 1937851
Environment:
Last Closed: 2021-09-15 07:15:18 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2021:3483 0 None None None 2021-09-15 07:15:40 UTC

Comment 17 rlobillo 2021-07-01 11:05:05 UTC
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).

Comment 21 errata-xmlrpc 2021-09-15 07:15:18 UTC
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


Note You need to log in before you can comment on or make changes to this bug.