-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: ensures SMCP is created before any other features #1118
fix: ensures SMCP is created before any other features #1118
Conversation
With the opendatahub-io#1052 refactoring, the order of features added to the Registry was accidentally changed. It results in failing of metrics collection feature which expects SMCP to be created first, but the creation runs afterwards. The setup is eventually consistent, as the reconcile will retry, so this not a bug per se, but results in unnecassary errors. This fix ensures features are ordered as before and levarages `.EnabledWhen` instead of wrapping features in `if`s.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: zdtsw The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test opendatahub-operator-e2e |
d6f25c7
into
opendatahub-io:incubation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think noticed this... but because of the pre/post conditions, my brain told me "meh, it doesn't matter"... xD
…o#1118) With the opendatahub-io#1052 refactoring, the order of features added to the Registry was accidentally changed. It results in failing of metrics collection feature which expects SMCP to be created first, but the creation runs afterwards. The setup is eventually consistent, as the reconcile will retry, so this not a bug per se, but results in unnecassary errors. This fix ensures features are ordered as before and levarages `.EnabledWhen` instead of wrapping features in `if`s. (cherry picked from commit d6f25c7)
…o#1118) With the opendatahub-io#1052 refactoring, the order of features added to the Registry was accidentally changed. It results in failing of metrics collection feature which expects SMCP to be created first, but the creation runs afterwards. The setup is eventually consistent, as the reconcile will retry, so this not a bug per se, but results in unnecassary errors. This fix ensures features are ordered as before and levarages `.EnabledWhen` instead of wrapping features in `if`s. (cherry picked from commit d6f25c7)
Description
With the #1052 refactoring, the order of features added to the Registry was accidentally changed. It results in failing of metrics collection feature which expects SMCP to be created first, but the creation runs afterwards. The setup is eventually consistent, as the reconcile will retry, so this not a bug per se, but results in unnecassary errors.
This fix ensures features are ordered as before and levarages
.EnabledWhen
instead of wrapping features inif
s.How Has This Been Tested?
BEFORE: Reconcile log
AFTER: Reconcile log
Screenshot or short clip
Merge criteria