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

Problem installing with the helm charts [BUG] #206

Closed
saeid93 opened this issue Nov 17, 2021 · 6 comments
Closed

Problem installing with the helm charts [BUG] #206

saeid93 opened this issue Nov 17, 2021 · 6 comments
Assignees

Comments

@saeid93
Copy link

saeid93 commented Nov 17, 2021

What happened:
I cannot install kubedl using the provided helm charts
following the steps described for Helm installation

saeid@saeid-OptiPlex-7440-AIO:~/codes/kubedl$ helm install kubedl ./helm/kubedl --create-namespace -n kubedl-system

Error: INSTALLATION FAILED: validation: chart.metadata.version "daily" is invalid
saeid@saeid-OptiPlex-7440-AIO:~/codes/kubedl$ 

Environment:

  • KubeDL version:
  • Kubernetes version (use kubectl version): v1.22.3
  • OS (e.g: cat /etc/os-release): Ubuntu 20.04.3 LTS
  • Kernel (e.g. uname -a):Ubuntu 20.04.3 LTS
  • Install tools: helm
@SimonCqk
Copy link
Collaborator

@saeid93 hi saeid, it seems helm >= 3.5.2 enforce that format of chart.metadata.version must be a Semantic Versioning name, would you please provide your helm version to confirm it?

@saeid93
Copy link
Author

saeid93 commented Nov 17, 2021

Hi Simon @SimonCqk Thanks for your reply. It's 3.7.0 . How can I solve this?

@SimonCqk
Copy link
Collaborator

@saeid93 you may amend the content of version: daily to version: 0.4.0 in helm/kubedl/Chart.yaml locally, we'll fix this in master branch soon.

@saeid93
Copy link
Author

saeid93 commented Nov 17, 2021

Thanks for the suggestion. @SimonCqk The installation could pass the previous phase, however I'm having another issue with the installation:

saeid@saeid-OptiPlex-7440-AIO:~/codes/kubedl$ k get pods --all-namespaces
NAMESPACE              NAME                                         READY   STATUS              RESTARTS        AGE
kube-system            coredns-78fcd69978-7vr9g                     1/1     Running             1 (3h47m ago)   2d17h
kube-system            etcd-minikube                                1/1     Running             1 (3h47m ago)   2d17h
kube-system            kube-apiserver-minikube                      1/1     Running             1 (3h47m ago)   2d17h
kube-system            kube-controller-manager-minikube             1/1     Running             1 (3h47m ago)   2d17h
kube-system            kube-proxy-g55r9                             1/1     Running             1 (3h47m ago)   2d17h
kube-system            kube-scheduler-minikube                      1/1     Running             1 (3h47m ago)   2d17h
kube-system            metrics-server-77c99ccb96-9lqn8              1/1     Running             1 (3h47m ago)   2d17h
kube-system            storage-provisioner                          1/1     Running             3 (3h41m ago)   2d17h
kubedl-system          kubedl-5576d9c96f-p6jwc                      0/1     RunContainerError   6 (17s ago)     5m59s
kubedl-system          kubedl-5576d9c96f-rbgpc                      0/1     CrashLoopBackOff    5 (2m53s ago)   5m59s
kubernetes-dashboard   dashboard-metrics-scraper-5594458c94-pmcdr   1/1     Running             1 (3h47m ago)   4h52m
kubernetes-dashboard   kubernetes-dashboard-654cf69797-cbcbf        1/1     Running
saeid@saeid-OptiPlex-7440-AIO:~/codes/kubedl$ k -n kubedl-system describe pod kubedl-5576d9c96f-rbgpc
Name:         kubedl-5576d9c96f-rbgpc
Namespace:    kubedl-system
Priority:     0
Node:         minikube/192.168.49.2
Start Time:   Wed, 17 Nov 2021 08:41:38 -0500
Labels:       app.kubernetes.io/instance=kubedl
              app.kubernetes.io/name=kubedl
              pod-template-hash=5576d9c96f
Annotations:  <none>
Status:       Running
IP:           172.17.0.6
IPs:
  IP:           172.17.0.6
Controlled By:  ReplicaSet/kubedl-5576d9c96f
Containers:
  kubedl:
    Container ID:   docker://69157303925d807445bdc6e0c50841d6af35a74b6e7b4e7392cfe3152d4541a2
    Image:          kubedl/kubedl:daily
    Image ID:       docker-pullable://kubedl/kubedl@sha256:a4e5651476c62bd51c986cc159b7fad619779e9bbf10fb58f3907cd36dfe7069
    Port:           8443/TCP
    Host Port:      0/TCP
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       ContainerCannotRun
      Message:      OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: process_linux.go:508: setting cgroup config for procHooks process caused: failed to write "204800": write /sys/fs/cgroup/cpu,cpuacct/kubepods/burstable/pod8e2c2392-dffa-44af-a47f-1f1b93cd0ede/69157303925d807445bdc6e0c50841d6af35a74b6e7b4e7392cfe3152d4541a2/cpu.cfs_quota_us: invalid argument: unknown
      Exit Code:    128
      Started:      Wed, 17 Nov 2021 08:47:34 -0500
      Finished:     Wed, 17 Nov 2021 08:47:34 -0500
    Ready:          False
    Restart Count:  6
    Limits:
      cpu:     2048m
      memory:  2Gi
    Requests:
      cpu:        1024m
      memory:     1Gi
    Liveness:     http-get http://:http/metrics delay=0s timeout=1s period=10s #success=1 #failure=3
    Readiness:    http-get http://:http/metrics delay=0s timeout=1s period=10s #success=1 #failure=3
    Environment:  <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-9qcvp (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             False 
  ContainersReady   False 
  PodScheduled      True 
Volumes:
  kube-api-access-9qcvp:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   Burstable
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason     Age                   From               Message
  ----     ------     ----                  ----               -------
  Normal   Scheduled  9m9s                  default-scheduler  Successfully assigned kubedl-system/kubedl-5576d9c96f-rbgpc to minikube
  Normal   Created    8m17s (x4 over 9m8s)  kubelet            Created container kubedl
  Warning  Failed     8m17s (x4 over 9m8s)  kubelet            Error: failed to start container "kubedl": Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: process_linux.go:508: setting cgroup config for procHooks process caused: failed to write "204800": write /sys/fs/cgroup/cpu,cpuacct/kubepods/burstable/pod8e2c2392-dffa-44af-a47f-1f1b93cd0ede/kubedl/cpu.cfs_quota_us: invalid argument: unknown
  Normal   Pulled     7m31s (x5 over 9m8s)  kubelet            Container image "kubedl/kubedl:daily" already present on machine
  Warning  BackOff    4m2s (x31 over 9m)    kubelet            Back-off restarting failed container
saeid@saeid-OptiPlex-7440-AIO:~/codes/kubedl$ k -n kubedl-system describe pod kubedl-5576d9c96f-p6jwc
Name:         kubedl-5576d9c96f-p6jwc
Namespace:    kubedl-system
Priority:     0
Node:         minikube/192.168.49.2
Start Time:   Wed, 17 Nov 2021 08:41:38 -0500
Labels:       app.kubernetes.io/instance=kubedl
              app.kubernetes.io/name=kubedl
              pod-template-hash=5576d9c96f
Annotations:  <none>
Status:       Running
IP:           172.17.0.7
IPs:
  IP:           172.17.0.7
Controlled By:  ReplicaSet/kubedl-5576d9c96f
Containers:
  kubedl:
    Container ID:   docker://fc8aa0759e2979ed2f67b35d83732a423c9ee50e77f564ab5938807b30841d52
    Image:          kubedl/kubedl:daily
    Image ID:       docker-pullable://kubedl/kubedl@sha256:a4e5651476c62bd51c986cc159b7fad619779e9bbf10fb58f3907cd36dfe7069
    Port:           8443/TCP
    Host Port:      0/TCP
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       ContainerCannotRun
      Message:      OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: process_linux.go:508: setting cgroup config for procHooks process caused: failed to write "204800": write /sys/fs/cgroup/cpu,cpuacct/kubepods/burstable/podec83695c-d111-47a8-a424-4f8ee5ed359e/fc8aa0759e2979ed2f67b35d83732a423c9ee50e77f564ab5938807b30841d52/cpu.cfs_quota_us: invalid argument: unknown
      Exit Code:    128
      Started:      Wed, 17 Nov 2021 08:47:20 -0500
      Finished:     Wed, 17 Nov 2021 08:47:20 -0500
    Ready:          False
    Restart Count:  6
    Limits:
      cpu:     2048m
      memory:  2Gi
    Requests:
      cpu:        1024m
      memory:     1Gi
    Liveness:     http-get http://:http/metrics delay=0s timeout=1s period=10s #success=1 #failure=3
    Readiness:    http-get http://:http/metrics delay=0s timeout=1s period=10s #success=1 #failure=3
    Environment:  <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-ssbk2 (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             False 
  ContainersReady   False 
  PodScheduled      True 
Volumes:
  kube-api-access-ssbk2:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   Burstable
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason     Age                    From               Message
  ----     ------     ----                   ----               -------
  Normal   Scheduled  10m                    default-scheduler  Successfully assigned kubedl-system/kubedl-5576d9c96f-p6jwc to minikube
  Warning  Failed     9m12s (x4 over 10m)    kubelet            Error: failed to start container "kubedl": Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: process_linux.go:508: setting cgroup config for procHooks process caused: failed to write "204800": write /sys/fs/cgroup/cpu,cpuacct/kubepods/burstable/podec83695c-d111-47a8-a424-4f8ee5ed359e/kubedl/cpu.cfs_quota_us: invalid argument: unknown
  Normal   Pulled     8m31s (x5 over 10m)    kubelet            Container image "kubedl/kubedl:daily" already present on machine
  Normal   Created    8m30s (x5 over 10m)    kubelet            Created container kubedl
  Warning  BackOff    5m1s (x31 over 9m56s)  kubelet            Back-off restarting failed container

Could you pleae help me how can I resolve this?

@SimonCqk
Copy link
Collaborator

Could you pleae help me how can I resolve this?

As I replied in #207 , I do think that you'd reset your node and start it from a clean environment, btw it says can not write "204800" as container cfs quota, would you re-apply deployment with empty resource?

@saeid93
Copy link
Author

saeid93 commented Nov 18, 2021

Thanks @SimonCqk for all the help! yes, it was some problem with my cluster.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants