Skip to content
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

[SURE-9111] OverrideTargets and clustersDesiredReady Count mismatch #2995

Open
manno opened this issue Oct 24, 2024 · 0 comments
Open

[SURE-9111] OverrideTargets and clustersDesiredReady Count mismatch #2995

manno opened this issue Oct 24, 2024 · 0 comments
Assignees
Labels

Comments

@manno
Copy link
Member

manno commented Oct 24, 2024

Could be related to rancher/dashboard#12232, rancher/rancher#46916, rancher/dashboard#11643

The calculation of gitrepo status fields has several problems:

It seems the clustersDesiredReady count does not work with the overrideTargets option. The result is set in the gitrepo.Status.DesiredReadyClusters.

Furthermore, the gitops controller, does not trigger for bundledeployment changes, but the resourceKey and "Bundle" condition are computed from bundledeployments. The "Bundle" condition contains gitrepo.Status.Summary, which consists of the ready and desiredReady for bundledeployments. The code assumes a bundle always changes after a bundledeployment changes and triggers the status update code that way.

@manno manno added this to Fleet Oct 24, 2024
@manno manno converted this from a draft issue Oct 24, 2024
@manno manno added kind/bug JIRA Must shout labels Oct 24, 2024
@manno manno changed the title OverrideTargets and clustersDesiredReady Count mismatch [SURE-9111] OverrideTargets and clustersDesiredReady Count mismatch Oct 24, 2024
@manno manno self-assigned this Oct 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: 🏗 In progress
Development

No branches or pull requests

1 participant