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

Jump to bottom

failed to "StartContainer" for "etcd" with CrashLoopBackOff Ubuntu:17.10 #62904

Closed
haddada opened this issue Apr 20, 2018 · 5 comments
Closed

failed to "StartContainer" for "etcd" with CrashLoopBackOff Ubuntu:17.10 #62904

haddada opened this issue Apr 20, 2018 · 5 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/cli Categorizes an issue or PR as relevant to SIG CLI.

Comments

@haddada
Copy link

haddada commented Apr 20, 2018

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:
/kind bug
/kind feature

What happened:
kubectl get pods
Unable to connect to the server: http2: server sent GOAWAY and closed the connection; LastStreamID=9, ErrCode=NO_ERROR, debug=""

What you expected to happen:
list pods

How to reproduce it (as minimally and precisely as possible):

  • update history
    Commandline: aptdaemon role='role-commit-packages' sender=':1.23281' Install: pigz:amd64 (2.3.4-1, automatic), nvidia-container-runtime-hook:amd64 (1.3.0-1, automatic) Upgrade: nvidia-docker2:amd64 (2.0.2+docker17.12.0-1, 2.0.3+docker18.03.0-1), kubelet:amd64 (1.9.3-00, 1.10.0-00), friendly-recovery:amd64 (0.2.36, 0.2.36ubuntu1), libnvidia-container-tools:amd64 (1.0.0~alpha.3-1, 1.0.0~beta.1-1), nvidia-container-runtime:amd64 (1.1.1+docker17.12.0-1, 2.0.0+docker18.03.0-1), grub-common:amd64 (2.02~beta3-4ubuntu7.1, 2.02~beta3-4ubuntu7.3), libavahi-glib1:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), python3-aptdaemon.gtk3widgets:amd64 (1.1.1+bzr982-0ubuntu17, 1.1.1+bzr982-0ubuntu17.1), lshw:amd64 (02.18-0.1ubuntu4, 02.18-0.1ubuntu4.1), libavahi-common-data:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), slack-desktop:amd64 (3.0.5, 3.1.1), libavahi-common3:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), google-chrome-stable:amd64 (64.0.3282.186-1, 66.0.3359.117-1), plymouth-label:amd64 (0.9.2-3ubuntu17, 0.9.2-3ubuntu19), grub2-common:amd64 (2.02~beta3-4ubuntu7.1, 2.02~beta3-4ubuntu7.3), plymouth-theme-ubuntu-text:amd64 (0.9.2-3ubuntu17, 0.9.2-3ubuntu19), isc-dhcp-common:amd64 (4.3.5-3ubuntu2.2, 4.3.5-3ubuntu2.3), initramfs-tools-bin:amd64 (0.125ubuntu12, 0.125ubuntu12.1), libplymouth4:amd64 (0.9.2-3ubuntu17, 0.9.2-3ubuntu19), libavahi-ui-gtk3-0:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), libnvidia-container1:amd64 (1.0.0~alpha.3-1, 1.0.0~beta.1-1), grub-efi-amd64-bin:amd64 (2.02~beta3-4ubuntu7.1, 2.02~beta3-4ubuntu7.3), avahi-daemon:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), libavahi-core7:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), grub-efi-amd64:amd64 (2.02~beta3-4ubuntu7.1, 2.02~beta3-4ubuntu7.3), aptdaemon-data:amd64 (1.1.1+bzr982-0ubuntu17, 1.1.1+bzr982-0ubuntu17.1), avahi-autoipd:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), plymouth:amd64 (0.9.2-3ubuntu17, 0.9.2-3ubuntu19), python3-aptdaemon:amd64 (1.1.1+bzr982-0ubuntu17, 1.1.1+bzr982-0ubuntu17.1), grub-efi-amd64-signed:amd64 (1.85.1+2.02~beta3-4ubuntu7.1, 1.85.3+2.02~beta3-4ubuntu7.3), avahi-utils:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), kubeadm:amd64 (1.9.3-00, 1.10.0-00), aptdaemon:amd64 (1.1.1+bzr982-0ubuntu17, 1.1.1+bzr982-0ubuntu17.1), plymouth-theme-ubuntu-logo:amd64 (0.9.2-3ubuntu17, 0.9.2-3ubuntu19), kubectl:amd64 (1.9.3-00, 1.10.0-00), libavahi-client3:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), isc-dhcp-client:amd64 (4.3.5-3ubuntu2.2, 4.3.5-3ubuntu2.3), initramfs-tools-core:amd64 (0.125ubuntu12, 0.125ubuntu12.1), initramfs-tools:amd64 (0.125ubuntu12, 0.125ubuntu12.1), docker-ce:amd64 (17.12.0~ce-0~ubuntu, 18.03.0~ce-0~ubuntu), hdparm:amd64 (9.51+ds-1, 9.51+ds-1ubuntu0.1) End-Date: 2018-04-20 09:51:23

Anything else we need to know?:

Environment:

  • Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.2", GitCommit:"5fa2db2bd46ac79e5e00a4e6ed24191080aa463b", GitTreeState:"clean", BuildDate:"2018-01-18T10:09:24Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.3", GitCommit:"d2835416544f298c919e2ead3be3d0864b52323b", GitTreeState:"clean", BuildDate:"2018-02-07T11:55:20Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"}

  • Cloud provider or hardware configuration:
  • OS (e.g. from /etc/os-release):
    NAME="Ubuntu" VERSION="17.10 (Artful Aardvark)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 17.10" VERSION_ID="17.10" HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" VERSION_CODENAME=artful UBUNTU_CODENAME=artful
  • Kernel (e.g. uname -a):

Linux sh-Hyrican-PC 4.13.0-38-generic #43-Ubuntu SMP Wed Mar 14 15:20:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  • Install tools:
    kubeadm version: &version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.0", GitCommit:"fc32d2f3698e36b93322a3465f63a14e9f0eaead", GitTreeState:"clean", BuildDate:"2018-03-26T16:44:10Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
  • Others:
    journalctl -fu kubelet
    Error syncing pod 17c801f54fe8bd173a9f4810b4242bbb ("etcd-sh-hyrican-pc_kube-system(17c801f54fe8bd173a9f4810b4242bbb)"), skipping: failed to "StartContainer" for "etcd" with CrashLoopBackOff: "Back-off 5m0s restarting failed container=etcd pod=etcd-sh-hyrican-pc_kube-system(17c801f54fe8bd173a9f4810b4242bbb)"
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Apr 20, 2018
@shubheksha
Copy link
Contributor

shubheksha commented Apr 20, 2018 •
edited

/sig cli

@k8s-ci-robot k8s-ci-robot added sig/cli Categorizes an issue or PR as relevant to SIG CLI. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Apr 20, 2018
@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 19, 2018
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 18, 2018
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/cli Categorizes an issue or PR as relevant to SIG CLI.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@haddada @shubheksha @k8s-ci-robot @fejta-bot