-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.14
-
None
-
Quality / Stability / Reliability
-
False
-
-
5
-
Moderate
-
No
-
None
-
None
-
None
-
OTA 268
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
The in-cluster resource openshift-machine-api-gcp CredentialsRequest does not have the capability.openshift.io/name: MachineAPI annotation, while the post-upgrade extracted manifest 0000_30_machine-api-operator_00_credentials-request.yaml has it.
//post-upgrade:
# ./oc get clusterversion version -o json | jq -r ".status.capabilities.enabledCapabilities"[ "CSISnapshot", "Console", "Insights", "MachineAPI", "NodeTuning", "Storage", "baremetal", "marketplace", "openshift-samples"]
# ./oc2 adm release extract --to post-upgrade-gcp-v4.13-basecap-include-creds --included --credentials-requests
# cat post-upgrade-gcp-v4.13-basecap-include-creds/0000_30_machine-api-operator_00_credentials-request.yaml|grep -A4 annotations:
annotations:
capability.openshift.io/name: MachineAPI
exclude.release.openshift.io/internal-openshift-hosted: "true"
include.release.openshift.io/self-managed-high-availability: "true"
labels:
As above, the new gained cap MachineAPI can be found in post-upgrade extracted CredentialsRequest manifest. But the annotation missing in the in-cluster resource.
# ./oc2 -n openshift-cloud-credential-operator get CredentialsRequest openshift-machine-api-gcp -ojson|jq .metadata.annotations
{
"exclude.release.openshift.io/internal-openshift-hosted": "true",
"include.release.openshift.io/self-managed-high-availability": "true"
}
Version-Release number of selected component (if applicable):
4.14.0-0.nightly-2023-08-08-222204
How reproducible:
always
Steps to Reproduce:
1. Upgrade a gcp cluster with v4.13 set in baselineCapabilitySet from v4.13 to v4.14 2. 3.
Actual results:
No MachineAPI annotation in openshift-machine-api-gcp CredentialsRequest
Expected results:
In-cluster resource openshift-machine-api-gcp CredentialsRequest should respect to the target CR manifest.
Additional info:
//there is cap annotation for another in-cluster resource
# ./oc2 -n openshift-cloud-credential-operator get CredentialsRequest openshift-gcp-pd-csi-driver-operator -ojson|jq .metadata.annotations
{
"capability.openshift.io/name": "Storage",
"include.release.openshift.io/self-managed-high-availability": "true",
"include.release.openshift.io/single-node-developer": "true"
}