Re: Error updating deployment [deploy] status to Pending

[Stéphane Klein]

I see that in origin-node log:

```
mai 20 09:52:21 openshift-master-1.priv.tech-angels.net origin-node[1238]:
E0520 09:52:21.4046571238 event.go:192] Server rejected event
'{TypeMeta:unversioned.TypeMeta{Kind:"", APIVersion:""},
ObjectMeta:api.ObjectMeta{Name:"openshift-master-1.priv.tech-angels.net.144f81b48964418e",
GenerateName:"", Namespace:"default", SelfLink:"", UID:"",
ResourceVersion:"7644318", Generation:0,
CreationTimestamp:unversioned.Time{Time:time.Time{sec:0, nsec:0,
loc:(*time.Location)(nil)}}, DeletionTimestamp:(*unversioned.Time)(nil),
DeletionGracePeriodSeconds:(*int64)(nil), Labels:map[string]string(nil),
Annotations:map[string]string(nil)},
InvolvedObject:api.ObjectReference{Kind:"Node", Namespace:"", Name:"
openshift-master-1.priv.tech-angels.net", UID:"
openshift-master-1.priv.tech-angels.net", APIVersion:"",
ResourceVersion:"", FieldPath:""}, Reason:"NodeHasSufficientDisk",
Message:"Node openshift-master-1.priv.tech-angels.net status is now:
NodeHasSufficientDisk", Source:api.EventSource{Component:"kubelet", Host:"
openshift-master-1.priv.tech-angels.net"},
FirstTimestamp:unversioned.Time{Time:time.Time{sec:63599127816, nsec:0,
loc:(*time.Location)(0x56a0960)}},
LastTimestamp:unversioned.Time{Time:time.Time{sec:63599327541,
nsec:367959378, loc:(*time.Location)(0x56a0960)}}, Count:2,
Type:"Normal"}': 'events
"openshift-master-1.priv.tech-angels.net.144f81b48964418e" not found' (will
not retry!)
mai 20 10:01:58 openshift-master-1.priv.tech-angels.net origin-node[1238]:
E0520 10:01:58.2410641238 kubelet.go:2654] Error updating node status,
will retry: error #0: client: etcd member
https://openshift-etcd-1.priv.tech-angels.net:2379 has no leader
```


2016-05-20 11:23 GMT+02:00 Philippe Lafoucrière <
philippe.lafoucri...@tech-angels.com>:

> Hi,
>
> Yes the node is ready. I have tried to unschedule it, and evacuate pods,
> it's not working either. I  don't use any PV in the test I'm doing. The
> other node seems to have the same problem, so I guess it's somewhere else
> than the node. Maybe corrupted data in etcd?
> This cluster has been working for months now, I don't understand why it's
> suddenly failing. I have absolutely no clue.
> Thanks
>
>
>
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>


-- 
Stéphane Klein 
blog: http://stephane-klein.info
cv : http://cv.stephane-klein.info
Twitter: http://twitter.com/klein_stephane
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Error updating deployment [deploy] status to Pending

[Philippe Lafoucrière]

Hi,

Yes the node is ready. I have tried to unschedule it, and evacuate pods,
it's not working either. I  don't use any PV in the test I'm doing. The
other node seems to have the same problem, so I guess it's somewhere else
than the node. Maybe corrupted data in etcd?
This cluster has been working for months now, I don't understand why it's
suddenly failing. I have absolutely no clue.
Thanks
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Error updating deployment [deploy] status to Pending

[Skarbek, John]

Philippe,

Is the node in a Ready state?

The log output you posted makes it seem like something isn’t working properly 
if it keeps reading a config file over and over.

Are you able to start pods that do not utilize a PV?


--
John Skarbek


On May 19, 2016 at 16:43:16, Philippe Lafoucrière 
(philippe.lafoucri...@tech-angels.com)
 wrote:

If I make this node unschedulable, I get an event: "node 'openshift-node-1' is 
not in cache"
Does this ring a bell? (and the pod is still pending)
For the record, there's PV used in this pod, and all pods have the same 
behavior now on this cluster. Only a restart of origin-node can unlock them.
​Thanks
___
users mailing list
users@lists.openshift.redhat.com
https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openshift.redhat.com_openshiftmm_listinfo_users=DQICAg=_hRq4mqlUmqpqlyQ5hkoDXIVh6I6pxfkkNxQuL0p-Z0=8IlWeJZqFtf8Tvx1PDV9NsLfM_M0oNfzEXXNp-tpx74=jLh1X9RvUZ4CzmdQ7elsOeY1CR-qoLimd877VlHjB6k=9WbmAPFRTGUQFaa5BonKWxuoR1_O_IEXYHq6UiaFwGg=
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Error updating deployment [deploy] status to Pending

[Philippe Lafoucrière]

If I make this node unschedulable, I get an event: "node 'openshift-node-1'
is not in cache"
Does this ring a bell? (and the pod is still pending)
For the record, there's PV used in this pod, and all pods have the same
behavior now on this cluster. Only a restart of origin-node can unlock them.
​Thanks
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Error updating deployment [deploy] status to Pending

[Philippe Lafoucrière]

I have this in the logs (with loglevel=4):
https://gist.github.com/gravis/7454a743cb988f6d192bf5a5c9890a82
So, nothing fancy :(

Thanks
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Error updating deployment [deploy] status to Pending

[Philippe Lafoucrière]

Hello,

I can't deploy any on os 1.1.3: the deploy (and/or build) is stuck on
pending, with the message:

Error updating deployment [project]/[deploy] status to Pending

in the events. Nothing specific in the logs.
Using oc describe doesn't give any reason, and I see a different event:

Events:
  FirstSeen LastSeenCount   From
 SubobjectPath   TypeReason  Message
  - -   
 -   --  ---
  6m6m  1   {default-scheduler }
 Normal  Scheduled   Successfully assigned
slots-site-8-deploy to node-1

The deploy is starting if I restart origin-node on node-1. If I deploy
again, I get stuck at the same place, and only a origin-node restart can
unlock it.

Any hints to fix that?

Thanks
Philippe
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users