Red Hat Bugzilla – Bug 1196777
Can't connect to docker compute resource (Docker::Error::AuthenticationError)
Last modified: 2017-02-23 15:25:31 EST
Description of problem: I think this might be due to some packages on RHEL6 or something. Not sure. Version-Release number of selected component (if applicable): Nightly build. Here's the docker-related packages: pulp-docker-plugins-0.2.2-1.el6.noarch ruby193-rubygem-foreman_docker-1.2.0-1.fm1_8.el6.noarch python-pulp-docker-common-0.2.2-1.el6.noarch ruby193-rubygem-docker-api-1.17.0-1.el6.noarch docker-io-1.4.1-3.el6.x86_64 How reproducible: Always. Steps to Reproduce: 1. Set up the nightly build on RHEL6 with these options in /etc/sysconfig/docker: other_args='--selinux-enabled=true --host tcp://0.0.0.0:2375 --host unix:///var/run/docker.sock' DOCKER_CERT_PATH=/etc/docker 2. Create a compute resource 3. Click on Test Connection Actual results: Docker::Error::AuthenticationError Docker log: ERRO[0014] Handler for POST /auth returned error: Registration: "Missing username field" ERRO[0014] HTTP Error: statusCode=500 Registration: "Missing username field" Expected results: Success Additional info:
The url for the compute resource is http://localhost:2375
Looks like the problem is the new fog version. Got a fix for it.
Make sure you're running the same versions of fog and docker-api as in the nightlies.
Created redmine issue http://projects.theforeman.org/issues/9570 from this bug
Pull request: https://github.com/theforeman/foreman-docker/pull/90
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
Moving to POST since upstream bug http://projects.theforeman.org/issues/9570 has been closed ------------- David Davis Applied in changeset commit:foreman-docker|6789456ca82b33c933fec94f2fc8383edd2779d3.
Verified on: Satellite-6.1.0-RHEL-7-20150303.0 Steps to verify: 1. Navigated to Infrastructure > Compute Resources 2. Clicked on New Compute Resource 3. Filled the form with values: Name: MyComputeResource Provider: Docker URL: http://localhost:2375 4. Clicked on Test Connection and no error was raised 5. Created the Compute Resource and checked the Virtual Machines tab to check if it does not show any error. All was OK.
This bug is slated to be released with Satellite 6.1.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2015:1592