-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
Bug Tracking
-
2
-
False
-
-
False
-
?
-
rhos-storage-integration
-
None
-
-
-
-
Storage Integration Sprint 18
-
1
-
Moderate
The ci_lvms_storage role can fail intermittently when the LVMCluster CRD has not been fully registered by the Kubernetes API server at the time the LVMCluster CR is applied.
Observed behavior:
- LVMCluster stuck in Progressing state with ResourcesSyncIncomplete
- Error message references cannot find RESTMapping for APIVersion lvm.topolvm.io/v1alpha1 Kind LVMCluster
- The role times out after 10 minutes
- The LVMCluster may self-heal hours later after the operator pod restarts
status: conditions: - lastTransitionTime: '2026-02-11T02:35:08Z' message: |- Resources have not yet been fully synced to the cluster: LVMCluster's resources are not yet fully synchronized: csi node master-0 does not have driver topolvm.io lvmvgnodestatus failed to reconcile: lvmvolumegroupnodestatuses.lvm.topolvm.io "master-0" is forbidden: cannot set blockOwnerDeletion in this case because cannot find RESTMapping for APIVersion lvm.topolvm.io/v1alpha1 Kind LVMCluster: no matches for kind "LVMCluster" in version "lvm.topolvm.io/v1alpha1" lvmvg-manager failed to reconcile: lvmvolumegroups.lvm.topolvm.io "local-storage" is forbidden: cannot set blockOwnerDeletion in this case because cannot find RESTMapping for APIVersion lvm.topolvm.io/v1alpha1 Kind LVMCluster: no matches for kind "LVMCluster" in version "lvm.topolvm.io/v1alpha1" vg-manager failed to reconcile: daemonsets.apps "vg-manager" is forbidden: cannot set blockOwnerDeletion in this case because cannot find RESTMapping for APIVersion lvm.topolvm.io/v1alpha1 Kind LVMCluster: no matches for kind "LVMCluster" in version "lvm.topolvm.io/v1alpha1" reason: ResourcesSyncIncomplete status: 'False' type: ResourcesAvailable - lastTransitionTime: '2026-02-11T02:35:08Z' message: VG readiness check is still in progress reason: VGReadinessInProgress status: 'False' type: VolumeGroupsReady state: Progressing
Expected behavior:
The role should wait for the LVMCluster CRD to be fully established before creating the LVMCluster CR.
Environment:
- OCP 4.18
- LVMS Operator 4.18.4
- ci-framework main branch
