-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Digital Ocean external volume test failing #529
Comments
And here is the message from the pod, PVC, and PVC:
And both the |
And the logs on the node are telling me this:
|
Probably the same DNS issue as in #527, the flexplugin which is run by Please run: |
Thanks. Here's the results of those two queries.
|
Ìs all pods in the |
Hi @klausenbusk: thanks for the quick response. They're all running quite hapily:
|
And FYI, kube-controller-manager has public nameservers.
|
Is networking working inside that pod? Ex: curling |
Yes, if the nameserver's work, I can get curl. Note: even on the
|
Hmm.. Please check the log of |
Sorry, I got a little lost and it took me a while to find where I was. To answer your questions:
My client is OSX and the master and nodes are running Ubuntu 16. Here are the last 30 lines from
|
No problem..
Not anything useful, the errors is probably more than 50 lines back. BTW: What version of flannel is you using? flannel v0.9.1 contain a fix, which could explain the DNS issue: flannel-io/flannel#872 It would be a lot easier to help with direct access to the cluster.. |
I'm running flannel Here are the last 200 lines:
|
Still not anything interesting, weird.. hmm |
@klausenbusk: I think I have the interesting error you've been looking for. Upgraded the server to use flannel
showing that the pod is still stuck. And here are the results of
(or at least the last 100 lines thereof):
|
Could you run |
Here it is:
|
Could you run |
Sure! The results appear to be the same:
|
Could you run the same command inside the |
And in case you're curious:
|
And for your previous question:
There's just that one file. |
Aha, that explain it. |
That works!
And the result of spinning up a pod with a PVC:
Thanks so much for the tireless debugging @klausenbusk! Should I add this to the |
No problem.
It should definitely be documented to help users. Maybe as a Note under point 3:
I use Regard |
I have opened a issue to keep track of it: #531 , as said before: feel free to open a PR. |
Done! |
/area digitalocean Just for the record. |
I built a PV and connected to Digital Ocean as per the README.md. Aside from a small DNS fix, this has worked. However, I am unable to successfully complete the last two steps in the README.md
The PVC appears to successfully bind but the pod does not start up:
and it appears to never want to startup.
busy-pod2
is the same pod but without the external mountingFYI: using commit
ce571982aeedba29185048b8398fab90116f2d29
. Let me know if you have any ideas @klausenbusk.The text was updated successfully, but these errors were encountered: