Skip to content
This repository has been archived by the owner on Oct 24, 2023. It is now read-only.

azure-cni-networkmonitor pod can't be scheduled #3543

Closed
chewong opened this issue Jun 25, 2020 · 1 comment
Closed

azure-cni-networkmonitor pod can't be scheduled #3543

chewong opened this issue Jun 25, 2020 · 1 comment
Labels
bug Something isn't working e2e test signal stale

Comments

@chewong
Copy link

chewong commented Jun 25, 2020

Describe the bug

Happened in k8s-create-cluster-matrix-1.19 #5.

07:24:22  2020/06/25 14:24:18 $ k describe pod azure-cni-networkmonitor-drp74 -n kube-system
07:24:22  2020/06/25 14:24:19 #### $ k describe pod azure-cni-networkmonitor-drp74 -n kube-system completed in 899.829551ms
07:24:22  2020/06/25 14:24:19 
07:24:22  Name:                 azure-cni-networkmonitor-drp74
07:24:22  Namespace:            kube-system
07:24:22  Priority:             2000001000
07:24:22  Priority Class Name:  system-node-critical
07:24:22  Node:                 <none>
07:24:22  Labels:               controller-revision-hash=578d4cf9d7
07:24:22                        k8s-app=azure-cnms
07:24:22                        pod-template-generation=1
07:24:22  Annotations:          cluster-autoscaler.kubernetes.io/daemonset-pod: true
07:24:22                        kubernetes.io/psp: privileged
07:24:22  Status:               Pending
07:24:22  IP:                   
07:24:22  IPs:                  <none>
07:24:22  Controlled By:        DaemonSet/azure-cni-networkmonitor
07:24:22  Containers:
07:24:22    azure-cnms:
07:24:22      Image:      mcr.microsoft.com/containernetworking/networkmonitor:v0.0.8
07:24:22      Port:       <none>
07:24:22      Host Port:  <none>
07:24:22      Limits:
07:24:22        cpu:     200m
07:24:22        memory:  256Mi
07:24:22      Requests:
07:24:22        cpu:     30m
07:24:22        memory:  25Mi
07:24:22      Environment:
07:24:22        HOSTNAME:   (v1:spec.nodeName)
07:24:22      Mounts:
07:24:22        /opt/cni/bin from telemetry (rw)
07:24:22        /var/log from log (rw)
07:24:22        /var/run from ebtables-rule-repo (rw)
07:24:22        /var/run/secrets/kubernetes.io/serviceaccount from default-token-ps8pv (ro)
07:24:22  Conditions:
07:24:22    Type           Status
07:24:22    PodScheduled   False 
07:24:22  Volumes:
07:24:22    log:
07:24:22      Type:          HostPath (bare host directory volume)
07:24:22      Path:          /var/log
07:24:22      HostPathType:  Directory
07:24:22    ebtables-rule-repo:
07:24:22      Type:          HostPath (bare host directory volume)
07:24:22      Path:          /var/run/
07:24:22      HostPathType:  Directory
07:24:22    telemetry:
07:24:22      Type:          HostPath (bare host directory volume)
07:24:22      Path:          /opt/cni/bin
07:24:22      HostPathType:  Directory
07:24:22    default-token-ps8pv:
07:24:22      Type:        Secret (a volume populated by a Secret)
07:24:22      SecretName:  default-token-ps8pv
07:24:22      Optional:    false
07:24:22  QoS Class:       Burstable
07:24:22  Node-Selectors:  kubernetes.io/os=linux
07:24:22  Tolerations:     :NoExecuteop=Exists
07:24:22                   :NoScheduleop=Exists
07:24:22                   CriticalAddonsOnly op=Exists
07:24:22                   node-role.kubernetes.io/master=true:NoSchedule
07:24:22                   node.kubernetes.io/disk-pressure:NoSchedule op=Exists
07:24:22                   node.kubernetes.io/memory-pressure:NoSchedule op=Exists
07:24:22                   node.kubernetes.io/network-unavailable:NoSchedule op=Exists
07:24:22                   node.kubernetes.io/not-ready:NoExecute op=Exists
07:24:22                   node.kubernetes.io/pid-pressure:NoSchedule op=Exists
07:24:22                   node.kubernetes.io/unreachable:NoExecute op=Exists
07:24:22                   node.kubernetes.io/unschedulable:NoSchedule op=Exists
07:24:22  Events:
07:24:22    Type     Reason            Age                   From               Message
07:24:22    ----     ------            ----                  ----               -------
07:24:22    Warning  FailedScheduling  4m34s (x65 over 39m)  default-scheduler  0/6 nodes are available: 5 node(s) didn't match node selector.

Might be related to #3531

Steps To Reproduce

Expected behavior

AKS Engine version

Kubernetes version

Additional context

@chewong chewong added bug Something isn't working e2e test signal labels Jun 25, 2020
@stale
Copy link

stale bot commented Aug 29, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Aug 29, 2020
@stale stale bot closed this as completed Sep 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working e2e test signal stale
Projects
None yet
Development

No branches or pull requests

1 participant