search

squat / generic-device-plugin

A Kubernetes device plugin to schedule generic Linux devices
Apache License 2.0
210 stars 23 forks source link

pod is pending while trying to access to ttyUSB0 (squat.ai/serial) #22

Closed smyshliakov closed 1 year ago

smyshliakov commented 1 year ago

Hello,

I set

squat commented 1 year ago

Hi, there are many reasons why the device might be pending!

  1. Can you share the output of kubectl describe pod <pod-name>? That would tell us exactly why the pod isn't scheduled and if it's due to device allocation.
  2. Is it possible that the plugin did not discover any USB serial devices because no devices match this path on your nodes? Let's check if the device plugin actually discovered serial devices. Can you share the output of kubectl describe nodes? That would allow us to check if any serial devices are allocatable on any nodes. If the count of squat.ai/serial devices on any node is more than 0 then we know that the device plugin is working in discovering devices.
  3. Is the serial device count 0? Then maybe this path for serial devices doesn't exist on your nodes. Can you SSH onto your nodes and share the output of ls -l /dev?
  4. Is it possible that a combination of device/resource availability and node taints makes is so that even though some nodes have discovered serial devices, no node is able to satisfy all of the requirements for the pod?

That should be a good start for debugging!

smyshliakov commented 1 year ago

Hello Lucas,

Here is info you asked

On Sun, Apr 23, 2023 at 9:01 AM Lucas Servén Marín @.***> wrote:

Hi, there are many reasons why the device might be pending!

  1. Can you share the output of kubectl describe pod ? That would tell us exactly why the pod isn't scheduled and if it's due to device allocation.
  2. Is it possible that the plugin did not discover any USB serial devices because no devices match this path on your nodes? Let's check if the device plugin actually discovered serial devices. Can you share the output of kubectl describe nodes? That would allow us to check if any serial devices are allocatable on any nodes. If the count of squat.ai/serial devices on any node is more than 0 then we know that the device plugin is working in discovering devices.
  3. Is the serial device count 0? Then maybe this path for serial devices doesn't exist on your nodes. Can you SSH onto your nodes and share the output of ls -l /dev?
  4. Is it possible that a combination of device/resource availability and node taints makes is so that even though some nodes have discovered serial devices, no node is able to satisfy all of the requirements for the pod?

That should be a good start for debugging!

— Reply to this email directly, view it on GitHub https://github.com/squat/generic-device-plugin/issues/22#issuecomment-1518954699, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVRYISZKCIU6LTUZLNDTL73XCTARZANCNFSM6AAAAAAXIJZRQY . You are receiving this because you authored the thread.Message ID: @.***>

@.*** serial]$ kubectl describe po hello Name: hello Namespace: default Priority: 0 Service Account: default Node: Labels: app.kubernetes.io/name=hello Annotations: Status: Pending IP:
IPs: Containers: hello-container: Image: docker.io/localhost/smarthab Port: Host Port: Limits: squat.ai/serial: 1 Requests: squat.ai/serial: 1 Environment: Mounts: /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-lhts7 (ro) Conditions: Type Status PodScheduled False Volumes: kube-api-access-lhts7: Type: Projected (a volume that contains injected data from multiple sources) TokenExpirationSeconds: 3607 ConfigMapName: kube-root-ca.crt ConfigMapOptional: DownwardAPI: true QoS Class: BestEffort Node-Selectors: 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

Warning FailedScheduling 110s default-scheduler 0/1 nodes are available: 1 Insufficient squat.ai/serial. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod..

@.*** serial]$ kubectl describe nodes Name: minikube Roles: control-plane Labels: beta.kubernetes.io/arch=amd64 beta.kubernetes.io/os=linux kubernetes.io/arch=amd64 kubernetes.io/hostname=minikube kubernetes.io/os=linux minikube.k8s.io/commit=08896fd1dc362c097c925146c4a0d0dac715ace0 minikube.k8s.io/name=minikube minikube.k8s.io/primary=true minikube.k8s.io/updated_at=2023_04_15T20_21_55_0700 minikube.k8s.io/version=v1.30.1 node-role.kubernetes.io/control-plane= node.kubernetes.io/exclude-from-external-load-balancers= Annotations: kubeadm.alpha.kubernetes.io/cri-socket: unix:///var/run/cri-dockerd.sock node.alpha.kubernetes.io/ttl: 0 volumes.kubernetes.io/controller-managed-attach-detach: true CreationTimestamp: Sat, 15 Apr 2023 20:21:52 +0300 Taints: Unschedulable: false Lease: HolderIdentity: minikube AcquireTime: RenewTime: Sun, 23 Apr 2023 09:14:23 +0300 Conditions: Type Status LastHeartbeatTime LastTransitionTime Reason Message

MemoryPressure False Sun, 23 Apr 2023 09:10:27 +0300 Sat, 15 Apr 2023 20:21:49 +0300 KubeletHasSufficientMemory kubelet has sufficient memory available DiskPressure False Sun, 23 Apr 2023 09:10:27 +0300 Sat, 15 Apr 2023 20:21:49 +0300 KubeletHasNoDiskPressure kubelet has no disk pressure PIDPressure False Sun, 23 Apr 2023 09:10:27 +0300 Sat, 15 Apr 2023 20:21:49 +0300 KubeletHasSufficientPID kubelet has sufficient PID available Ready True Sun, 23 Apr 2023 09:10:27 +0300 Sun, 23 Apr 2023 08:19:23 +0300 KubeletReady kubelet is posting ready status Addresses: InternalIP: 192.168.39.57 Hostname: minikube Capacity: cpu: 2 ephemeral-storage: 17784752Ki hugepages-2Mi: 0 memory: 5925620Ki pods: 110 squat.ai/serial: 0 squat.ai/serial0: 0 Allocatable: cpu: 2 ephemeral-storage: 17784752Ki hugepages-2Mi: 0 memory: 5925620Ki pods: 110 squat.ai/serial: 0 squat.ai/serial0: 0 System Info: Machine ID: 6333bcfbd2144cdc9b82a915bd752250 System UUID: 6333bcfb-d214-4cdc-9b82-a915bd752250 Boot ID: a8a707c6-1fad-4120-a9ed-84e63d191daa Kernel Version: 5.10.57 OS Image: Buildroot 2021.02.12 Operating System: linux Architecture: amd64 Container Runtime Version: docker://20.10.23 Kubelet Version: v1.26.3 Kube-Proxy Version: v1.26.3 PodCIDR: 10.244.0.0/24 PodCIDRs: 10.244.0.0/24 Non-terminated Pods: (10 in total) Namespace Name CPU Requests CPU Limits Memory Requests Memory Limits Age

default curl 0 (0%) 0 (0%) 0 (0%) 0 (0%) 6d12h kube-system coredns-787d4945fb-w5nc2 100m (5%) 0 (0%) 70Mi (1%) 170Mi (2%) 7d12h kube-system etcd-minikube 100m (5%) 0 (0%) 100Mi (1%) 0 (0%) 7d12h kube-system generic-device-plugin-f7zkt 50m (2%) 50m (2%) 20Mi (0%) 20Mi (0%) 41m kube-system kube-apiserver-minikube 250m (12%) 0 (0%) 0 (0%) 0 (0%) 7d12h kube-system kube-controller-manager-minikube 200m (10%) 0 (0%) 0 (0%) 0 (0%) 7d12h kube-system kube-proxy-j6zcp 0 (0%) 0 (0%) 0 (0%) 0 (0%) 7d12h kube-system kube-scheduler-minikube 100m (5%) 0 (0%) 0 (0%) 0 (0%) 7d12h kube-system metrics-server-6588d95b98-kjlct 100m (5%) 0 (0%) 200Mi (3%) 0 (0%) 5d15h kube-system storage-provisioner 0 (0%) 0 (0%) 0 (0%) 0 (0%) 7d12h Allocated resources: (Total limits may be over 100 percent, i.e., overcommitted.) Resource Requests Limits

cpu 900m (45%) 50m (2%) memory 390Mi (6%) 190Mi (3%) ephemeral-storage 0 (0%) 0 (0%) hugepages-2Mi 0 (0%) 0 (0%) squat.ai/serial 0 0 squat.ai/serial0 0 0 Events: Type Reason Age From Message

Normal Starting 55m kube-proxy
Normal Starting 55m kubelet Starting kubelet. Normal NodeAllocatableEnforced 55m kubelet Updated Node Allocatable limit across pods Normal NodeHasSufficientMemory 55m (x8 over 55m) kubelet Node minikube status is now: NodeHasSufficientMemory Normal NodeHasNoDiskPressure 55m (x8 over 55m) kubelet Node minikube status is now: NodeHasNoDiskPressure Normal NodeHasSufficientPID 55m (x7 over 55m) kubelet Node minikube status is now: NodeHasSufficientPID Normal RegisteredNode 54m node-controller Node minikube event: Registered Node minikube in Controller

@.*** serial]$ ls -al /dev total 0 drwxr-xr-x 23 root root 3740 Apr 23 06:03 . dr-xr-xr-x. 18 root root 270 Apr 21 21:01 .. drwxr-xr-x 2 root root 80 Apr 23 06:03 almalinux crw-r--r-- 1 root root 10, 235 Apr 23 06:03 autofs drwxr-xr-x 2 root root 440 Apr 23 06:03 block drwxr-xr-x 2 root root 100 Apr 23 06:03 bsg drwxr-xr-x 3 root root 60 Apr 23 06:03 bus drwxr-xr-x 2 root root 80 Apr 23 06:03 centos_sim22 drwxr-xr-x 2 root root 4060 Apr 23 06:13 char crw------- 1 root root 5, 1 Apr 23 06:03 console lrwxrwxrwx 1 root root 11 Apr 23 06:03 core -> /proc/kcore drwxr-xr-x 10 root root 220 Apr 23 06:13 cpu crw------- 1 root root 10, 62 Apr 23 06:03 cpu_dma_latency drwxr-xr-x 7 root root 140 Apr 23 06:03 disk brw-rw---- 1 root disk 253, 0 Apr 23 06:03 dm-0 brw-rw---- 1 root disk 253, 1 Apr 23 06:03 dm-1 brw-rw---- 1 root disk 253, 2 Apr 23 06:03 dm-2 brw-rw---- 1 root disk 253, 3 Apr 23 06:03 dm-3 drwxr-xr-x 3 root root 100 Apr 23 06:03 dri crw------- 1 root root 243, 0 Apr 23 06:03 drm_dp_aux0 crw-rw---- 1 root video 29, 0 Apr 23 06:03 fb0 lrwxrwxrwx 1 root root 13 Apr 23 06:03 fd -> /proc/self/fd crw-rw-rw- 1 root root 1, 7 Apr 23 06:03 full crw-rw-rw- 1 root root 10, 229 Apr 23 06:03 fuse crw------- 1 root root 254, 0 Apr 23 06:03 gpiochip0 crw------- 1 root root 244, 0 Apr 23 06:03 hidraw0 crw------- 1 root root 244, 1 Apr 23 06:03 hidraw1 crw------- 1 root root 244, 2 Apr 23 06:03 hidraw2 crw------- 1 root root 244, 3 Apr 23 06:03 hidraw3 crw------- 1 root root 10, 228 Apr 23 06:03 hpet drwxr-xr-x 3 root root 0 Apr 23 06:03 hugepages crw------- 1 root root 10, 183 Apr 23 06:03 hwrng lrwxrwxrwx 1 root root 12 Apr 23 06:03 initctl -> /run/initctl drwxr-xr-x 4 root root 580 Apr 23 06:03 input crw-r--r-- 1 root root 1, 11 Apr 23 06:03 kmsg crw-rw-rw- 1 root kvm 10, 232 Apr 23 08:18 kvm lrwxrwxrwx 1 root root 28 Apr 23 06:03 log -> /run/systemd/journal/dev-log brw-rw---- 1 root disk 7, 0 Apr 23 06:03 loop0 brw-rw---- 1 root disk 7, 1 Apr 23 06:03 loop1 brw-rw---- 1 root disk 7, 2 Apr 23 06:03 loop2 brw-rw---- 1 root disk 7, 3 Apr 23 06:03 loop3 brw-rw---- 1 root disk 7, 4 Apr 23 06:03 loop4 brw-rw---- 1 root disk 7, 5 Apr 23 06:03 loop5 brw-rw---- 1 root disk 7, 6 Apr 23 06:03 loop6 brw-rw---- 1 root disk 7, 7 Apr 23 06:03 loop7 crw-rw---- 1 root disk 10, 237 Apr 23 06:03 loop-control crw-rw---- 1 root lp 6, 0 Apr 23 06:03 lp0 crw-rw---- 1 root lp 6, 1 Apr 23 06:03 lp1 crw-rw---- 1 root lp 6, 2 Apr 23 06:03 lp2 crw-rw---- 1 root lp 6, 3 Apr 23 06:03 lp3 drwxr-xr-x 2 root root 140 Apr 23 06:03 mapper crw------- 1 root root 10, 227 Apr 23 06:03 mcelog crw------- 1 root root 241, 0 Apr 23 06:03 mei0 crw-r----- 1 root kmem 1, 1 Apr 23 06:03 mem drwxrwxrwt 2 root root 40 Apr 23 06:03 mqueue drwxr-xr-x 2 root root 60 Apr 23 06:03 net crw-rw-rw- 1 root root 1, 3 Apr 23 06:03 null crw------- 1 root root 10, 144 Apr 23 06:03 nvram crw-r----- 1 root kmem 1, 4 Apr 23 06:03 port crw------- 1 root root 108, 0 Apr 23 06:03 ppp crw-rw-rw- 1 root tty 5, 2 Apr 23 09:17 ptmx crw------- 1 root root 249, 0 Apr 23 06:03 ptp0 drwxr-xr-x 2 root root 0 Apr 23 06:03 pts crw-rw-rw- 1 root root 1, 8 Apr 23 06:03 random drwxr-xr-x 2 root root 60 Apr 23 06:03 raw crw-rw-r--+ 1 root root 10, 61 Apr 23 06:03 rfkill lrwxrwxrwx 1 root root 4 Apr 23 06:03 rtc -> rtc0 crw------- 1 root root 251, 0 Apr 23 06:03 rtc0 brw-rw---- 1 root disk 8, 0 Apr 23 06:03 sda brw-rw---- 1 root disk 8, 1 Apr 23 06:03 sda1 brw-rw---- 1 root disk 8, 2 Apr 23 06:03 sda2 brw-rw---- 1 root disk 8, 16 Apr 23 06:03 sdb brw-rw---- 1 root disk 8, 17 Apr 23 06:03 sdb1 brw-rw---- 1 root disk 8, 18 Apr 23 06:03 sdb2 brw-rw---- 1 root disk 8, 32 Apr 23 06:03 sdc brw-rw---- 1 root disk 8, 33 Apr 23 06:03 sdc1 drwxr-xr-x 4 root root 80 Apr 23 06:03 serial crw-rw---- 1 root disk 21, 0 Apr 23 06:03 sg0 crw-rw---- 1 root disk 21, 1 Apr 23 06:03 sg1 crw-rw---- 1 root disk 21, 2 Apr 23 06:03 sg2 drwxrwxrwt 2 root root 40 Apr 23 06:03 shm crw------- 1 root root 10, 231 Apr 23 06:03 snapshot drwxr-xr-x 4 root root 420 Apr 23 06:03 snd lrwxrwxrwx 1 root root 15 Apr 23 06:03 stderr -> /proc/self/fd/2 lrwxrwxrwx 1 root root 15 Apr 23 06:03 stdin -> /proc/self/fd/0 lrwxrwxrwx 1 root root 15 Apr 23 06:03 stdout -> /proc/self/fd/1 crw-rw-rw- 1 root tty 5, 0 Apr 23 06:03 tty crw--w---- 1 root tty 4, 0 Apr 23 06:03 tty0 crw--w---- 1 root tty 4, 1 Apr 23 06:03 tty1 crw--w---- 1 root tty 4, 10 Apr 23 06:03 tty10 crw--w---- 1 root tty 4, 11 Apr 23 06:03 tty11 crw--w---- 1 root tty 4, 12 Apr 23 06:03 tty12 crw--w---- 1 root tty 4, 13 Apr 23 06:03 tty13 crw--w---- 1 root tty 4, 14 Apr 23 06:03 tty14 crw--w---- 1 root tty 4, 15 Apr 23 06:03 tty15 crw--w---- 1 root tty 4, 16 Apr 23 06:03 tty16 crw--w---- 1 root tty 4, 17 Apr 23 06:03 tty17 crw--w---- 1 root tty 4, 18 Apr 23 06:03 tty18 crw--w---- 1 root tty 4, 19 Apr 23 06:03 tty19 crw--w---- 1 sim tty 4, 2 Apr 23 06:04 tty2 crw--w---- 1 root tty 4, 20 Apr 23 06:03 tty20 crw--w---- 1 root tty 4, 21 Apr 23 06:03 tty21 crw--w---- 1 root tty 4, 22 Apr 23 06:03 tty22 crw--w---- 1 root tty 4, 23 Apr 23 06:03 tty23 crw--w---- 1 root tty 4, 24 Apr 23 06:03 tty24 crw--w---- 1 root tty 4, 25 Apr 23 06:03 tty25 crw--w---- 1 root tty 4, 26 Apr 23 06:03 tty26 crw--w---- 1 root tty 4, 27 Apr 23 06:03 tty27 crw--w---- 1 root tty 4, 28 Apr 23 06:03 tty28 crw--w---- 1 root tty 4, 29 Apr 23 06:03 tty29 crw--w---- 1 root tty 4, 3 Apr 23 06:03 tty3 crw--w---- 1 root tty 4, 30 Apr 23 06:03 tty30 crw--w---- 1 root tty 4, 31 Apr 23 06:03 tty31 crw--w---- 1 root tty 4, 32 Apr 23 06:03 tty32 crw--w---- 1 root tty 4, 33 Apr 23 06:03 tty33 crw--w---- 1 root tty 4, 34 Apr 23 06:03 tty34 crw--w---- 1 root tty 4, 35 Apr 23 06:03 tty35 crw--w---- 1 root tty 4, 36 Apr 23 06:03 tty36 crw--w---- 1 root tty 4, 37 Apr 23 06:03 tty37 crw--w---- 1 root tty 4, 38 Apr 23 06:03 tty38 crw--w---- 1 root tty 4, 39 Apr 23 06:03 tty39 crw--w---- 1 root tty 4, 4 Apr 23 06:03 tty4 crw--w---- 1 root tty 4, 40 Apr 23 06:03 tty40 crw--w---- 1 root tty 4, 41 Apr 23 06:03 tty41 crw--w---- 1 root tty 4, 42 Apr 23 06:03 tty42 crw--w---- 1 root tty 4, 43 Apr 23 06:03 tty43 crw--w---- 1 root tty 4, 44 Apr 23 06:03 tty44 crw--w---- 1 root tty 4, 45 Apr 23 06:03 tty45 crw--w---- 1 root tty 4, 46 Apr 23 06:03 tty46 crw--w---- 1 root tty 4, 47 Apr 23 06:03 tty47 crw--w---- 1 root tty 4, 48 Apr 23 06:03 tty48 crw--w---- 1 root tty 4, 49 Apr 23 06:03 tty49 crw--w---- 1 root tty 4, 5 Apr 23 06:03 tty5 crw--w---- 1 root tty 4, 50 Apr 23 06:03 tty50 crw--w---- 1 root tty 4, 51 Apr 23 06:03 tty51 crw--w---- 1 root tty 4, 52 Apr 23 06:03 tty52 crw--w---- 1 root tty 4, 53 Apr 23 06:03 tty53 crw--w---- 1 root tty 4, 54 Apr 23 06:03 tty54 crw--w---- 1 root tty 4, 55 Apr 23 06:03 tty55 crw--w---- 1 root tty 4, 56 Apr 23 06:03 tty56 crw--w---- 1 root tty 4, 57 Apr 23 06:03 tty57 crw--w---- 1 root tty 4, 58 Apr 23 06:03 tty58 crw--w---- 1 root tty 4, 59 Apr 23 06:03 tty59 crw--w---- 1 root tty 4, 6 Apr 23 06:03 tty6 crw--w---- 1 root tty 4, 60 Apr 23 06:03 tty60 crw--w---- 1 root tty 4, 61 Apr 23 06:03 tty61 crw--w---- 1 root tty 4, 62 Apr 23 06:03 tty62 crw--w---- 1 root tty 4, 63 Apr 23 06:03 tty63 crw--w---- 1 root tty 4, 7 Apr 23 06:03 tty7 crw--w---- 1 root tty 4, 8 Apr 23 06:03 tty8 crw--w---- 1 root tty 4, 9 Apr 23 06:03 tty9 crw-rw---- 1 root dialout 4, 64 Apr 23 06:03 ttyS0 crw-rw---- 1 root dialout 4, 65 Apr 23 06:03 ttyS1 crw-rw---- 1 root dialout 4, 66 Apr 23 06:03 ttyS2 crw-rw---- 1 root dialout 4, 67 Apr 23 06:03 ttyS3 crw-rw---- 1 root dialout 188, 0 Apr 23 06:03 ttyUSB0 crw------- 1 root root 10, 239 Apr 23 06:03 uhid crw------- 1 root root 10, 223 Apr 23 06:03 uinput crw-rw-rw- 1 root root 1, 9 Apr 23 06:03 urandom crw------- 1 root root 246, 0 Apr 23 06:03 usbmon0 crw------- 1 root root 246, 1 Apr 23 06:03 usbmon1 crw------- 1 root root 246, 2 Apr 23 06:03 usbmon2 drwxr-xr-x 4 root root 80 Apr 23 06:03 v4l crw-rw---- 1 root tty 7, 0 Apr 23 06:03 vcs crw-rw---- 1 root tty 7, 1 Apr 23 06:03 vcs1 crw-rw---- 1 root tty 7, 2 Apr 23 06:03 vcs2 crw-rw---- 1 root tty 7, 3 Apr 23 06:03 vcs3 crw-rw---- 1 root tty 7, 4 Apr 23 06:03 vcs4 crw-rw---- 1 root tty 7, 5 Apr 23 06:03 vcs5 crw-rw---- 1 root tty 7, 6 Apr 23 06:03 vcs6 crw-rw---- 1 root tty 7, 128 Apr 23 06:03 vcsa crw-rw---- 1 root tty 7, 129 Apr 23 06:03 vcsa1 crw-rw---- 1 root tty 7, 130 Apr 23 06:03 vcsa2 crw-rw---- 1 root tty 7, 131 Apr 23 06:03 vcsa3 crw-rw---- 1 root tty 7, 132 Apr 23 06:03 vcsa4 crw-rw---- 1 root tty 7, 133 Apr 23 06:03 vcsa5 crw-rw---- 1 root tty 7, 134 Apr 23 06:03 vcsa6 drwxr-xr-x 2 root root 60 Apr 23 06:03 vfio crw------- 1 root root 10, 63 Apr 23 06:03 vga_arbiter crw------- 1 root root 10, 137 Apr 23 06:03 vhci crw------- 1 root root 10, 238 Apr 23 06:13 vhost-net crw------- 1 root root 10, 241 Apr 23 06:03 vhost-vsock crw-rw----+ 1 root video 81, 0 Apr 23 06:03 video0 crw-rw----+ 1 root video 81, 1 Apr 23 06:03 video1 crw------- 1 root root 10, 130 Apr 23 06:03 watchdog crw------- 1 root root 248, 0 Apr 23 06:03 watchdog0 crw-rw-rw- 1 root root 1, 5 Apr 23 06:03 zero

squat commented 1 year ago

Hi @smyshliakov :) thanks for all of those details. Can you please share with me the exact YAML for the generic-device-plugin? From your first post, it looks like the indentation on the YAML might be wrong, which would cause the plugin not to know what paths you are interested in.

smyshliakov commented 1 year ago

Hello Lucas,

On Sun, Apr 23, 2023 at 9:53 AM Lucas Servén Marín @.***> wrote:

Hi @smyshliakov https://github.com/smyshliakov :) thanks for all of those details. Can you please share with me the exact YAML for the generic-device-plugin? From your first post, it looks like the indentation on the YAML might be wrong, which would cause the plugin not to know what paths you are interested in.

— Reply to this email directly, view it on GitHub https://github.com/squat/generic-device-plugin/issues/22#issuecomment-1518967154, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVRYIS2MN6EK25KFX64QNBTXCTGVHANCNFSM6AAAAAAXIJZRQY . You are receiving this because you were mentioned.Message ID: @.***>

squat commented 1 year ago

@smyshliakov something seems to have gone wrong with the email, there was no attachment / no YAML :(

smyshliakov commented 1 year ago

Hello Lucas,

Sorry for the late reply, just came from a local table-tennis competition 🤗

here is the file

On Sun, Apr 23, 2023 at 10:11 AM Lucas Servén Marín < @.***> wrote:

@smyshliakov https://github.com/smyshliakov something seems to have gone wrong with the email, there was no attachment / no YAML :(

— Reply to this email directly, view it on GitHub https://github.com/squat/generic-device-plugin/issues/22#issuecomment-1518976115, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVRYIS2UNCFJ35WD43YMMYDXCTIYPANCNFSM6AAAAAAXIJZRQY . You are receiving this because you were mentioned.Message ID: @.***>

smyshliakov commented 1 year ago

It looks like google mail is blocking attachments,

On Sun, Apr 23, 2023 at 3:45 PM Sergei Myshliakov < @.***> wrote:

Hello Lucas,

Sorry for the late reply, just came from a local table-tennis competition 🤗

here is the file

On Sun, Apr 23, 2023 at 10:11 AM Lucas Servén Marín < @.***> wrote:

@smyshliakov https://github.com/smyshliakov something seems to have gone wrong with the email, there was no attachment / no YAML :(

— Reply to this email directly, view it on GitHub https://github.com/squat/generic-device-plugin/issues/22#issuecomment-1518976115, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVRYIS2UNCFJ35WD43YMMYDXCTIYPANCNFSM6AAAAAAXIJZRQY . You are receiving this because you were mentioned.Message ID: @.***>

apiVersion: apps/v1 kind: DaemonSet metadata: name: generic-device-plugin namespace: kube-system labels: app.kubernetes.io/name: generic-device-plugin spec: selector: matchLabels: app.kubernetes.io/name: generic-device-plugin template: metadata: labels: app.kubernetes.io/name: generic-device-plugin spec: priorityClassName: system-node-critical tolerations:

smyshliakov commented 1 year ago

generic-device-plugin.txt

squat commented 1 year ago

Hi @smyshliakov I took your manifest and I am able schedule a random TTY device (changed /dev/ttyUSB0 to /dev/ttyS9 since I don't have a ttyUSB in my kind cluster) just fine.

I wonder if the problem lies in the minikube cluster. When you showed me the list of devices, was this the list from your host machne? Or the list of available devices after doing minikube ssh? I wonder if there actually is a /dev/ttyUSB0 in your minikube node.

smyshliakov commented 1 year ago

Hello Lucas,

You are right, there is no ttyUSB device when I ssh -n minikube, will figure out how to add ttyUSB support to the minikube node.

On Mon, Apr 24, 2023 at 12:41 PM Lucas Servén Marín < @.***> wrote:

Hi @smyshliakov https://github.com/smyshliakov I took your manifest and I am able schedule a random TTY device (changed /dev/ttyUSB0 to /dev/ttyS9 since I don't have a ttyUSB in my kind cluster) just fine.

I wonder if the problem lies in the minikube cluster. When you showed me the list of devices, was this the list from your host machne? Or the list of available devices after doing minikube ssh? I wonder if there actually is a /dev/ttyUSB0 in your minikube node.

— Reply to this email directly, view it on GitHub https://github.com/squat/generic-device-plugin/issues/22#issuecomment-1519752930, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVRYIS4XC6HQARIMPAWA3EDXCZDE7ANCNFSM6AAAAAAXIJZRQY . You are receiving this because you were mentioned.Message ID: @.***>

rbaumgar commented 1 year ago

Lucas,

would be nice to have your recommendations (first replay) in the readme as something like error handling/debugging...

kr Robert

squat commented 1 year ago

closing this for now as the issue was that no devices were present in the Minukube cluster rather than an issue with the plugin. Please re-open if you need more help or we do discover and issue.