Ah, that explains why this issue is random for me. I created this particular project directly via the API instead of the web console or ‘oc’ (testing an external provisioning tool) so the builder service account wasn’t automatically set up and assigned a role. Doh.
Thanks for the troubleshooting assistance. > On Apr 22, 2016, at 1:53 PM, Andy Goldstein <[email protected]> wrote: > > Hi Stephen, > > This is the key line from your log: > > OpenShift access denied: User \"system:serviceaccount:sbraswe1xzz:builder\" > cannot get imagestreams/layers in project \"sbraswe1xzz > > What is the output of `oadm policy who-can get imagestreams/layers -n > sbraswe1xzz`? > > Andy > > On Fri, Apr 22, 2016 at 1:51 PM, Braswell, Stephen <[email protected]> wrote: > Hi Andy, > > I don’t know if my issue is exactly the same as Gary’s but I have some > additional log data from when I was getting a similar error if it is helpful. > > https://gist.github.com/braswell/048b5a1d9c8b740673218188fe959545 > > > -Stephen > > > On Apr 19, 2016, at 3:27 PM, Andy Goldstein <[email protected]> wrote: > > > > Do you have more output from the registry's log? That "error" message is > > quite normal and doesn't actually indicate an error. It shows up when a > > Docker client first tries to talk to it without providing any credentials. > > The registry sends back an "unauthorized" response, so Docker then sends > > credentials. > > > > On Tue, Apr 19, 2016 at 12:05 PM, Gary Franczyk > > <[email protected]> wrote: > > Hi there. > > > > I'm attempting to push a docker image to the internal registry and am > > getting this error in the registry pod logs: > > > > > > time="2016-04-19T11:58:58.942610625-04:00" level=error msg="error > > authorizing context: authorization header with basic token required" > > go.version=go1.4 > > .2 http.request.host="172.30.142.84:5000" > > http.request.id=a4ecc601-9bc3-4f23-94b4-b2362555618b > > http.request.method=GET http.request.remoteaddr="10.1.1. > > 1:46873" http.request.uri="/v2/" http.request.useragent="docker/1.9.1 > > go/go1.4.2 kernel/3.10.0-327.10.1.el7.x86_64 os/linux arch/amd64" > > instance.id=74d > > e4ff9-2af6-496e-b033-52e9711a4bd6 > > > > > > > > I was able to successfully (as far as I can tell) login to the docker > > registry with "docker login". > > WARNING: login credentials saved in /root/.docker/config.json > > Login Succeeded > > I am using LDAP for authentication. > > > > Can anyone shed some light on this? Thanks! > > > > Gary Franczyk > > Senior Unix Administrator, Infrastructure > > > > Availity | 10752 Deerwood Park Blvd S. Ste 110, Jacksonville FL 32256 > > W 904.470.4953 | M 561.313.2866 > > [email protected] > > The information contained in this e-mail may be privileged and confidential > > under applicable law. It is intended solely for the use of the person or > > firm named above. If the reader of this e-mail is not the intended > > recipient, please notify us immediately by returning the e-mail to the > > originating e-mail address. Availity, LLC is not responsible for errors or > > omissions in this e-mail message. Any personal comments made in this e-mail > > do not reflect the views of Availity, LLC. > > _______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
