-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.15
-
None
-
Important
-
Yes
-
OTA 253
-
1
-
Rejected
-
False
-
Description of problem:
No metadataURI in updateservice resource.
# ./oc get updateservice update-service-oc-mirror -n openshift-update-service -ojson|jq .status
{
"conditions": [
{
"lastHeartbeatTime": "2024-05-06T07:56:12Z",
"lastTransitionTime": "2024-05-06T07:56:12Z",
"reason": "Success",
"status": "True",
"type": "ReconcileCompleted"
},
{
"lastHeartbeatTime": "2024-05-06T07:56:12Z",
"lastTransitionTime": "2024-05-06T07:56:12Z",
"reason": "CACertFound",
"status": "True",
"type": "RegistryCACertFound"
}
],
"policyEngineURI": "https://update-service-oc-mirror-route-openshift-update-service.apps.jliu416.qe.devcluster.openshift.com"
}
#./oc get CustomResourceDefinition updateservices.updateservice.operator.openshift.io -oyaml|grep metadataURI
#
Version-Release number of selected component (if applicable):
cincinnati-operator-bundle-container-v5.0.3-3 cincinnati-operator-container-v5.0.3-4 cincinnati-container-v5.0.3-4
How reproducible:
always
Steps to Reproduce:
1. Install osus operator v5.0.3 on ocp v4.15
2. mirror ocp release image and graph-data/signatures with prepared imageset-config.yaml file by oc-mirror
3. create osus instance with the updateservice.yaml file generated in step 2
Actual results:
No metadataURI in updateservice resource.
Expected results:
There should be metadataURI in updateservice resource.
Additional info:
The issue has been caught during pre-merge test against OTA-1014 and fixed in https://github.com/openshift/cincinnati-operator/pull/179.