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

Fleet controller and agent update status field too often #3004

Closed
1 task done
aruiz14 opened this issue Oct 24, 2024 · 1 comment
Closed
1 task done

Fleet controller and agent update status field too often #3004

aruiz14 opened this issue Oct 24, 2024 · 1 comment
Assignees
Labels

Comments

@aruiz14
Copy link
Contributor

aruiz14 commented Oct 24, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

I've observed an abnormal number of status updates in some BundleDeployments objects.
While comparing them, I noticed that both Fleet's agent and controller are fighting to update the same field:

@@ -314,6 +314,19 @@
       fieldsType: FieldsV1
       fieldsV1:
         f:status:
+          f:appliedDeploymentID: {}
+          f:nonModified: {}
+          f:ready: {}
+          f:release: {}
+          f:resources: {}
+      manager: fleetagent
+      operation: Update
+      subresource: status
+      time: "2024-10-23T06:17:26Z"
+    - apiVersion: fleet.cattle.io/v1alpha1
+      fieldsType: FieldsV1
+      fieldsV1:
+        f:status:
           .: {}
           f:conditions: {}
           f:display:
@@ -321,27 +334,14 @@
             f:deployed: {}
             f:monitored: {}
             f:state: {}
+          f:syncGeneration: {}
       manager: fleetcontroller
       operation: Update
       subresource: status
-      time: "2024-10-23T06:17:06Z"
-    - apiVersion: fleet.cattle.io/v1alpha1
-      fieldsType: FieldsV1
-      fieldsV1:
-        f:status:
-          f:appliedDeploymentID: {}
-          f:nonModified: {}
-          f:ready: {}
-          f:release: {}
-          f:resources: {}
-          f:syncGeneration: {}
-      manager: fleetagent
-      operation: Update
-      subresource: status
-      time: "2024-10-23T06:17:26Z"
+      time: "2024-10-23T06:17:30Z"

Expected Behavior

fleetcontroller should respect the existing value in the status.

Steps To Reproduce

No response

Environment

- Fleet Version: 0.10.2

Logs

No response

Anything else?

No response

@aruiz14
Copy link
Contributor Author

aruiz14 commented Oct 24, 2024

/backport v2.9.4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

No branches or pull requests

3 participants