search

redhat-developer-tooling / openshift-vagrant

All-in-One OpenShift Enterprise Vagrant setup
37 stars 32 forks source link

Docker login fails #68

Closed rafabene closed 8 years ago

rafabene commented 8 years ago

When I run on cdk-2-ose-3-2:

I receive the following error: 

Error response from daemon: Unexpected status code [503] : <html>
  <body>
    <h1>503 Service Unavailable</h1>
    No server available to handle the request.
  </body>
</html>
hferentschik commented 8 years ago

That's correct. There is a difference here between using OSE 3.1 and OSE 3.2. Since it seemed to only effect this use case, I decided to still push the update while investigating the cause. AFAICT the registry is started and exposed via a route. Also docker daemon seems to be registered properly. The error originates from the HPProxy.

Might be related to the reported issue of the underlying VM which delays the Beta5 release?!.

I am looking into it.

hferentschik commented 8 years ago

BTW, these are the things which the serverspec tests in the test directory nicely catch :-)

rafabene commented 8 years ago

I tried this recently and now I get the following error:

Unable to connect to the server: x509: certificate is valid for kubernetes, kubernetes.default, kubernetes.default.svc, kubernetes.default.svc.cluster.local, localhost, openshift, openshift.default, openshift.default.svc, openshift.default.svc.cluster.local, 10.0.2.15, 10.3.2.2, 127.0.0.1, 172.17.42.1, 172.30.0.1, not hub.openshift.10.3.2.2.xip.io

hferentschik commented 8 years ago

I tried this recently and now I get the following error:

That's probably caused by the vagrant-service-manager issues which existed in version 0.0.4 of the plugin. vagrant-service-manager 0.0.5 is out and should fix any TLS certificate mismatch issues.

hferentschik commented 8 years ago

docker login works also now with OSE 3.2. This was implicitly fixed by securing the registry. I also updated the tests a bit. Note, docker login seems to still fail sometimes in the tests. Not quite sure yet what the reason is for that.

Also, note that I removed the dedicated cdk-2-ose-3-2 directory. It was too hard to keep changes to Vagrantfile and test in sync. Now you can use OSE 3.2 from the main cdk-v2 directory by setting an environment variable:

$ cd cdk-v2
$ export SUB_USERNAME=<your-subscription-username>
$ export SUB_PASSWORD=<your-subscription-password>
$ export OPENSHIFT_VAGRANT_USE_OSE_3_2=true
$ vagrant up

See also the README.

P.S. You might want to try the Landrush approach for DNS as well. This avoids xip.ip. You can enable it via an ENV variable as well. I am interested in some feedback.