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

Re: Router Pod stuck at pending



Hello,

I ponder if there’s an issue with the labels being utilized by the nodes and the pods. Can you run the following command: oc get nodes —show-labels

And then an: oc describe dc router



-- 
John Skarbek

On April 7, 2016 at 04:26:37, Mfawa Alfred Onen (muffycompoqm gmail com) wrote:

So I enabled scheduling as you pointed out but still no luck:

oc get nodes

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

oc get pods

docker-registry-2-pbvcf   1/1       Running   0          10h
router-1-bk55a            0/1       Pending   0          1s
router-1-deploy           1/1       Running   0          4s

oc describe pod router-1-bk55a

<Showing only Event logs>
Events:
  FirstSeen     LastSeen        Count   From                    SubobjectPath   Type            Reason                  Message
  ---------     --------        -----   ----                    -------------   --------        ------                  -------
  1m            1m              1       {default-scheduler }                    Warning         FailedScheduling        pod (router-1-bk55a) failed to fit in any node
fit failure on node (master.dev.local): PodFitsPorts
fit failure on node (node1.dev.local): Region
fit failure on node (node2.dev.local): MatchNodeSelector

  1m    1m      1       {default-scheduler }            Warning FailedScheduling        pod (router-1-bk55a) 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

  1m    1m      2       {default-scheduler }            Warning FailedScheduling        pod (router-1-bk55a) failed to fit in any node
fit failure on node (master.dev.local): PodFitsPorts
fit failure on node (node1.dev.local): Region
fit failure on node (node2.dev.local): Region

  47s   47s     1       {default-scheduler }            Warning FailedScheduling        pod (router-1-bk55a) failed to fit in any node
fit failure on node (node1.dev.local): Region
fit failure on node (node2.dev.local): Region
fit failure on node (master.dhcpaas.com): PodFitsPorts

  1m    15s     2       {default-scheduler }            Warning FailedScheduling        pod (router-1-bk55a) 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): Region


Regards!


On Thu, Apr 7, 2016 at 8:01 AM, Tobias Florek <openshift ibotty net> wrote:
Hi.

I assume your router does not get scheduled on master.dev.local, because
scheduling is disabled there:

> *1. oc get nodes*
>
> NAME                 STATUS                     AGE
> master.dev.local   Ready,SchedulingDisabled   8d

Run

    oadm manage-node master.dev.local --schedulable=true

to enable pods to run on your master.

Cheers,
 Tobias Florek



--
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
_______________________________________________
users mailing list
users lists openshift redhat com
https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openshift.redhat.com_openshiftmm_listinfo_users&d=CwICAg&c=_hRq4mqlUmqpqlyQ5hkoDXIVh6I6pxfkkNxQuL0p-Z0&r=8IlWeJZqFtf8Tvx1PDV9NsLfM_M0oNfzEXXNp-tpx74&m=Kvu7h4NH0VKpICUhIHRvPYCilfYCENeI2O51tCkTZy4&s=0WL53uxKYHilIXS-LCdwwWsrnLspLh5l5njDeBw48m8&e=


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