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

After initializing k3s, some pods cannot run #8313

Closed
Hans-Wu-cn opened this issue Sep 7, 2023 · 2 comments
Closed

After initializing k3s, some pods cannot run #8313

Hans-Wu-cn opened this issue Sep 7, 2023 · 2 comments

Comments

@Hans-Wu-cn
Copy link

Environmental Info:
K3s Version:

k3s version v1.27.4+k3s1 (36645e7)
go version go1.20.6
Node(s) CPU architecture, OS, and Version:

Linux hans 5.15.0-83-generic #92-Ubuntu SMP Mon Aug 14 09:30:42 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration:

Currently, only 1 server is started
Describe the bug:

Some nodes have been unable to start after running. Enter kubectl all - n kube system

NAME                                         READY   STATUS      RESTARTS   AGE
pod/coredns-77ccd57875-cjcd8                 1/1     Running     0          13m
pod/helm-install-traefik-crd-ksqbr           0/1     Completed   0          13m
pod/helm-install-traefik-f4wjl               0/1     Completed   1          13m
pod/local-path-provisioner-957fdf8bc-9r8wl   1/1     Running     0          13m
pod/svclb-traefik-92809991-dssj8             2/2     Running     0          11m
pod/metrics-server-648b5df564-4zfbm          1/1     Running     0          13m
pod/traefik-64f55bb67d-htc6n                 1/1     Running     0          11m

NAME                     TYPE           CLUSTER-IP      EXTERNAL-IP       PORT(S)                      AGE
service/kube-dns         ClusterIP      10.43.0.10      <none>            53/UDP,53/TCP,9153/TCP       13m
service/metrics-server   ClusterIP      10.43.240.49    <none>            443/TCP                      13m
service/traefik          LoadBalancer   10.43.154.214   192.168.189.128   80:32164/TCP,443:30826/TCP   11m

NAME                                    DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE
daemonset.apps/svclb-traefik-92809991   1         1         1       1            1           <none>          11m

NAME                                     READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/coredns                  1/1     1            1           13m
deployment.apps/local-path-provisioner   1/1     1            1           13m
deployment.apps/metrics-server           1/1     1            1           13m
deployment.apps/traefik                  1/1     1            1           11m

NAME                                               DESIRED   CURRENT   READY   AGE
replicaset.apps/coredns-77ccd57875                 1         1         1       13m
replicaset.apps/local-path-provisioner-957fdf8bc   1         1         1       13m
replicaset.apps/metrics-server-648b5df564          1         1         1       13m
replicaset.apps/traefik-64f55bb67d                 1         1         1       11m

NAME                                 COMPLETIONS   DURATION   AGE
job.batch/helm-install-traefik-crd   1/1           2m29s      13m
job.batch/helm-install-traefik       1/1           2m32s      13m

Steps To Reproduce:

  • Installed K3s:
sudo apt update 
sudo apt install docker.io
curl -sfL https://rancher-mirror.rancher.cn/k3s/k3s-install.sh | INSTALL_K3S_EXEC="--docker" INSTALL_K3S_MIRROR=cn sh -

Expected behavior:

Actual behavior:

Additional context / logs:

root@hans:/home/hans# kubectl logs helm-install-traefik-f4wjl -n kube-system
if [[ ${KUBERNETES_SERVICE_HOST} =~ .*:.* ]]; then
        echo "KUBERNETES_SERVICE_HOST is using IPv6"
        CHART="${CHART//%\{KUBERNETES_API\}%/[${KUBERNETES_SERVICE_HOST}]:${KUBERNETES_SERVICE_PORT}}"
else
        CHART="${CHART//%\{KUBERNETES_API\}%/${KUBERNETES_SERVICE_HOST}:${KUBERNETES_SERVICE_PORT}}"
fi

set +v -x
+ [[ '' != \t\r\u\e ]]
+ export HELM_HOST=127.0.0.1:44134
+ HELM_HOST=127.0.0.1:44134
+ helm_v2 init --skip-refresh --client-only --stable-repo-url https://charts.helm.sh/stable/
+ tiller --listen=127.0.0.1:44134 --storage=secret
Creating /home/klipper-helm/.helm
Creating /home/klipper-helm/.helm/repository
Creating /home/klipper-helm/.helm/repository/cache
Creating /home/klipper-helm/.helm/repository/local
Creating /home/klipper-helm/.helm/plugins
Creating /home/klipper-helm/.helm/starters
Creating /home/klipper-helm/.helm/cache/archive
Creating /home/klipper-helm/.helm/repository/repositories.yaml
Adding stable repo with URL: https://charts.helm.sh/stable/
Adding local repo with URL: http://127.0.0.1:8879/charts
$HELM_HOME has been configured at /home/klipper-helm/.helm.
Not installing Tiller due to 'client-only' flag having been set
++ timeout -s KILL 30 helm_v2 ls --all '^traefik$' --output json
++ jq -r '.Releases | length'
[main] 2023/09/07 14:26:46 Starting Tiller v2.17.0 (tls=false)
[main] 2023/09/07 14:26:46 GRPC listening on 127.0.0.1:44134
[main] 2023/09/07 14:26:46 Probes listening on :44135
[main] 2023/09/07 14:26:46 Storage driver is Secret
[main] 2023/09/07 14:26:46 Max history per release is 0
[storage] 2023/09/07 14:26:46 listing all releases with filter
+ V2_CHART_EXISTS=
+ [[ '' == \1 ]]
+ [[ '' == \v\2 ]]
+ shopt -s nullglob
+ [[ -f /config/ca-file.pem ]]
+ [[ -f /tmp/ca-file.pem ]]
+ [[ -n '' ]]
+ helm_content_decode
+ set -e
+ ENC_CHART_PATH=/chart/traefik.tgz.base64
+ CHART_PATH=/tmp/traefik.tgz
+ [[ ! -f /chart/traefik.tgz.base64 ]]
+ return
+ [[ install != \d\e\l\e\t\e ]]
+ helm_repo_init
+ grep -q -e 'https\?://'
+ echo 'chart path is a url, skipping repo update'
+ helm_v3 repo remove stable
chart path is a url, skipping repo update
Error: no repositories configured
+ true
+ return
+ helm_update install --set-string global.systemDefaultRegistry=
+ [[ helm_v3 == \h\e\l\m\_\v\3 ]]
++ tr '[:upper:]' '[:lower:]'
++ helm_v3 ls --all -f '^traefik$' --namespace kube-system --output json
++ jq -r '"\(.[0].app_version),\(.[0].status)"'
+ LINE=null,null
+ IFS=,
+ read -r INSTALLED_VERSION STATUS _
+ VALUES=
+ for VALUES_FILE in /config/*.yaml
+ VALUES=' --values /config/values-01_HelmChart.yaml'
+ [[ install = \d\e\l\e\t\e ]]
+ [[ null =~ ^(|null)$ ]]
+ [[ null =~ ^(|null)$ ]]
+ echo 'Installing helm_v3 chart'
+ helm_v3 install --set-string global.systemDefaultRegistry= traefik https://10.43.0.1:443/static/charts/traefik-21.2.1+up21.2.0.tgz --values /config/values-01_HelmChart.yaml
NAME: traefik
LAST DEPLOYED: Thu Sep  7 14:26:47 2023
NAMESPACE: kube-system
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
Traefik Proxy 2.9.10 has been deployed successfully
on kube-system namespace !
+ exit
@dereknola
Copy link
Member

The helm-install-* are suppose to complete, they don't continue to run.

@brandond
Copy link
Member

brandond commented Sep 7, 2023

To mirror Derek's question, where's the acual problem? You didn't show kubectl get node -o wide, logs from the affected nodes, or anything else to back up your report that some nodes are unable to run. Did you at some point attempt to add additional nodes to this cluster?

@caroline-suse-rancher caroline-suse-rancher moved this from New to In Triage in K3s Development Sep 20, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 31, 2024
@github-project-automation github-project-automation bot moved this from In Triage to Done Issue in K3s Development Jan 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

4 participants