Can you gist the tail end of the registry pod log from when the push failed?

On Thursday, March 10, 2016, Tim Moor <[email protected]> wrote:

> Hey thanks Clayton,
>
> I’ve built  a fresh environment to ensure that this isn’t an isolated
> incident and it is displaying there as well.
>
> As I mentioned earlier I can see that data is being stored on the
> persistent volume, the 500 error seems to occur in the final commit phase
> of the push.
>
> I’ve also tried different users and projects and getting the same result.
>
> The logs are rather useless, any lead on where I can try next?
>
> Thanks
>
>
> On 10/03/2016, at 4:19 PM, Clayton Coleman <[email protected]
> <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote:
>
> error authorizing context: authorization header with basic token required"
>
>
> Is definitely not expected.  Did you do any sort of upgrade or change to
> the registry image?   What image is your registry pod using?
>
> On Mar 9, 2016, at 10:11 PM, Tim Moor <[email protected]
> <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote:
>
> Hey Guys, in the last few days we’ve been having issues with pushes to our
> OpenShift docker registry.
>
> On the client side we’ve pulled from docker, tagged for the destination
> including a name space that we are admins for and we’re getting the
> following error.
>
> oc login <enter details
>
> docker login -u $(oc whoami) -p $(oc whoami -t) registry.oso.infra.corp
> docker pull springnz/post_a_job:latest
> docker tag springnz/post_a_job:latest
> registry.oso.infra.corp/springnz/post_a_job:latest
> docker push registry.oso.infra.corp/springnz/post_a_job:latest
>
>
> Received unexpected HTTP status: 500 Internal Server Error
>
>
> From the oc get logs side we’re seeing the following level=error messages.
>
>
> 54 "response completed with error" err.code
>
> 16 "error authorizing context: authorization header with basic token
> required" go.version
>
> 6 "Error creating ImageStreamMapping: imagestreams \"ansible-runtime\" not
> found" go.version
>
> 4 "Error creating ImageStreamMapping: imagestreams \"centos-base\" not
> found" go.version
>
> 3 "Error creating ImageStreamMapping: imagestreams \"centos\" not found"
> go.version
>
>
>
> Environment
>
> - origin-1.1.3-0.git.0.8edc1be.el7.centos.x86_64
> - origin-clients-1.1.3-0.git.0.8edc1be.el7.centos.x86_64
> - origin-master-1.1.3-0.git.0.8edc1be.el7.centos.x86_64
> - origin-node-1.1.3-0.git.0.8edc1be.el7.centos.x86_64
> - origin-sdn-ovs-1.1.3-0.git.0.8edc1be.el7.centos.x86_64
>
>
>
>
> oc get pods docker-registry-??
>
> "metadata": {
>        "name": "docker-registry-4-ye8hi",
>        "generateName": "docker-registry-4-",
>        "namespace": "default",
>        "selfLink":
> "/api/v1/namespaces/default/pods/docker-registry-4-ye8hi",
>        "uid": "55ad28f5-e65e-11e5-98e9-001a4a160178",
>        "resourceVersion": "2393",
>        "creationTimestamp": "2016-03-10T01:20:54Z",
>        "labels": {
>            "deployment": "docker-registry-4",
>            "deploymentconfig": "docker-registry",
>            "docker-registry": "default"
>        },
>        "annotations": {
>            "kubernetes.io/created-by":
> "{\"kind\":\"SerializedReference\",\"apiVersion\":\"v1\",\"reference\":{\"kind\":\"ReplicationController\",\"namespace\":\"default\",\"name\":\"docker-registry-4\",\"uid\":\"52e32262-e65e-11e5-98e9-001a4a160178\",\"apiVersion\":\"v1\",\"resourceVersion\":\"1996\"}}\n",
>            "openshift.io/deployment-config.latest-version": "4",
>            "openshift.io/deployment-config.name": "docker-registry",
>            "openshift.io/deployment.name": "docker-registry-4",
>            "openshift.io/scc": "restricted"
>        }
>    },
>
>
> Thanks
>
> Tim
>
>
> _______________________________________________
> users mailing list
> [email protected]
> <javascript:_e(%7B%7D,'cvml','[email protected]');>
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>
>
_______________________________________________
users mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Reply via email to