Closed kornys closed 9 months ago
what is the "latest" referred here?
@zdtsw latest available image with incubation
tag
from: quay.io/opendatahub/opendatahub-operator:v2.4.0
to: quay.io/opendatahub/opendatahub-operator@sha256:2d569be2885ca4b5f83df6ddc1cf39052fb979ae11591f6be94863a9f9f9c789
i can confirm this is an issue, i will need to look into it.
the problem lies in the logic of operator we did not handle it for upstream upgrade from 2.4 to later version
to capture underlying problem: we have the selector change introduced in ODH v2.3 which should make a smooth upgrade from v2.3 to v2.4 but then we changed the selector again in post-v2.4 to match the logic from downstream v2.4 so now the gap is between ODH v2.4 to post-v2.4 and the logic cannot be easily re-use in ODH, so we will need another way to automatically perform upgrade or we ask user to set all components to Removed before upgrade to post-2.4
Customer will not change state to removed Im sure, so this has to be fixed in operator logic from my POV
just to explain another thing -> this upgrade worked 2days back. So some of the yesterday commit did the break.
just to explain another thing -> this upgrade worked 2days back. So some of the yesterday commit did the break.
we backported the code from downstream to upstream yesterday morning
yup I noticed that
@zdtsw this should be also migrated to jira right?
@zdtsw this should be also migrated to jira right?
yes, please. we should use jira for new issue creation.
@zdtsw created: https://issues.redhat.com/browse/RHOAIENG-965
since this is migrated to JIRA, I am closing it here :)
Describe the bug DSC during upgrade from odh 2.4 to latest main fails and all conditions in dsc are in failed state.
To Reproduce Steps to reproduce the behavior:
Operator Log:
DSC: