Not planned
Description
What happened:
If a StatefulSet stucks at the failing init container - it's impossible to fix it via a redeploy.
What you expected to happen:
If a new version of StatefulSet is deployed - a new set of pods eventually should be created
How to reproduce it (as minimally and precisely as possible):
Here is a repository with all the necessary manifests https://github.com/zerkms/statefulset-init-stuck
Anything else we need to know?:
Environment:
- Kubernetes version (use
kubectl version): 1.14.1 - Cloud provider or hardware configuration: bare metal
- OS (e.g:
cat /etc/os-release): ubuntu bionic 18.04 - Kernel (e.g.
uname -a): 4.15.0-50-generic Update README.md #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux - Install tools: kubeadm
- Network plugin and version (if this is a network-related bug):
- Others:
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Closed
Milestone
Relationships
Development
Participants
Activity
zerkms commentedon May 17, 2019
/sig scheduling
draveness commentedon May 17, 2019
I could work on this and try to make a fix.
/assign
tedyu commentedon May 18, 2019
I guess by 'a never version' you mean 'a newer version'
[-]StatefulSet does not upgrade to a never version of manifests[/-][+]StatefulSet does not upgrade to a newer version of manifests[/+]draveness commentedon May 22, 2019
I opened a PR and reproduced the issue with e2e test in #78182
fejta-bot commentedon Aug 20, 2019
Issues go stale after 90d of inactivity.
Mark the issue as fresh with
/remove-lifecycle stale.Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with
/close.Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
zerkms commentedon Aug 20, 2019
/remove-lifecycle stale
73 remaining items
k8s-triage-robot commentedon Jan 22, 2024
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/staleis appliedlifecycle/stalewas applied,lifecycle/rottenis appliedlifecycle/rottenwas applied, the issue is closedYou can:
/remove-lifecycle stale/closePlease send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
zerkms commentedon Jan 23, 2024
Hello from 2024 :-)
/remove-lifecycle stale
k8s-triage-robot commentedon Apr 22, 2024
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/staleis appliedlifecycle/stalewas applied,lifecycle/rottenis appliedlifecycle/rottenwas applied, the issue is closedYou can:
/remove-lifecycle stale/closePlease send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
k8s-triage-robot commentedon May 22, 2024
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/staleis appliedlifecycle/stalewas applied,lifecycle/rottenis appliedlifecycle/rottenwas applied, the issue is closedYou can:
/remove-lifecycle rotten/closePlease send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
k8s-triage-robot commentedon Jun 21, 2024
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
lifecycle/staleis appliedlifecycle/stalewas applied,lifecycle/rottenis appliedlifecycle/rottenwas applied, the issue is closedYou can:
/reopen/remove-lifecycle rottenPlease send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
k8s-ci-robot commentedon Jun 21, 2024
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.