-
Notifications
You must be signed in to change notification settings - Fork 154
fix: upgrade workspace status condition correctly #1758
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
base: main
Are you sure you want to change the base?
fix: upgrade workspace status condition correctly #1758
Conversation
TitleFix workspace status conditions and node readiness verification Description
Changes walkthrough 📝
|
PR Reviewer Guide 🔍Here are some key observations to aid the review process:
|
PR Code Suggestions ✨Explore these optional code suggestions:
|
Signed-off-by: rambohe-ch <[email protected]>
1a902d6 to
4580c16
Compare
Reason for Change:
fix some bugs according to E2E failure: https://github.com/kaito-project/kaito/actions/runs/21513080521/job/61984690966?pr=1747#step:16:5812
ResourcesReady is set true initially when neither of ConditionTypeNodeClaimStatus and ConditionTypeNodeStatus exist. the logs as follows:
skip set ConditionTypeResourceStatus condition when owned conditions don't exist.
Related services are created just after NodesReady condition is true. and then ResourcesReady will never be set to true, because workload creation will block the reconciliation.
so E2E test will timeout for resource status checking.

go forward to workload reconcilation before ConditionTypeResourceStatus condition is true
Requirements
Issue Fixed:
Notes for Reviewers: