-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.20.z
-
None
-
None
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Install v5.0.3 osus from default redhat-operators catalogsource, and then updating channel/name/source/startingCSV of the subscription to align with osus-fbc catalogsource, no upgrade is available.
# ./oc -n openshift-marketplace get catalogsource osus-fbc -ojson|jq .spec
{
"displayName": "OSUS Test CatalogSource",
"image": "quay.io/redhat-user-workloads/osus-tenant/osus-fbc@sha256:ad429b07b63897ffb4bef5592bc1c1fa8a3f888b1d42ca2de9bc6c159eaccb17",
"publisher": "Red Hat",
"sourceType": "grpc"
}
The subscription after installing v5.0.3 with default redhat-operators catalogsource:
# ./oc -n openshift-update-service get sub cincinnati-operator -ojson|jq .spec
{
"channel": "v1",
"installPlanApproval": "Manual",
"name": "cincinnati-operator",
"source": "redhat-operators",
"sourceNamespace": "openshift-marketplace",
"startingCSV": "update-service-operator.v5.0.3"
}
Update channel/name/source/startingCSV of above subscription to align with osus-fbc:
# ./oc -n openshift-update-service get sub cincinnati-operator -ojson|jq .spec
{
"channel": "stable",
"installPlanApproval": "Manual",
"name": "osus-operator",
"source": "osus-fbc",
"sourceNamespace": "openshift-marketplace",
"startingCSV": "update-service-operator.v5.0.4"
}
The osus-fbc appears to lack a defined update path. Additionally, the channel and package name within the osus-fbc image built by Konflux seem to have changed unexpectedly.
Version-Release number of selected component (if applicable):
osus-fbc:quay.io/redhat-user-workloads/osus-tenant/osus-fbc@sha256:ad429b07b63897ffb4bef5592bc1c1fa8a3f888b1d42ca2de9bc6c159eaccb17 osus-bundle:quay.io/redhat-user-workloads/osus-tenant/osus-operator-metadata-bundle@sha256:808cab9fae01f1304989b9e83a5cd2bb60f8281c8906f2c6c31d362a71062567 osus-operator:quay.io/redhat-user-workloads/osus-tenant/osus-operator@sha256:dd6f7cb9041b27e4d89419dc041d593c8c84cf55739e1d152b5a4b7b38ebf41f osus-operand:quay.io/redhat-user-workloads/osus-tenant/osus-operand@sha256:89e62572118bfa635b0b1e3b88674a4fb0807dd70ed46b39597a958301285a71
How reproducible:
always
Steps to Reproduce:
1. create osus-fbc catalogsource with osus-fbc image
2. install v5.0.3 through default redhat-operators catalogsource
3. update the subscription to align with osus-fbc catalogsource and check for available update
Actual results:
No installplan for the v5.0.4 is available
Expected results:
osus should be upgraded from v5.0.3 to v5.0.4
Additional info: