So I went ahead and restarted origin-master and also origin-node.... now I get a different error from builds:
I0301 06:38:23.333131 1 docker.go:117] Pushing image 172.30.143.204:5000/web04-app/web04:latest ... 52 F0301 06:38:23.360279 1 builder.go:204] Error: build error: Failed to push image: Post http://172.30.143.204:5000/v2/web04-app/web04/blobs/uploads/: no basic auth credentials On Tue, Mar 1, 2016 at 1:25 AM, Mohamed Lrhazi < [email protected]> wrote: > Also, in the documentation: > > > https://docs.openshift.org/latest/install_config/install/docker_registry.html#storage-for-the-registry > > This example, the name "v1".. is that a mistake? should it not > be: registry-storage > > In: > > PRODUCTION USE > > For production use, attach a remote volume or define and use the > persistent storage method of your choice > <https://docs.openshift.org/latest/install_config/persistent_storage/index.html> > . > > For example, to use an existing persistent volume claim: > > $ oc volume deploymentconfigs/docker-registry --add --name=v1 -t pvc \ > --claim-name=<pvc_name> --overwrite > > > On Tue, Mar 1, 2016 at 1:09 AM, Mohamed Lrhazi < > [email protected]> wrote: > >> One more issue... now that the registry seems to be back up... >> rebuilding, even recreating, a test project I have, seems to fail as if the >> registry IP it is trying to push to is wrong? >> >> ... >> Successfully built 502ed8ccfb26 >> I0301 05:59:50.642747 1 docker.go:117] Pushing image >> 172.30.105.149:5000/web04-app/web04:latest ... >> F0301 06:00:05.685281 1 builder.go:204] Error: build error: Failed >> to push image: Put >> http://172.30.105.149:5000/v1/repositories/web04-app/web04/: dial tcp >> 172.30.105.149:5000: no route to host >> >> >> [root@openshift-1 ~]# oc get service docker-registry >> NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR >> AGE >> docker-registry 172.30.143.204 <none> 5000/TCP >> docker-registry=default 22h >> [root@openshift-1 ~]# >> >> >> What else am I missing ? >> >> Thanks a lot, >> Mohamed. >> >> On Tue, Mar 1, 2016 at 12:21 AM, Mohamed Lrhazi < >> [email protected]> wrote: >> >>> Yes! entrypoints did it! re added the service too. Thanks a lot. >>> >>> On Mon, Feb 29, 2016 at 7:22 PM, Philippe Lafoucrière < >>> [email protected]> wrote: >>> >>>> ok, did you create the glusterfs endpoint in the corresponding project >>>> (yes, you have to do that for all projects using glusterfs...). >>>> Last but not least, remember to add a glusterfs service to ensure your >>>> endpoints are not deleted: >>>> >>>> >>>> apiVersion: v1 >>>> kind: Endpoints >>>> metadata: >>>> name: glusterfs-cluster >>>> subsets: >>>> - addresses: >>>> - ip: [glusterfs-node-1] >>>> - ip: [glusterfs-node-2] >>>> - ip: [...] >>>> ports: >>>> - port: 1 >>>> protocol: TCP >>>> >>>> >>>> apiVersion: v1 >>>> kind: Service >>>> metadata: >>>> name: glusterfs-cluster >>>> spec: >>>> ports: >>>> - port: 1 >>>> protocol: TCP >>>> targetPort: 1 >>>> >>>> >>> >> >
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
