[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Router Pod stuck at pending



Hello all, I have installed Openshift Origin 3 on my 3 node setup (1 Master, 2 Nodes) and noticed the following errors:

1. oc get nodes

NAME                 STATUS                     AGE
master.dev.local   Ready,SchedulingDisabled   8d
node1.dev.local    Ready                      8d
node2.dev.local    Ready                      8d

2. oc get pods

NAME                       READY     STATUS             RESTARTS   AGE
docker-registry-1-deploy   0/1       DeadlineExceeded   0          22m
docker-registry-2-pbvcf    1/1       Running            0          21m
router-1-deploy            1/1       Running            0          1m
router-1-vzngh             0/1       Pending            0          3s

3. oc describe pod router-1-vzngh

Name:           router-1-vzngh
Namespace:      openshift
Image(s):       openshift/origin-haproxy-router:v1.1.4
Node:           /
Labels:         deployment=router-1,deploymentconfig=router,router=router
Status:         Pending
Reason:
Message:
IP:
Controllers:    ReplicationController/router-1
Containers:
  router:
    Container ID:
    Image:              openshift/origin-haproxy-router:v1.1.4
    Image ID:
    Ports:              80/TCP, 443/TCP, 1936/TCP
    QoS Tier:
      cpu:              BestEffort
      memory:           BestEffort
    State:              Waiting
    Ready:              False
    Restart Count:      0
    Liveness:           http-get http://localhost:1936/healthz delay=10s timeout=1s period=10s #success=1 #failure=3
    Readiness:          http-get http://localhost:1936/healthz delay=10s timeout=1s period=10s #success=1 #failure=3
    Environment Variables:
     ---
     --- <Certificate data truncated for clarity>
      OPENSHIFT_MASTER:                         https://master.dev.local:8443
      ROUTER_EXTERNAL_HOST_HOSTNAME:
      ROUTER_EXTERNAL_HOST_HTTPS_VSERVER:
      ROUTER_EXTERNAL_HOST_HTTP_VSERVER:
      ROUTER_EXTERNAL_HOST_INSECURE:            false
      ROUTER_EXTERNAL_HOST_PARTITION_PATH:
      ROUTER_EXTERNAL_HOST_PASSWORD:
      ROUTER_EXTERNAL_HOST_PRIVKEY:             /etc/secret-volume/router.pem
      ROUTER_EXTERNAL_HOST_USERNAME:
      ROUTER_SERVICE_HTTPS_PORT:                443
      ROUTER_SERVICE_HTTP_PORT:                 80
      ROUTER_SERVICE_NAME:                      router
      ROUTER_SERVICE_NAMESPACE:                 openshift
      ROUTER_SUBDOMAIN:
      STATS_PASSWORD:                           wrqNuG0PBH
      STATS_PORT:                               1936
      STATS_USERNAME:                           admin
Volumes:
  router-token-qk5ot:
    Type:       Secret (a secret that should populate this volume)
    SecretName: router-token-qk5ot
Events:
  FirstSeen     LastSeen        Count   From                    SubobjectPath   Type            Reason                  Message
  ---------     --------        -----   ----                    -------------   --------        ------                  -------
  45s           43s             2       {default-scheduler }                    Warning         FailedScheduling        pod (router-1-vzngh) failed to fit in any node
fit failure on node (node2.dev.local): MatchNodeSelector
fit failure on node (master.dev.local): PodFitsPorts
fit failure on node (node1.dev.local): MatchNodeSelector

  47s   31s     3       {default-scheduler }            Warning FailedScheduling        pod (router-1-vzngh) failed to fit in any node
fit failure on node (master.dev.local): PodFitsPorts
fit failure on node (node1.dev.local): MatchNodeSelector
fit failure on node (node2.dev.local): MatchNodeSelector

  15s   15s     1       {default-scheduler }            Warning FailedScheduling        pod (router-1-vzngh) failed to fit in any node
fit failure on node (node1.dev.local): MatchNodeSelector
fit failure on node (node2.dev.local): MatchNodeSelector
fit failure on node (master.dev.local): PodFitsPorts

Note: Based on the selector (--selector="region=infra"), it is scheduling it on the master node.

Both netstat -anlupt | grep 80 and netstat -anlupt | grep 443 shows that there is no service using port 80 and 443 on the master node. What could be the issue here as I have spend hours trying to figure out what went wrong.

Kind Regards!

--
Mfawa Alfred Onen
System Administrator / GDG Lead, Bingham University
Department of Computer Science,
Bingham University.

E-Mail: muffycompoqm gmail com
Phone1: +234 805 944 3154
Phone2: +234 803 079 6088
Twitter: @muffycompo
Google+: https://plus.google.com/+MfawaAlfredOnen

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]