Normal Description of problem:
After OCP upgrade old lvms resource pods still present in 'Error' state
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Setup OCP 4.12 and install lvms stable released 4.12 2. Upgrade OCP cluster from 4.12 to 4.13 3. After OCP upgrade to 4.13 is successful, check lvms resource pods
Actual results:
Older lvms resource pods are present on cluster with states such as 'Error', 'ContainerStatusUnknown'
Expected results:
Only latest lvms resource pods with state 'Running' should be present
Additional info:
$ oc get pods -n openshift-storage NAME READY STATUS RESTARTS AGE lvms-operator-xxxxxxx-xxxxx 0/3 Completed 1 175m lvms-operator-xxxxxxx-xxxxx 0/3 ContainerStatusUnknown 4 (160m ago) 164m lvms-operator-xxxxxxx-xxxxx 3/3 Running 4 156m lvms-operator-xxxxxxx-xxxxx 0/3 Completed 0 158m topolvm-controller-xxxxxxx-xxxxx 5/5 Running 5 136m topolvm-controller-xxxxxxx-xxxxx 0/5 Error 0 163m topolvm-controller-xxxxxxx-xxxxx 0/5 Error 0 174m topolvm-controller-xxxxxxx-xxxxx 0/5 ContainerStatusUnknown 5 158m topolvm-node-xxxx 4/4 Running 5 158m vg-manager-xxxxx 1/1 Running 1 174m
- links to
-
RHBA-2024:126443
LVMS 4.15 Bug Fix and Enhancement update