-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
running one of the examples against an OS X build of openshift v3 doesn't seem to work #180
Comments
The above worked for me on OS X right now with HEAD == 043e5c6. I wonder what caused //EDIT: Output from the server (openshift start cmd) would be great too! |
Could you try running |
I get the same when trying a sample pods.json too
|
|
Happy to try any command line / JSON files you think might work :) |
|
@jstrachan can you attach the output of the |
I don't see any new output when I try the "kube process" or "create pods" commands now. I stopped and started openshift and tried these commands and got no new errors:
Here's the entire output I got from the first attempt at running 'openshift start' with the previous commands in previous comments:
|
There's a bunch of HTTP connection failures. Can you make sure this isn't a firewall issue? Could you turn the firewall off temporarily? |
OK I tried not being on the VPN; restarting from a clean directory openshift then I tried creating a pod
Shouldn't it be "/api/v1beta1/pods?labels="? Am wondering if this is some OS X thing? FWIW I can view this fine in a browser: http://127.0.0.1:8080/api/v1beta1/pods?labels=
FWIW I didn't see any new error messages in the shell running "openshift start" - I think those previous watch issues are either a VPN issue or a red herring:
I tried the template command and again got no errors in the "openshift start" log:
Again I wonder if "/v1beta1/templateConfigs" is wrong (its missing the "/osapi" prefix). I can view http://127.0.0.1:8080/osapi/v1beta1/templateConfigs fine in a browser:
|
BTW I tried running all the various tests and they seemed fine on my OS X box
|
FWIW here's the output of "openshift" start after running the above tests. Via the REST API I can see the various pods / replication controllers / services from the integration test; though can't ping them from my Mac (though can do inside boot2docker). Am thinking its maybe better to run "openshift start" inside vagrant as my host can't see the pods IP address (as its running inside boot2docker) :). It'd be awesome if we could figure out a way to fix the networking so the host can see those IPs...
|
BTW I thought I'd try the vagrant image instead. I wonder if there is some gremlin in the "openshift kube..." commands?
and
|
I've just run through the steps using OSX and yeah I can see the hello world page in boot2docker but not localhost. I also saw some of the errors in you logs @jstrachan http://localhost:6061/ - page not found
I also see the below JSON with http://127.0.0.1:8080/osapi/v1beta1/templateConfigs
pod list - http://127.0.0.1:8080/api/v1beta1/pods?labels=
|
FWIW I'm thinking this isn't anything to do with OS X; its more underlying "openshift kube " CLI issues? |
@rawlingsj I raised a separate #182 to track the Pod IP address issue when using non-linux and boot2docker |
@jstrachan yes, given the |
@jstrachan fyi, the |
@VojtechVitek BTW are you using an up to date master of openshift/origin? I get these same errors in vagrant too. I think these are just gremlins in the kube CLI client though.... |
@jstrachan can you try
and
|
Here you go:
|
BTW the above was the output of me running hack/test-cmd.sh btw :) |
I think I got it. Since you have I will have a fix for this later today. @jstrachan @rawlingsj Thanks for the detailed reports. Much appreciated! |
AHA!!!! Many thanks @VojtechVitek - sorry for not spotting that! |
adding this fixes everything here too:
|
Minor: pod-network CLI examples to use # for comments
I just built master of openshift origin V3; ran openshift start.
then I did this based on the README.md
Is this a known issue? I've found using vanilla kube examples for pods didn't seem to work either. Wonder if its known or an OS X issue (or just a bad example?)
The text was updated successfully, but these errors were encountered: