Bug 1748218
| Summary: | kubelet.service: Main process exited, code=exited, status=255/EXCEPTION | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | alexander.kondrachuk |
| Component: | kubernetes | Assignee: | Jan Chaloupka <jchaloup> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 30 | CC: | eparis, go-sig, ichavero, jbrooks, jcajka, jchaloup, jpazdziora, nhorman, strigazi, tstclair |
| Target Milestone: | --- | Keywords: | Regression, Reproducer, SubBug |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-05-26 14:34:13 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
alexander.kondrachuk
2019-09-03 07:56:51 UTC
As packaged in kubernetes-node-1.15.2-1.fc30.x86_64, the kubelet.service is misconfigured.
Just plain
# dnf install -y /usr/lib/systemd/system/kubelet.service
# systemctl start kubelet.service
# systemctl status kubelet.service
yields
● kubelet.service - Kubernetes Kubelet Server
Loaded: loaded (/usr/lib/systemd/system/kubelet.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2019-09-12 20:09:08 CEST; 4min 2s ago
Docs: https://github.com/GoogleCloudPlatform/kubernetes
Process: 10018 ExecStart=/usr/bin/kubelet $KUBE_LOGTOSTDERR $KUBE_LOG_LEVEL $KUBELET_API_SERVER $KUBELET_ADDRESS $KUBELET_PORT $KUBELET_HOSTNAME $KUBE_ALLOW_PRIV $KUBELET_ARGS (code=exited, status=255/EXCEPTION)
Main PID: 10018 (code=exited, status=255/EXCEPTION)
CPU: 125ms
Sep 12 20:09:08 machine.example.test systemd[1]: kubelet.service: Main process exited, code=exited, status=255/EXCEPTION
Sep 12 20:09:08 machine.example.test systemd[1]: kubelet.service: Failed with result 'exit-code'.
Sep 12 20:09:08 machine.example.test systemd[1]: kubelet.service: Consumed 125ms CPU time.
Sep 12 20:09:08 machine.example.test systemd[1]: kubelet.service: Service RestartSec=100ms expired, scheduling restart.
Sep 12 20:09:08 machine.example.test systemd[1]: kubelet.service: Scheduled restart job, restart counter is at 5.
Sep 12 20:09:08 machine.example.test systemd[1]: Stopped Kubernetes Kubelet Server.
Sep 12 20:09:08 machine.example.test systemd[1]: kubelet.service: Consumed 125ms CPU time.
Sep 12 20:09:08 machine.example.test systemd[1]: kubelet.service: Start request repeated too quickly.
Sep 12 20:09:08 machine.example.test systemd[1]: kubelet.service: Failed with result 'exit-code'.
Sep 12 20:09:08 machine.example.test systemd[1]: Failed to start Kubernetes Kubelet Server.
In the journal, there's
Sep 12 20:09:08 machine.example.test audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=kubelet comm="systemd" exe="/usr/lib/syste
md/systemd" hostname=? addr=? terminal=? res=success'
Sep 12 20:09:08 machine.example.test kubelet[10018]: Flag --address has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https
://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
Sep 12 20:09:08 machine.example.test kubelet[10018]: Usage:
Sep 12 20:09:08 machine.example.test kubelet[10018]: kubelet [flags]
Sep 12 20:09:08 machine.example.test kubelet[10018]: Flags:
Sep 12 20:09:08 machine.example.test kubelet[10018]: --address 0.0.0.0 The IP address for the
Kubelet to serve on (set to 0.0.0.0 for all IPv4 interfaces and `::` for all IPv6 interfaces) (default 0.0.0.0) (DEPRECATED: This parameter should be set via the config file specified by t
he Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.)
Sep 12 20:09:08 machine.example.test kubelet[10018]: --allowed-unsafe-sysctls strings Comma-separated whitel
[...]
Sep 12 18:23:14 kvm-02-guest18.rhts.eng.brq.redhat.com kubelet[14673]: --vmodule moduleSpec Sep 12 18:23:14 kvm-02-guest18.rhts.eng.brq.redhat.com kubelet[14673]: --volume-plugin-dir string Sep 12 18:23:14 kvm-02-guest18.rhts.eng.brq.redhat.com kubelet[14673]: --volume-stats-agg-period duration Sep 12 18:23:14 kvm-02-guest18.rhts.eng.brq.redhat.com kubelet[14673]: F0912 18:23:14.356051 14673 server.go:156] unknown flag: --allow-privileged
That --allow-privileged comes from
# grep -r allow-privileged /etc/kubernetes
/etc/kubernetes/config:KUBE_ALLOW_PRIV="--allow-privileged=false"
When I comment out that KUBE_ALLOW_PRIV line in /etc/kubernetes/config, the kubelet.service with its out-of-box configuration at least starts and does not die immediatelly.
So the /etc/kubernetes/config is likely the first thing that needs to change to accomodate Kubernetes 1.15.
Hello Jan Pazdzioram, (In reply to Jan Pazdziora from comment #1) > As packaged in kubernetes-node-1.15.2-1.fc30.x86_64, the kubelet.service is > misconfigured. > > > So the /etc/kubernetes/config is likely the first thing that needs to change > to accomodate Kubernetes 1.15. What would be the approach to fix it? I might help to build stable rpm. Shall it be remained as kubernetes v1.15 or it can be switched to latest v1.16 ? Sincerely Alexander Given that even rawhide only has 1.15 now, and given that different Kubernetes versions bring small incompatibilities, I'd say rebase to 1.16 in rawhide and possibly in Fedora 30, and fix the config for the 1.15 bulid in Fedora 30. This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |