Looks like "etcd member [...] has no leader" is the key here...
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
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
'&api.Event{TypeMeta:unversioned.TypeMeta{Kind:"", APIVersion:""},
ObjectMeta:api.ObjectMeta{Name:"openshift-master-1.priv
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
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
(phi
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.
Th
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
This seems like the node is "stuck" in that it didn't see the updated
pod, or didn't think it accepted it. What log level are you at on
your node? At level 4, when you get "stuck" what shows up at the node
log?
On Tue, May 17, 2016 at 8:22 PM, Philippe Lafoucrière
wrote:
> Hello,
>
> I can't de
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:
F
