-
Notifications
You must be signed in to change notification settings - Fork 517
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Endless Rolling Restarts when using Tolerations #1344
Comments
@siegenthalerroger Thank you for raising this, it is indeed a bug addressed with #1346 . We're releasing a fix version shortly. |
fix #1346 seems working fine for me after upgrading to 0.8.2 version. |
@siegenthalerroger Closing this as it was addressed with the |
Also tested on my end, working as intended now :) |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
What did you do to encounter the bug?
Had a MongoDB resource with v0.8.0 like below (incomplete) and then upgraded to v0.8.1.
What did you expect?
The cluster to continue to operate with the newer operator.
What happened instead?
There was an endless rolling restart loop between the two replicas.
Downgrading to 0.8.0 rectified the issue.
I triaged this to be due to the operator repeatedly adding the "toleration" defined above to the StatefulSet, causing a state difference which k8s reconciled by triggering a rolling update. I suspect this bug was introduced by #1314.
Following a cleaned-up variant of the operator-reconciled mongo StatefulSet:
volumeClaimTemplates:
- kind: PersistentVolumeClaim
apiVersion: v1
metadata:
name: data-volume
creationTimestamp: null
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 30Gi
storageClassName: ssd-retained
volumeMode: Filesystem
status:
phase: Pending
- kind: PersistentVolumeClaim
apiVersion: v1
metadata:
name: logs-volume
creationTimestamp: null
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 2G
volumeMode: Filesystem
status:
phase: Pending
serviceName: mongodb-svc
podManagementPolicy: OrderedReady
updateStrategy:
type: RollingUpdate
revisionHistoryLimit: 10
The text was updated successfully, but these errors were encountered: