Bug 2030486 - [4.9] Do not restart Kuryr-Controller when LB is stuck in PENDING_UPDATE state or Neutron port is DOWN
Summary: [4.9] Do not restart Kuryr-Controller when LB is stuck in PENDING_UPDATE stat...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.9.z
Assignee: Robin Cernin
QA Contact: Itzik Brown
URL:
Whiteboard:
Depends On:
Blocks: 2028307
TreeView+ depends on / blocked
 
Reported: 2021-12-08 22:26 UTC by Robin Cernin
Modified: 2023-09-15 01:18 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2028307
Environment:
Last Closed: 2022-01-04 18:41:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2021:5214 0 None None None 2022-01-04 18:41:49 UTC

Description Robin Cernin 2021-12-08 22:26:08 UTC
This is already fixed in 4.9, we need this BZ for QA to verify this on 4.9 and then we can verify the same way on 4.8

+++ This bug was initially created as a clone of Bug #2028307 +++

Description of problem:

This is back port of 

https://review.opendev.org/c/openstack/kuryr-kubernetes/+/812246 +
https://review.opendev.org/c/openstack/kuryr-kubernetes/+/796881

into 4.8, the same code + prometheus are present in 4.9 and 4.10

Version-Release number of selected component (if applicable):

4.8

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Itzik Brown 2021-12-16 16:41:27 UTC
1. Created a service.
2. The stopped the Kuryr controller
   oc -n openshift-cluster-version scale deploy cluster-version-operator --replicas 0
   oc -n openshift-network-operator scale deploy network-operator --replicas 0
   oc -n openshift-kuryr scale deploy kuryr-controller --replicas 0
3. Checked that the Kuryr controller  is down

4. Updated the Loadbalancer provisioning status to PENDING_UPDATE

. ~/stackrc && ssh heat-admin@$(openstack server list -f value -c Name -c Networks | grep controller-0 | awk -F= '{print $2}')

   sudo podman exec -it galera-bundle-podman-2 mysql (maybe different)

   use octavia;
   MariaDB [octavia]> update load_balancer set provisioning_status='PENDING_UPDATE' where id='<LB ID>';

5. Started the controller 
   oc -n openshift-kuryr scale deploy kuryr-controller --replicas 1
   oc -n openshift-network-operator scale deploy network-operator --replicas 1
   oc -n openshift-cluster-version scale deploy cluster-version-operator --replicas 1

6. Checked that the controller is Ready and in the log I saw
   kuryr_kubernetes.exceptions.LoadBalancerNotReady: Resource not ready: 'Loadbalancer 744181c0-04d3-4b67-b477-99a8336a5645    is stuck in PENDING_UPDATE status for several minutes


Verified:
OCP 4.9.0-0.nightly-2021-12-15-103522
OSP RHOS-16.1-RHEL-8-20211126.n.1

Comment 5 errata-xmlrpc 2022-01-04 18:41:24 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 (OpenShift Container Platform 4.9.12 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:5214

Comment 6 Red Hat Bugzilla 2023-09-15 01:18:01 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days


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