-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.19.0
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
Yes
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
TechPreviewNoUpgrade cluster, monitoring upgrade from 4.19.0-ec.1 to 4.19.0-0.nightly-2025-02-11-161912 is failed due to Invalid value v1 in clustermonitoring crd, orginal file is 0000_10_config-operator_01_clustermonitoring-TechPreviewNoUpgrade.crd.yaml
checked from must-gather
$ omc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.19.0-ec.1 True True 3m30s Unable to apply 4.19.0-0.nightly-2025-02-11-161912: some cluster configuration is invalid
$ omc get featuregate cluster -ojsonpath='{.spec.featureSet}'
TechPreviewNoUpgrade
$ omc get clusterversion -oyaml
...
- lastTransitionTime: "2025-02-13T08:42:56Z"
message: '{"message":"Could not update customresourcedefinition \"clustermonitoring.config.openshift.io\"
(40 of 966): the object is invalid, possibly due to local cluster configuration","children":[{"message":"CustomResourceDefinition.apiextensions.k8s.io
\"clustermonitoring.config.openshift.io\" is invalid: status.storedVersions[0]:
Invalid value: \"v1\": must appear in spec.versions"}],"manifest":{"originalFilename":"0000_10_config-operator_01_clustermonitoring-TechPreviewNoUpgrade.crd.yaml","group":"apiextensions.k8s.io","kind":"CustomResourceDefinition","name":"clustermonitoring.config.openshift.io"}}'
reason: IssuesFound
status: "True"
type: ReconciliationIssues
checked the clustermonitoring crd from must-gather, status.storedVersions[0] is v1, same as spec.versions
$ omc get crd clustermonitoring.config.openshift.io -oyaml ... spec: ... versions: - name: v1 schema: openAPIV3Schema: ... status: ... storedVersions: - v1
Version-Release number of selected component (if applicable):
TechPreviewNoUpgrade cluster, monitoring failed to upgrade from 4.19.0-ec.1 to 4.19.0-0.nightly-2025-02-11-161912
also checked in the TechPreviewNoUpgrade 4.19.0-0.nightly-2025-02-11-161912 cluster, status.storedVersions[0] is v1alpha1, same as spec.versions, not v1
$ oc get featuregate cluster -ojsonpath='{.spec.featureSet}'
TechPreviewNoUpgrade
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.19.0-0.nightly-2025-02-11-161912 True False 10h Cluster version is 4.19.0-0.nightly-2025-02-11-161912
$ omc get crd clustermonitoring.config.openshift.io -oyaml
...
spec:
...
versions:
- name: v1alpha1
schema:
openAPIV3Schema:
...
status:
...
storedVersions:
- v1alpha1
the change is brought by https://github.com/openshift/api/pull/2155, I doubt if we upgrade from the TechPreviewNoUpgrade cluster which contains the fix, should be upgrade successfully.
How reproducible:
always
Steps to Reproduce:
1. TechPreviewNoUpgrade cluster, upgrade from 4.19.0-ec.1 to 4.19.0-0.nightly-2025-02-11-161912
Actual results:
TechPreviewNoUpgrade cluster, monitoring failed to upgrade from 4.19.0-ec.1 to 4.19.0-0.nightly-2025-02-11-161912
Expected results:
no error
Additional info:
only affect 4.19 TechPreviewNoUpgrade cluster
