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

Old replica sets not always scaling down after update from 1.6.6 to 1.7.1 #3762

Closed
jmansar-fm opened this issue Aug 2, 2024 · 2 comments · Fixed by #3784
Closed

Old replica sets not always scaling down after update from 1.6.6 to 1.7.1 #3762

jmansar-fm opened this issue Aug 2, 2024 · 2 comments · Fixed by #3784
Assignees
Labels
bug Something isn't working

Comments

@jmansar-fm
Copy link

Describe the bug

After upgrading from 1.6.6 to 1.7.1 we've noticed that occasionally when deploying and promoting releases the old ReplicaSet does not get scaled down. The old pods keep running indefinitely. Though they do not receive any traffic as active/preview services correctly point to a new ReplicaSet

To Reproduce

The issue is hard to replicate since it happens sporadically.

  • Make a new revision of a rollout with blue/green strategy and ephemeral labels configured, auto promotion disabled.
  • Promote a new revision

Version
1.7.1

Logs
controller-deployment.log

It looks like the controller sets scale-down-deadline annotation correctly to 30 seconds forward. Few lines below the ReplicaSet gets patched without changing scale-down-deadline annotation. But then after few more lines it makes another patch operation with scale-down-deadline set to an empty string, which I think is the problem.

From this point of time, the controller keeps setting the deadline date and resetting it to the empty string.

time="2024-08-01T15:13:06Z" level=info msg="Set 'scale-down-deadline' annotation on 'ui-widgets-684cf6478b' to 2024-08-01T15:13:36Z (30s)" namespace=default rollout=ui-widgets
(...)

time="2024-08-01T15:13:06Z" level=info msg="Conflict when updating replicaset ui-widgets-684cf6478b, falling back to patch" namespace=default rollout=ui-widgets
time="2024-08-01T15:13:06Z" level=info msg="Patching replicaset with patch: {\"metadata\":{\"annotations\":{\"rollout.argoproj.io/desired-replicas\":\"1\",\"rollout.argoproj.io/revision\":\"59\"},\"labels\":{\"rollouts-pod-template-hash\":\"684cf6478b\"}},\"spec\":{\"replicas\":1,\"selector\":{\"matchLabels\":{\"rollouts-pod-template-hash\":\"684cf6478b\"}},\"template\":{\"metadata\":{\"labels\":{\"app\":\"ui-widgets\",\"release\":\"ui-widgets\",\"rollouts-pod-template-hash\":\"684cf6478b\"}}}}}" namespace=default rollout=ui-widgets

(...)
time="2024-08-01T15:13:06Z" level=info msg="Conflict when updating replicaset ui-widgets-684cf6478b, falling back to patch" namespace=default rollout=ui-widgets
time="2024-08-01T15:13:06Z" level=info msg="Patching replicaset with patch: {\"metadata\":{\"annotations\":{\"rollout.argoproj.io/desired-replicas\":\"1\",\"rollout.argoproj.io/revision\":\"59\",\"scale-down-deadline\":\"\"},\"labels\":{\"rollouts-pod-template-hash\":\"684cf6478b\"}},\"spec\":{\"replicas\":1,\"selector\":{\"matchLabels\":{\"rollouts-pod-template-hash\":\"684cf6478b\"}},\"template\":{\"metadata\":{\"labels\":{\"app\":\"ui-widgets\",\"release\":\"ui-widgets\",\"rollouts-pod-template-hash\":\"684cf6478b\"}}}}}" namespace=default rollout=ui-widgets


I had a look at the recent changes to see what might cause this to happen. There was a new function added that is responsible for patching the replica set - updateReplicaSetFallbackToPatch

I suspect the problem lies on the following line

patchRS.Annotations[v1alpha1.DefaultReplicaSetScaleDownDeadlineAnnotationKey] = rs.Labels[v1alpha1.DefaultReplicaSetScaleDownDeadlineAnnotationKey]

It copies the annotation from rs.Labels instead of rs.Annotations

if _, found := rs.Annotations[v1alpha1.DefaultReplicaSetScaleDownDeadlineAnnotationKey]; found {
                patchRS.Annotations[v1alpha1.DefaultReplicaSetScaleDownDeadlineAnnotationKey] = rs.Labels[v1alpha1.DefaultReplicaSetScaleDownDeadlineAnnotationKey]
}

Though, it's not clear to me what is the exact flow that triggers this issue intermittently.


Message from the maintainers:

Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.

@jmansar-fm jmansar-fm added the bug Something isn't working label Aug 2, 2024
@zachaller zachaller self-assigned this Aug 5, 2024
@zachaller
Copy link
Collaborator

Yup that is an issue it should be Annotations

@zachaller
Copy link
Collaborator

#3774

agaudreault added a commit to agaudreault/argo-rollouts that referenced this issue Aug 12, 2024
zachaller pushed a commit that referenced this issue Aug 12, 2024
…3784)

dco

Signed-off-by: Alexandre Gaudreault <alexandre_gaudreault@intuit.com>
zachaller pushed a commit that referenced this issue Aug 13, 2024
…3784)

dco

Signed-off-by: Alexandre Gaudreault <alexandre_gaudreault@intuit.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants