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

AtlasDeployment stuck in deployment is updating state #2106

Open
vmanikes opened this issue Feb 8, 2025 · 3 comments
Open

AtlasDeployment stuck in deployment is updating state #2106

vmanikes opened this issue Feb 8, 2025 · 3 comments

Comments

@vmanikes
Copy link

vmanikes commented Feb 8, 2025

What did you do to encounter the bug?
Steps to reproduce the behavior:
I have a deployment with autoscaling enabled

            autoScaling:
              compute:
                enabled: true
                maxInstanceSize: M20
                minInstanceSize: M10
                scaleDownEnabled: true
              diskGB:
                enabled: true

Now when I change scaleDownEnabled: false, the deployment is stuck in updating state

NAME         READY   ATLAS STATE   MONGODB VERSION
data-vault   False   UPDATING      8.0.4

And when I describe

Events:
  Type    Reason              Age                     From             Message
  ----    ------              ----                    ----             -------
  Normal  DeploymentUpdating  4m47s (x3600 over 32d)  AtlasDeployment  deployment is updating

What did you expect?
Deployment should have been updated successfully

What happened instead?
Deployment is stuck in a loop

Operator Information

  • 2.6.0
@vmanikes
Copy link
Author

vmanikes commented Feb 9, 2025

This is definitely a bug. To disable autoscaling I had to remove the autoscaling block from the spec entirely and I had to look at the source code to comprehend this.

P.S the autoscaling actually gets disabled when I set autoscaling.enabled = false but the deployment never becomes ready

@helderjs
Copy link
Collaborator

Hi @vmanikes,
Thanks for the report. We are actively looking into the issue.

@helderjs
Copy link
Collaborator

Hi @vmanikes!

Thank you, again, for bringing this issue to our attention. Our team has successfully reproduced the error, and we can confirm it is a bug. As a temporary workaround, you can remove autoscaling configuration and add it back once the cluster is idle, as you have already discovered. Our team is actively investigating a more permanent solution by assessing the possibility of removing the validation constraints around autoscaling without impacting the usability of the resource. Please note that developing and testing a proper fix might take some time. We appreciate your patience and will keep you updated on our progress.

@helderjs helderjs reopened this Feb 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants