Bug 1936342: kuryr-controller restarting after 3 days cluster running - pools without members
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kuryr-kubernetes |
Fix Committed
|
Undecided
|
Sarka Scavnicka |
Bug Description
Created attachment 1761526 [details]
kuryr controller logs
Description of problem:
After 4.8.0-0.
$ openstack loadbalancer pool show a8bf9c07-
+------
| Field | Value |
+------
| admin_state_up | True |
| created_at | 2021-03-05T11:16:10 |
| description | |
| healthmonitor_id | |
| id | a8bf9c07-
| lb_algorithm | ROUND_ROBIN |
| listeners | 80708599-
| loadbalancers | b1a3ee03-
| members | |
| name | openshift-
| operating_status | ONLINE |
| project_id | cb736c7b6ada442
| protocol | TCP |
| provisioning_status | ACTIVE |
| session_persistence | None |
| updated_at | 2021-03-05T11:16:17 |
| tls_container_ref | None |
| ca_tls_
| crl_container_ref | None |
| tls_enabled | False |
+------
The issue was resolved by removing two svc (and letting kuryr-controller to recreate them):
- openshift-
- openshift-
Version-Release number of selected component (if applicable): OCP4.8.
How reproducible: Unknown
Steps to Reproduce:
Install cluster and let it running 2-3 days.
Actual results: kuryr-controller restarting.
(shiftstack) [stack@undercloud-0 network]$ oc get pods -n openshift-kuryr
NAME READY STATUS RESTARTS AGE
kuryr-cni-4d76c 1/1 Running 1 2d21h
kuryr-cni-4j58w 1/1 Running 1 2d21h
kuryr-cni-7f6dt 1/1 Running 0 2d21h
kuryr-cni-qg9wm 1/1 Running 0 2d21h
kuryr-cni-qwfqw 1/1 Running 0 2d21h
kuryr-cni-r5ddr 1/1 Running 1 2d21h
kuryr-controlle
Expected results: kuryr-controller stable.
Additional info: kuryr-controller logs + must-gather.
Changed in kuryr-kubernetes: | |
assignee: | nobody → Sarka Scavnicka (scavnicka) |
Changed in kuryr-kubernetes: | |
status: | New → Incomplete |
status: | Incomplete → Fix Committed |
This issue was fixed in the openstack/ kuryr-kubernete s 4.0.0.0rc1 release candidate.