[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: OSE 3.2 - Registry - Unable to write



Can someone help here? Struck and unable to proceed next step

 

-- 

Srinivas Kotaru

 

From: skotaru <skotaru cisco com>
Date: Monday, June 6, 2016 at 8:24 PM
To: "dev lists openshift redhat com" <dev lists openshift redhat com>
Subject: OSE 3.2 - Registry - Unable to write

 

Hi

 

Just finished installing OSE 3.2.  Registry throwing below error while doing a sample deployment.

 

I0606 18:40:55.315293       1 sti.go:334] Successfully built alln-int-build-testing/cakephp-example-1:e6008a5f

I0606 18:40:55.335600       1 cleanup.go:23] Removing temporary directory /tmp/s2i-build044311744

I0606 18:40:55.335621       1 fs.go:156] Removing directory '/tmp/s2i-build044311744'

I0606 18:40:55.370335       1 sti.go:268] Using provided push secret for pushing 172.30.84.20:5000/alln-int-build-testing/cakephp-example:latest image

I0606 18:40:55.370389       1 sti.go:272] Pushing 172.30.84.20:5000/alln-int-build-testing/cakephp-example:latest image ...

I0606 18:40:57.016159       1 sti.go:277] Registry server Address:

I0606 18:40:57.016243       1 sti.go:278] Registry server User Name: serviceaccount

I0606 18:40:57.016255       1 sti.go:279] Registry server Email: serviceaccount example org

I0606 18:40:57.016262       1 sti.go:284] Registry server Password: <<non-empty>>

F0606 18:40:57.016273       1 builder.go:204] Error: build error: Failed to push image. Response from registry is: Received unexpected HTTP status: 500 Internal Server Error

 

Diagnostics on primary master throws below error

 

ERROR: [DClu1020 from diagnostic ClusterRegistry openshift/origin/pkg/diagnostics/cluster/registry.go:271]

       The pod logs for the "docker-registry-6-cqs51" pod belonging to

       the "docker-registry" service indicated the registry is unable to write to disk.

       This may indicate an SELinux denial, or problems with volume

       ownership/permissions.

 

       For volume permission problems please consult the Persistent Storage section

       of the Administrator's Guide.

 

       In the case of SELinux this may be resolved on the node by running:

 

           sudo chcon -R -t svirt_sandbox_file_t [PATH_TO]/openshift.local.volumes

 

       time="2016-06-06T19:00:08.144988457-04:00" level=error msg="response completed with error" err.code=UNKNOWN err.detail="filesystem: mkdir /registry/docker: permission denied" err.message="unknown error" go.version=go1.4.2 http.request.host="172.30.84.20:5000" http.request.id=7cb19403-49f5-4909-b287-582e60685bec http.request.method=POST http.request.remoteaddr="10.1.0.1:38212" http.request.uri="/v2/alln-int-build-testing/busybox/blobs/uploads/" http.request.useragent="docker/1.9.1 go/go1.4.2 kernel/3.10.0-327.13.1.el7.x86_64 os/linux arch/amd64" http.response.contenttype="application/json; charset=utf-8" http.response.duration=24.082081ms http.response.status=500 http.response.written=156 instance.id=45d786ad-d663-4dfc-8c8e-aa4455aab742 vars.name="alln-int-build-testing/busybox"

 

 

While further analsys, it seems NFS volume mounted on registry container has root:root permissions

 

# sudo docker exec -it 01b162687557 bash

 

bash-4.2$ ls -ld /registry/

drwxr-xr-x. 3 root root 4096 Jun  6 17:12 /registry/

 

I tried to change ownership , but no luck. What to do ? is it bug or intended behaviour?

 

bash-4.2$ whoami

whoami: cannot find name for user ID 1001

 

bash-4.2$ chown 1001 /registry/

chown: changing ownership of '/registry/': Operation not permitted

 

Srinivas Kotaru

 

 

-- 

Srinivas Kotaru


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]