Comment 5 for bug 1817723

Revision history for this message
Fernando Hernandez Gonzalez (fhernan2) wrote : Re: [Containers] Pods not running on computes (Standar 2+2)

Same behavior on 2 + 2 + 2

--------------------------------------------------------------------------------------------
controller-0:~$ kubectl get pods --all-namespaces -o wide |grep -v -e "Running" -e "Completed"
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE
kube-system calico-node-jd2gd 0/2 ContainerCreating 0 3h51m 192.168.204.172 compute-0 <none>
kube-system calico-node-nlt9h 0/2 ContainerCreating 0 3h50m 192.168.204.133 compute-1 <none>
kube-system kube-proxy-7gkrj 0/1 ContainerCreating 0 3h50m 192.168.204.133 compute-1 <none>
kube-system kube-proxy-fpk2z 0/1 ContainerCreating 0 3h51m 192.168.204.172 compute-0 <none>
openstack nova-cell-setup-krck7 0/1 Init:0/2 0 158m 172.16.0.34 controller-0 <none>
openstack osh-openstack-garbd-garbd-5d495764d9-zrddq 0/1 Pending 0 3h22m <none> <none> <none>
--------------------------------------------------------------------------------------------
controller-0:~$ kubectl describe pods -n openstack osh-openstack-garbd-garbd-5d495764d9-zrddq
Name: osh-openstack-garbd-garbd-5d495764d9-zrddq
Namespace: openstack
Priority: 0
PriorityClassName: <none>
Node: <none>
Labels: application=garbd
                    component=server
                    pod-template-hash=5d495764d9
                    release_group=osh-openstack-garbd
Annotations: configmap-bin-hash: e9eadebcdb0d47224b47dfa165edeca8ac773b0939b1672ee5d4a438c2341f5a
Status: Pending
IP:
Controlled By: ReplicaSet/osh-openstack-garbd-garbd-5d495764d9
Init Containers:
  init:
    Image: 192.168.204.2:9001/quay.io/stackanetes/kubernetes-entrypoint:v0.3.1
    Port: <none>
    Host Port: <none>
    Command:
      kubernetes-entrypoint
    Environment:
      POD_NAME: osh-openstack-garbd-garbd-5d495764d9-zrddq (v1:metadata.name)
      NAMESPACE: openstack (v1:metadata.namespace)
      INTERFACE_NAME: eth0
      PATH: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/
      DEPENDENCY_SERVICE:
      DEPENDENCY_DAEMONSET:
      DEPENDENCY_CONTAINER:
      DEPENDENCY_POD_JSON:
      COMMAND: echo done
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from osh-openstack-garbd-garbd-token-8x7p6 (ro)
Containers:
  garbd:
    Image: 192.168.204.2:9001/starlingx/stx-mariadb:dev-centos-pike-latest
    Port: <none>
    Host Port: <none>
    Command:
      /tmp/garbd.sh
    Environment:
      GROUP_NAME: mariadb-server_openstack
      GROUP_ADDRESS: gcomm://mariadb-server-0.mariadb-discovery.openstack.svc.cluster.local,mariadb-server-1.mariadb-discovery.openstack.svc.cluster.local
    Mounts:
      /tmp/garbd.sh from garbd-bin (ro)
      /var/run/secrets/kubernetes.io/serviceaccount from osh-openstack-garbd-garbd-token-8x7p6 (ro)
Conditions:
  Type Status
  PodScheduled False
Volumes:
  garbd-bin:
    Type: ConfigMap (a volume populated by a ConfigMap)
    Name: osh-openstack-garbd-garbd-bin
    Optional: false
  osh-openstack-garbd-garbd-token-8x7p6:
    Type: Secret (a volume populated by a Secret)
    SecretName: osh-openstack-garbd-garbd-token-8x7p6
    Optional: false
QoS Class: BestEffort
Node-Selectors: openstack-compute-node=enabled
Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type Reason Age From Message
  ---- ------ ---- ---- -------
  Warning FailedScheduling 3m14s (x12091 over 3h23m) default-scheduler 0/4 nodes are available: ***2 node(s) didn't match node selector, 2 node(s) had taints that the pod didn't tolerate.***