You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
manno
changed the title
OverrideTargets and clustersDesiredReady Count mismatch
[SURE-9111] OverrideTargets and clustersDesiredReady Count mismatch
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 thegitrepo.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 containsgitrepo.Status.Summary
, which consists of theready
anddesiredReady
for bundledeployments. The code assumes a bundle always changes after a bundledeployment changes and triggers the status update code that way.The text was updated successfully, but these errors were encountered: