Re: Hard Disk is full because of OpenShift Origin

[Tien Hung Nguyen]

I have checked the volumes already using the docker command docker volume ls. 
However, everything seems pretty normal there.

Furthermore, I have checked my images with docker images ls. I have found a lot 
of old images created by OpenShift, which used a lot of GBs on my Hard Disk. 
That‘s why I started to manually delete those images with the docker command: 
docker rmi [imageid], but that didn‘t change my hard disk space at all. 

Do you have any other ideas?

> Am 27.10.2017 um 01:24 schrieb Graham Dumpleton :
> 
> See if you have a lot of docker volumes that haven't been cleaned up properly.
> 
>docker volume ls
> 
> Maybe that is hanging onto space.
> 
> Graham
> 
>> On 27 Oct 2017, at 8:37 am, Tien Hung Nguyen  
>> wrote:
>> 
>> Hi everybody,
>> 
>> I have a problem with my hard drive space. Since I'm using OpenShift locally 
>> with Docker, I have the problem that my hard drive space gets full very fast 
>> and I can't remove it. I have already run the commands 'oc cluster down' and 
>> the 'docker rmi [imageip] commands to deleted unused images but it has no 
>> effect.
>> 
>> Please, could you tell me how to free up my disk space properly?
>> 
>> Thank you!
>> 
>> ___
>> users mailing list
>> users@lists.openshift.redhat.com
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
> 

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Hard Disk is full because of OpenShift Origin

[Graham Dumpleton]

See if you have a lot of docker volumes that haven't been cleaned up properly.

docker volume ls

Maybe that is hanging onto space.

Graham

> On 27 Oct 2017, at 8:37 am, Tien Hung Nguyen  wrote:
> 
> Hi everybody,
> 
> I have a problem with my hard drive space. Since I'm using OpenShift locally 
> with Docker, I have the problem that my hard drive space gets full very fast 
> and I can't remove it. I have already run the commands 'oc cluster down' and 
> the 'docker rmi [imageip] commands to deleted unused images but it has no 
> effect.
> 
> Please, could you tell me how to free up my disk space properly?
> 
> Thank you!
> 
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users


___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Hard Disk is full because of OpenShift Origin

[Tien Hung Nguyen]

Hi everybody,

I have a problem with my hard drive space. Since I'm using OpenShift
locally with Docker, I have the problem that my hard drive space gets full
very fast and I can't remove it. I have already run the commands 'oc
cluster down' and the 'docker rmi [imageip] commands to deleted unused
images but it has no effect.

Please, could you tell me how to free up my disk space properly?

Thank you!
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: OCP: Failed to push image: unauthorized: authentication req, uired

[Lionel Orellana]

Ah I think when I first installed the Origin cluster there were all these
problems with the registry ip and the proxy so I created the registry form
a yml file (to keep the ip consistent) and that yml file didn't set the
proxy vars. These problems are gone now that the default registry is set to
the service name instead of the ip. But it does mean proxy vars are added
to the registry deployment.

On 27 October 2017 at 07:45, Lionel Orellana  wrote:

> I have an Origin 3.6 cluster and the proxy vars are not set in the
> registry pod at all.
>
> -bash-4.2$ oc rsh docker-registry-9-c9mgd env | grep PROXY
>
> -bash-4.2$
>
> Whereas in the OCP 3.6 cluster they are.
>
> -bash-4.2$ oc rsh docker-registry-1-9z8p2 env | grep PROXY
> NO_PROXY=.x,.cluster.local,.svc,172.19.10.100,172.
> 19.10.202,172.19.10.203
> HTTP_PROXY=http://x
> HTTPS_PROXY=http://xxx
>
> Instead of adding the api server address to NO_PROXY I might as well
> remove all the proxy vars ? Why would the registry need a proxy anyway?
>
> On 26 October 2017 at 22:55, Ben Parees  wrote:
>
>>
>>
>> On Thu, Oct 26, 2017 at 12:43 PM, Lionel Orellana 
>> wrote:
>>
>>> This works.Would have thought the api server address was added
>>> automatically to NO_PROXY?
>>>
>>
>> it's supposed to be, but i do think there is a bug open where people have
>> seen it not be added:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1504464
>>
>>
>>
>>>
>>> -bash-4.2$ oc rsh docker-registry-1-9z8p2
>>> sh-4.2$ export NO_PROXY=$NO_PROXY,172.23.192.1
>>> sh-4.2$ oc whoami
>>> system:serviceaccount:default:registry
>>> sh-4.2$
>>>
>>> On 26 October 2017 at 20:54, Ben Parees  wrote:
>>>


 On Thu, Oct 26, 2017 at 11:50 AM, Lionel Orellana 
 wrote:

> I didn't put it there.
>
> I another cluster this works.
>
> -bash-4.2$ oc rsh docker-registry-9-c9mgd oc whoami
> system:serviceaccount:default:registry
>
> -bash-4.2$ oc rsh docker-registry-9-c9mgd which oc
> /usr/bin/oc
>
>
 ok, it looks like it was removed on 3.7.

 Anyway you've certainly established there is a networking issue between
 your registry pod and the api server in your cluster
 (but oddly not between other pods an the api server)  Adding the
 networking team to the thread.




>
> On 26 October 2017 at 20:37, Ben Parees  wrote:
>
>>
>>
>> On Thu, Oct 26, 2017 at 10:53 AM, Lionel Orellana > > wrote:
>>
>>> Interestingly
>>>
>>> -bash-4.2$ oc rsh router-1-bf95x oc whoami
>>> system:serviceaccount:default:router
>>> -bash-4.2$ oc rsh docker-registry-1-9z8p2 oc whoami
>>> Unable to connect to the server: Service Unavailable
>>> command terminated with exit code 1
>>>
>>
>> the registry image doesn't even contain an oc client binary (unless
>> you put one there?) so i'm not sure what that is doing.
>>
>>
>>
>>>
>>> On 26 October 2017 at 19:50, Lionel Orellana 
>>> wrote:
>>>
 Well this works from one of the hosts (using a token from oc whoami)

 curl -X GET -H "Authorization: Bearer $TOKEN"
 https://172.23.192.1/oapi/v1/users/~

 In the error msg

 msg="*invalid token*: Get https://172.23.192.1:443/oapi/v1/users/~
 : Service Unavailable"

 I wonder if the invalid toke part is the issue.

 On 26 October 2017 at 19:16, Ben Parees  wrote:

>
>
> On Thu, Oct 26, 2017 at 8:11 AM, Lionel Orellana <
> lione...@gmail.com> wrote:
>
>> Hi,
>>
>> In a new OCP 3.6 installation I'm trying to deploy JBoss EAP 7.0
>> from the catalog.
>>
>> This is in a project for which I am the admin.
>>
>> It's failing to push the image to the registry
>>
>> Pushing image 
>> docker-registry.default.svc:5000/bimorl/jboss-eap70:latest
>> ...
>> Registry server Address:
>> Registry server User Name: serviceaccount
>> Registry server Email: serviceacco...@example.org
>> Registry server Password: <>
>> error: build error: Failed to push image: unauthorized:
>> authentication required
>>
>
>> In the registry logs I see
>>
>> 172.23.140.1 - - [26/Oct/2017:05:08:19 +] "GET
>> /openshift/token?account=serviceaccount=repository%3Ab
>> imorl%2Fjboss-eap70%3Apush%2Cpull HTTP/1.1" 401 0 ""
>> "docker/1.12.6 go/go1.8.3 kernel/3.10.0-693.2.2.el7.x86_64
>> os/linux arch/amd64 UpstreamClient(go-dockerclient)"
>> time="2017-10-26T05:08:19.116844289Z" level=debug 

Re: OCP: Failed to push image: unauthorized: authentication req, uired

[Ben Parees]

On Thu, Oct 26, 2017 at 10:45 PM, Lionel Orellana 
wrote:

> I have an Origin 3.6 cluster and the proxy vars are not set in the
> registry pod at all.
>
> -bash-4.2$ oc rsh docker-registry-9-c9mgd env | grep PROXY
>
> -bash-4.2$
>
> Whereas in the OCP 3.6 cluster they are.
>
> -bash-4.2$ oc rsh docker-registry-1-9z8p2 env | grep PROXY
> NO_PROXY=.x,.cluster.local,.svc,172.19.10.100,172.
> 19.10.202,172.19.10.203
> HTTP_PROXY=http://x
> HTTPS_PROXY=http://xxx
>
> Instead of adding the api server address to NO_PROXY I might as well
> remove all the proxy vars ? Why would the registry need a proxy anyway?
>

the registry calls out to external registries to do pullthrough of images,
so if your cluster needs a proxy to reach the outside world, the registry
needs that proxy config.



>
> On 26 October 2017 at 22:55, Ben Parees  wrote:
>
>>
>>
>> On Thu, Oct 26, 2017 at 12:43 PM, Lionel Orellana 
>> wrote:
>>
>>> This works.Would have thought the api server address was added
>>> automatically to NO_PROXY?
>>>
>>
>> it's supposed to be, but i do think there is a bug open where people have
>> seen it not be added:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1504464
>>
>>
>>
>>>
>>> -bash-4.2$ oc rsh docker-registry-1-9z8p2
>>> sh-4.2$ export NO_PROXY=$NO_PROXY,172.23.192.1
>>> sh-4.2$ oc whoami
>>> system:serviceaccount:default:registry
>>> sh-4.2$
>>>
>>> On 26 October 2017 at 20:54, Ben Parees  wrote:
>>>


 On Thu, Oct 26, 2017 at 11:50 AM, Lionel Orellana 
 wrote:

> I didn't put it there.
>
> I another cluster this works.
>
> -bash-4.2$ oc rsh docker-registry-9-c9mgd oc whoami
> system:serviceaccount:default:registry
>
> -bash-4.2$ oc rsh docker-registry-9-c9mgd which oc
> /usr/bin/oc
>
>
 ok, it looks like it was removed on 3.7.

 Anyway you've certainly established there is a networking issue between
 your registry pod and the api server in your cluster
 (but oddly not between other pods an the api server)  Adding the
 networking team to the thread.




>
> On 26 October 2017 at 20:37, Ben Parees  wrote:
>
>>
>>
>> On Thu, Oct 26, 2017 at 10:53 AM, Lionel Orellana > > wrote:
>>
>>> Interestingly
>>>
>>> -bash-4.2$ oc rsh router-1-bf95x oc whoami
>>> system:serviceaccount:default:router
>>> -bash-4.2$ oc rsh docker-registry-1-9z8p2 oc whoami
>>> Unable to connect to the server: Service Unavailable
>>> command terminated with exit code 1
>>>
>>
>> the registry image doesn't even contain an oc client binary (unless
>> you put one there?) so i'm not sure what that is doing.
>>
>>
>>
>>>
>>> On 26 October 2017 at 19:50, Lionel Orellana 
>>> wrote:
>>>
 Well this works from one of the hosts (using a token from oc whoami)

 curl -X GET -H "Authorization: Bearer $TOKEN"
 https://172.23.192.1/oapi/v1/users/~

 In the error msg

 msg="*invalid token*: Get https://172.23.192.1:443/oapi/v1/users/~
 : Service Unavailable"

 I wonder if the invalid toke part is the issue.

 On 26 October 2017 at 19:16, Ben Parees  wrote:

>
>
> On Thu, Oct 26, 2017 at 8:11 AM, Lionel Orellana <
> lione...@gmail.com> wrote:
>
>> Hi,
>>
>> In a new OCP 3.6 installation I'm trying to deploy JBoss EAP 7.0
>> from the catalog.
>>
>> This is in a project for which I am the admin.
>>
>> It's failing to push the image to the registry
>>
>> Pushing image 
>> docker-registry.default.svc:5000/bimorl/jboss-eap70:latest
>> ...
>> Registry server Address:
>> Registry server User Name: serviceaccount
>> Registry server Email: serviceacco...@example.org
>> Registry server Password: <>
>> error: build error: Failed to push image: unauthorized:
>> authentication required
>>
>
>> In the registry logs I see
>>
>> 172.23.140.1 - - [26/Oct/2017:05:08:19 +] "GET
>> /openshift/token?account=serviceaccount=repository%3Ab
>> imorl%2Fjboss-eap70%3Apush%2Cpull HTTP/1.1" 401 0 ""
>> "docker/1.12.6 go/go1.8.3 kernel/3.10.0-693.2.2.el7.x86_64
>> os/linux arch/amd64 UpstreamClient(go-dockerclient)"
>> time="2017-10-26T05:08:19.116844289Z" level=debug msg="invalid
>> token: Get https://172.23.192.1:443/oapi/v1/users/~: *Service
>> Unavailable*" go.version=go1.7.6 
>> http.request.host="docker-registry.default.svc:5000"
>> 

Re: OCP: Failed to push image: unauthorized: authentication req, uired

[Lionel Orellana]

I have an Origin 3.6 cluster and the proxy vars are not set in the registry
pod at all.

-bash-4.2$ oc rsh docker-registry-9-c9mgd env | grep PROXY
-bash-4.2$

Whereas in the OCP 3.6 cluster they are.

-bash-4.2$ oc rsh docker-registry-1-9z8p2 env | grep PROXY
NO_PROXY=.x,.cluster.local,.svc,172.19.10.100,172.19.10.202,172.19.10.203
HTTP_PROXY=http://x
HTTPS_PROXY=http://xxx

Instead of adding the api server address to NO_PROXY I might as well remove
all the proxy vars ? Why would the registry need a proxy anyway?

On 26 October 2017 at 22:55, Ben Parees  wrote:

>
>
> On Thu, Oct 26, 2017 at 12:43 PM, Lionel Orellana 
> wrote:
>
>> This works.Would have thought the api server address was added
>> automatically to NO_PROXY?
>>
>
> it's supposed to be, but i do think there is a bug open where people have
> seen it not be added:
> https://bugzilla.redhat.com/show_bug.cgi?id=1504464
>
>
>
>>
>> -bash-4.2$ oc rsh docker-registry-1-9z8p2
>> sh-4.2$ export NO_PROXY=$NO_PROXY,172.23.192.1
>> sh-4.2$ oc whoami
>> system:serviceaccount:default:registry
>> sh-4.2$
>>
>> On 26 October 2017 at 20:54, Ben Parees  wrote:
>>
>>>
>>>
>>> On Thu, Oct 26, 2017 at 11:50 AM, Lionel Orellana 
>>> wrote:
>>>
 I didn't put it there.

 I another cluster this works.

 -bash-4.2$ oc rsh docker-registry-9-c9mgd oc whoami
 system:serviceaccount:default:registry

 -bash-4.2$ oc rsh docker-registry-9-c9mgd which oc
 /usr/bin/oc


>>> ok, it looks like it was removed on 3.7.
>>>
>>> Anyway you've certainly established there is a networking issue between
>>> your registry pod and the api server in your cluster
>>> (but oddly not between other pods an the api server)  Adding the
>>> networking team to the thread.
>>>
>>>
>>>
>>>

 On 26 October 2017 at 20:37, Ben Parees  wrote:

>
>
> On Thu, Oct 26, 2017 at 10:53 AM, Lionel Orellana 
> wrote:
>
>> Interestingly
>>
>> -bash-4.2$ oc rsh router-1-bf95x oc whoami
>> system:serviceaccount:default:router
>> -bash-4.2$ oc rsh docker-registry-1-9z8p2 oc whoami
>> Unable to connect to the server: Service Unavailable
>> command terminated with exit code 1
>>
>
> the registry image doesn't even contain an oc client binary (unless
> you put one there?) so i'm not sure what that is doing.
>
>
>
>>
>> On 26 October 2017 at 19:50, Lionel Orellana 
>> wrote:
>>
>>> Well this works from one of the hosts (using a token from oc whoami)
>>>
>>> curl -X GET -H "Authorization: Bearer $TOKEN"
>>> https://172.23.192.1/oapi/v1/users/~
>>>
>>> In the error msg
>>>
>>> msg="*invalid token*: Get https://172.23.192.1:443/oapi/v1/users/~
>>> : Service Unavailable"
>>>
>>> I wonder if the invalid toke part is the issue.
>>>
>>> On 26 October 2017 at 19:16, Ben Parees  wrote:
>>>


 On Thu, Oct 26, 2017 at 8:11 AM, Lionel Orellana <
 lione...@gmail.com> wrote:

> Hi,
>
> In a new OCP 3.6 installation I'm trying to deploy JBoss EAP 7.0
> from the catalog.
>
> This is in a project for which I am the admin.
>
> It's failing to push the image to the registry
>
> Pushing image 
> docker-registry.default.svc:5000/bimorl/jboss-eap70:latest
> ...
> Registry server Address:
> Registry server User Name: serviceaccount
> Registry server Email: serviceacco...@example.org
> Registry server Password: <>
> error: build error: Failed to push image: unauthorized:
> authentication required
>

> In the registry logs I see
>
> 172.23.140.1 - - [26/Oct/2017:05:08:19 +] "GET
> /openshift/token?account=serviceaccount=repository%3Ab
> imorl%2Fjboss-eap70%3Apush%2Cpull HTTP/1.1" 401 0 ""
> "docker/1.12.6 go/go1.8.3 kernel/3.10.0-693.2.2.el7.x86_64
> os/linux arch/amd64 UpstreamClient(go-dockerclient)"
> time="2017-10-26T05:08:19.116844289Z" level=debug msg="invalid
> token: Get https://172.23.192.1:443/oapi/v1/users/~: *Service
> Unavailable*" go.version=go1.7.6 
> http.request.host="docker-registry.default.svc:5000"
> http.request.id=467674a1-8618-4986-9e7f-b92a06afa43d
> http.request.method=GET http.request.remoteaddr="172.2
> 3.140.1:38284" http.request.uri="/openshift/t
> oken?account=serviceaccount=repository%3Abimorl%2Fjboss-eap70%3Apush%2Cpull"
> http.request.useragent="docker/1.12.6 go/go1.8.3
> kernel/3.10.0-693.2.2.el7.x86_64 os/linux arch/amd64
> UpstreamClient(go-dockerclient)" 

Re: OpenShift on AWS - Playbooks

[Tobias Brunner]

On 26.10.2017 15:23, Clayton Coleman wrote:
> The latter is still being actively developed - that will be the future
> direction but is not yet ready for genera use.  Our work towards
> leveraging node bootstrapping and using pre-baked AMIs is also not
> completely finalized, so no expectation of stability on the latter.

Thanks for the clarification! We'll have a deeper look at the
"playbooks/aws" stuff... Maybe we can help to bring it forward!



signature.asc
Description: OpenPGP digital signature
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: OpenShift on AWS - Playbooks

[Clayton Coleman]

The latter is still being actively developed - that will be the future
direction but is not yet ready for genera use.  Our work towards
leveraging node bootstrapping and using pre-baked AMIs is also not
completely finalized, so no expectation of stability on the latter.

> On Oct 26, 2017, at 9:18 AM, Tobias Brunner  wrote:
>
> Hi,
>
> There are at least two different "official" approaches to get OpenShift
> on AWS up and running:
>
> 1.
> https://github.com/openshift/openshift-ansible-contrib/tree/master/reference-architecture/aws-ansible
> 2. https://github.com/openshift/openshift-ansible/tree/master/playbooks/aws
>
> Which one of these two should we chose to get startet and have a
> maintained version? We're commited to contribute, but it's unclear which
> one we should use...
>
> Best,
> Tobias
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

OpenShift on AWS - Playbooks

[Tobias Brunner]

Hi,

There are at least two different "official" approaches to get OpenShift
on AWS up and running:

1.
https://github.com/openshift/openshift-ansible-contrib/tree/master/reference-architecture/aws-ansible
2. https://github.com/openshift/openshift-ansible/tree/master/playbooks/aws

Which one of these two should we chose to get startet and have a
maintained version? We're commited to contribute, but it's unclear which
one we should use...

Best,
Tobias



signature.asc
Description: OpenPGP digital signature
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: OCP: Failed to push image: unauthorized: authentication req, uired

[Ben Parees]

On Thu, Oct 26, 2017 at 12:43 PM, Lionel Orellana 
wrote:

> This works.Would have thought the api server address was added
> automatically to NO_PROXY?
>

it's supposed to be, but i do think there is a bug open where people have
seen it not be added:
https://bugzilla.redhat.com/show_bug.cgi?id=1504464



>
> -bash-4.2$ oc rsh docker-registry-1-9z8p2
> sh-4.2$ export NO_PROXY=$NO_PROXY,172.23.192.1
> sh-4.2$ oc whoami
> system:serviceaccount:default:registry
> sh-4.2$
>
> On 26 October 2017 at 20:54, Ben Parees  wrote:
>
>>
>>
>> On Thu, Oct 26, 2017 at 11:50 AM, Lionel Orellana 
>> wrote:
>>
>>> I didn't put it there.
>>>
>>> I another cluster this works.
>>>
>>> -bash-4.2$ oc rsh docker-registry-9-c9mgd oc whoami
>>> system:serviceaccount:default:registry
>>>
>>> -bash-4.2$ oc rsh docker-registry-9-c9mgd which oc
>>> /usr/bin/oc
>>>
>>>
>> ok, it looks like it was removed on 3.7.
>>
>> Anyway you've certainly established there is a networking issue between
>> your registry pod and the api server in your cluster
>> (but oddly not between other pods an the api server)  Adding the
>> networking team to the thread.
>>
>>
>>
>>
>>>
>>> On 26 October 2017 at 20:37, Ben Parees  wrote:
>>>


 On Thu, Oct 26, 2017 at 10:53 AM, Lionel Orellana 
 wrote:

> Interestingly
>
> -bash-4.2$ oc rsh router-1-bf95x oc whoami
> system:serviceaccount:default:router
> -bash-4.2$ oc rsh docker-registry-1-9z8p2 oc whoami
> Unable to connect to the server: Service Unavailable
> command terminated with exit code 1
>

 the registry image doesn't even contain an oc client binary (unless you
 put one there?) so i'm not sure what that is doing.



>
> On 26 October 2017 at 19:50, Lionel Orellana 
> wrote:
>
>> Well this works from one of the hosts (using a token from oc whoami)
>>
>> curl -X GET -H "Authorization: Bearer $TOKEN"
>> https://172.23.192.1/oapi/v1/users/~
>>
>> In the error msg
>>
>> msg="*invalid token*: Get https://172.23.192.1:443/oapi/v1/users/~
>> : Service Unavailable"
>>
>> I wonder if the invalid toke part is the issue.
>>
>> On 26 October 2017 at 19:16, Ben Parees  wrote:
>>
>>>
>>>
>>> On Thu, Oct 26, 2017 at 8:11 AM, Lionel Orellana >> > wrote:
>>>
 Hi,

 In a new OCP 3.6 installation I'm trying to deploy JBoss EAP 7.0
 from the catalog.

 This is in a project for which I am the admin.

 It's failing to push the image to the registry

 Pushing image 
 docker-registry.default.svc:5000/bimorl/jboss-eap70:latest
 ...
 Registry server Address:
 Registry server User Name: serviceaccount
 Registry server Email: serviceacco...@example.org
 Registry server Password: <>
 error: build error: Failed to push image: unauthorized:
 authentication required

>>>
 In the registry logs I see

 172.23.140.1 - - [26/Oct/2017:05:08:19 +] "GET
 /openshift/token?account=serviceaccount=repository%3Ab
 imorl%2Fjboss-eap70%3Apush%2Cpull HTTP/1.1" 401 0 ""
 "docker/1.12.6 go/go1.8.3 kernel/3.10.0-693.2.2.el7.x86_64
 os/linux arch/amd64 UpstreamClient(go-dockerclient)"
 time="2017-10-26T05:08:19.116844289Z" level=debug msg="invalid
 token: Get https://172.23.192.1:443/oapi/v1/users/~: *Service
 Unavailable*" go.version=go1.7.6 
 http.request.host="docker-registry.default.svc:5000"
 http.request.id=467674a1-8618-4986-9e7f-b92a06afa43d
 http.request.method=GET http.request.remoteaddr="172.23.140.1:38284"
 http.request.uri="/openshift/token?account=serviceaccount
 ope=repository%3Abimorl%2Fjboss-eap70%3Apush%2Cpull"
 http.request.useragent="docker/1.12.6 go/go1.8.3
 kernel/3.10.0-693.2.2.el7.x86_64 os/linux arch/amd64
 UpstreamClient(go-dockerclient)" 
 instance.id=e5e8a55e-c3bc-4dfa-a706-e844ddbbdf44
 openshift.logger=registry

>>>
>>> sounds like your registry is unable to reach your api server.  I
>>> would check if other pods running within your cluster are able to access
>>> the api server (ie run oc client commands from within a pod, against the
>>> kubernetes service ip)
>>>
>>>
>>>

 Any ideas?

 Thanks



 ___
 users mailing list
 users@lists.openshift.redhat.com
 http://lists.openshift.redhat.com/openshiftmm/listinfo/users


>>>
>>>
>>> --
>>> Ben Parees | 

Re: OCP: Failed to push image: unauthorized: authentication req, uired

[Lionel Orellana]

This works.Would have thought the api server address was added
automatically to NO_PROXY?

-bash-4.2$ oc rsh docker-registry-1-9z8p2
sh-4.2$ export NO_PROXY=$NO_PROXY,172.23.192.1
sh-4.2$ oc whoami
system:serviceaccount:default:registry
sh-4.2$

On 26 October 2017 at 20:54, Ben Parees  wrote:

>
>
> On Thu, Oct 26, 2017 at 11:50 AM, Lionel Orellana 
> wrote:
>
>> I didn't put it there.
>>
>> I another cluster this works.
>>
>> -bash-4.2$ oc rsh docker-registry-9-c9mgd oc whoami
>> system:serviceaccount:default:registry
>>
>> -bash-4.2$ oc rsh docker-registry-9-c9mgd which oc
>> /usr/bin/oc
>>
>>
> ok, it looks like it was removed on 3.7.
>
> Anyway you've certainly established there is a networking issue between
> your registry pod and the api server in your cluster
> (but oddly not between other pods an the api server)  Adding the
> networking team to the thread.
>
>
>
>
>>
>> On 26 October 2017 at 20:37, Ben Parees  wrote:
>>
>>>
>>>
>>> On Thu, Oct 26, 2017 at 10:53 AM, Lionel Orellana 
>>> wrote:
>>>
 Interestingly

 -bash-4.2$ oc rsh router-1-bf95x oc whoami
 system:serviceaccount:default:router
 -bash-4.2$ oc rsh docker-registry-1-9z8p2 oc whoami
 Unable to connect to the server: Service Unavailable
 command terminated with exit code 1

>>>
>>> the registry image doesn't even contain an oc client binary (unless you
>>> put one there?) so i'm not sure what that is doing.
>>>
>>>
>>>

 On 26 October 2017 at 19:50, Lionel Orellana 
 wrote:

> Well this works from one of the hosts (using a token from oc whoami)
>
> curl -X GET -H "Authorization: Bearer $TOKEN"
> https://172.23.192.1/oapi/v1/users/~
>
> In the error msg
>
> msg="*invalid token*: Get https://172.23.192.1:443/oapi/v1/users/~
> : Service Unavailable"
>
> I wonder if the invalid toke part is the issue.
>
> On 26 October 2017 at 19:16, Ben Parees  wrote:
>
>>
>>
>> On Thu, Oct 26, 2017 at 8:11 AM, Lionel Orellana 
>> wrote:
>>
>>> Hi,
>>>
>>> In a new OCP 3.6 installation I'm trying to deploy JBoss EAP 7.0
>>> from the catalog.
>>>
>>> This is in a project for which I am the admin.
>>>
>>> It's failing to push the image to the registry
>>>
>>> Pushing image docker-registry.default.svc:5000/bimorl/jboss-eap70:latest
>>> ...
>>> Registry server Address:
>>> Registry server User Name: serviceaccount
>>> Registry server Email: serviceacco...@example.org
>>> Registry server Password: <>
>>> error: build error: Failed to push image: unauthorized:
>>> authentication required
>>>
>>
>>> In the registry logs I see
>>>
>>> 172.23.140.1 - - [26/Oct/2017:05:08:19 +] "GET
>>> /openshift/token?account=serviceaccount=repository%3Ab
>>> imorl%2Fjboss-eap70%3Apush%2Cpull HTTP/1.1" 401 0 "" "docker/1.12.6
>>> go/go1.8.3 kernel/3.10.0-693.2.2.el7.x86_64 os/linux arch/amd64
>>> UpstreamClient(go-dockerclient)"
>>> time="2017-10-26T05:08:19.116844289Z" level=debug msg="invalid
>>> token: Get https://172.23.192.1:443/oapi/v1/users/~: *Service
>>> Unavailable*" go.version=go1.7.6 
>>> http.request.host="docker-registry.default.svc:5000"
>>> http.request.id=467674a1-8618-4986-9e7f-b92a06afa43d
>>> http.request.method=GET http.request.remoteaddr="172.23.140.1:38284"
>>> http.request.uri="/openshift/token?account=serviceaccount
>>> ope=repository%3Abimorl%2Fjboss-eap70%3Apush%2Cpull"
>>> http.request.useragent="docker/1.12.6 go/go1.8.3
>>> kernel/3.10.0-693.2.2.el7.x86_64 os/linux arch/amd64
>>> UpstreamClient(go-dockerclient)" 
>>> instance.id=e5e8a55e-c3bc-4dfa-a706-e844ddbbdf44
>>> openshift.logger=registry
>>>
>>
>> sounds like your registry is unable to reach your api server.  I
>> would check if other pods running within your cluster are able to access
>> the api server (ie run oc client commands from within a pod, against the
>> kubernetes service ip)
>>
>>
>>
>>>
>>> Any ideas?
>>>
>>> Thanks
>>>
>>>
>>>
>>> ___
>>> users mailing list
>>> users@lists.openshift.redhat.com
>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>>
>>>
>>
>>
>> --
>> Ben Parees | OpenShift
>>
>>
>

>>>
>>>
>>> --
>>> Ben Parees | OpenShift
>>>
>>>
>>
>
>
> --
> Ben Parees | OpenShift
>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: OCP: Failed to push image: unauthorized: authentication req, uired

[Ben Parees]

On Thu, Oct 26, 2017 at 11:50 AM, Lionel Orellana 
wrote:

> I didn't put it there.
>
> I another cluster this works.
>
> -bash-4.2$ oc rsh docker-registry-9-c9mgd oc whoami
> system:serviceaccount:default:registry
>
> -bash-4.2$ oc rsh docker-registry-9-c9mgd which oc
> /usr/bin/oc
>
>
ok, it looks like it was removed on 3.7.

Anyway you've certainly established there is a networking issue between
your registry pod and the api server in your cluster
(but oddly not between other pods an the api server)  Adding the networking
team to the thread.




>
> On 26 October 2017 at 20:37, Ben Parees  wrote:
>
>>
>>
>> On Thu, Oct 26, 2017 at 10:53 AM, Lionel Orellana 
>> wrote:
>>
>>> Interestingly
>>>
>>> -bash-4.2$ oc rsh router-1-bf95x oc whoami
>>> system:serviceaccount:default:router
>>> -bash-4.2$ oc rsh docker-registry-1-9z8p2 oc whoami
>>> Unable to connect to the server: Service Unavailable
>>> command terminated with exit code 1
>>>
>>
>> the registry image doesn't even contain an oc client binary (unless you
>> put one there?) so i'm not sure what that is doing.
>>
>>
>>
>>>
>>> On 26 October 2017 at 19:50, Lionel Orellana  wrote:
>>>
 Well this works from one of the hosts (using a token from oc whoami)

 curl -X GET -H "Authorization: Bearer $TOKEN"
 https://172.23.192.1/oapi/v1/users/~

 In the error msg

 msg="*invalid token*: Get https://172.23.192.1:443/oapi/v1/users/~
 : Service Unavailable"

 I wonder if the invalid toke part is the issue.

 On 26 October 2017 at 19:16, Ben Parees  wrote:

>
>
> On Thu, Oct 26, 2017 at 8:11 AM, Lionel Orellana 
> wrote:
>
>> Hi,
>>
>> In a new OCP 3.6 installation I'm trying to deploy JBoss EAP 7.0 from
>> the catalog.
>>
>> This is in a project for which I am the admin.
>>
>> It's failing to push the image to the registry
>>
>> Pushing image docker-registry.default.svc:5000/bimorl/jboss-eap70:latest
>> ...
>> Registry server Address:
>> Registry server User Name: serviceaccount
>> Registry server Email: serviceacco...@example.org
>> Registry server Password: <>
>> error: build error: Failed to push image: unauthorized:
>> authentication required
>>
>
>> In the registry logs I see
>>
>> 172.23.140.1 - - [26/Oct/2017:05:08:19 +] "GET
>> /openshift/token?account=serviceaccount=repository%3Ab
>> imorl%2Fjboss-eap70%3Apush%2Cpull HTTP/1.1" 401 0 "" "docker/1.12.6
>> go/go1.8.3 kernel/3.10.0-693.2.2.el7.x86_64 os/linux arch/amd64
>> UpstreamClient(go-dockerclient)"
>> time="2017-10-26T05:08:19.116844289Z" level=debug msg="invalid
>> token: Get https://172.23.192.1:443/oapi/v1/users/~: *Service
>> Unavailable*" go.version=go1.7.6 
>> http.request.host="docker-registry.default.svc:5000"
>> http.request.id=467674a1-8618-4986-9e7f-b92a06afa43d
>> http.request.method=GET http.request.remoteaddr="172.23.140.1:38284"
>> http.request.uri="/openshift/token?account=serviceaccount
>> ope=repository%3Abimorl%2Fjboss-eap70%3Apush%2Cpull"
>> http.request.useragent="docker/1.12.6 go/go1.8.3
>> kernel/3.10.0-693.2.2.el7.x86_64 os/linux arch/amd64
>> UpstreamClient(go-dockerclient)" 
>> instance.id=e5e8a55e-c3bc-4dfa-a706-e844ddbbdf44
>> openshift.logger=registry
>>
>
> sounds like your registry is unable to reach your api server.  I would
> check if other pods running within your cluster are able to access the api
> server (ie run oc client commands from within a pod, against the 
> kubernetes
> service ip)
>
>
>
>>
>> Any ideas?
>>
>> Thanks
>>
>>
>>
>> ___
>> users mailing list
>> users@lists.openshift.redhat.com
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>
>>
>
>
> --
> Ben Parees | OpenShift
>
>

>>>
>>
>>
>> --
>> Ben Parees | OpenShift
>>
>>
>


-- 
Ben Parees | OpenShift
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: OCP: Failed to push image: unauthorized: authentication req, uired

[Ben Parees]

On Thu, Oct 26, 2017 at 10:53 AM, Lionel Orellana 
wrote:

> Interestingly
>
> -bash-4.2$ oc rsh router-1-bf95x oc whoami
> system:serviceaccount:default:router
> -bash-4.2$ oc rsh docker-registry-1-9z8p2 oc whoami
> Unable to connect to the server: Service Unavailable
> command terminated with exit code 1
>

the registry image doesn't even contain an oc client binary (unless you put
one there?) so i'm not sure what that is doing.



>
> On 26 October 2017 at 19:50, Lionel Orellana  wrote:
>
>> Well this works from one of the hosts (using a token from oc whoami)
>>
>> curl -X GET -H "Authorization: Bearer $TOKEN"
>> https://172.23.192.1/oapi/v1/users/~
>>
>> In the error msg
>>
>> msg="*invalid token*: Get https://172.23.192.1:443/oapi/v1/users/~
>> : Service Unavailable"
>>
>> I wonder if the invalid toke part is the issue.
>>
>> On 26 October 2017 at 19:16, Ben Parees  wrote:
>>
>>>
>>>
>>> On Thu, Oct 26, 2017 at 8:11 AM, Lionel Orellana 
>>> wrote:
>>>
 Hi,

 In a new OCP 3.6 installation I'm trying to deploy JBoss EAP 7.0 from
 the catalog.

 This is in a project for which I am the admin.

 It's failing to push the image to the registry

 Pushing image docker-registry.default.svc:5000/bimorl/jboss-eap70:latest
 ...
 Registry server Address:
 Registry server User Name: serviceaccount
 Registry server Email: serviceacco...@example.org
 Registry server Password: <>
 error: build error: Failed to push image: unauthorized: authentication
 required

>>>
 In the registry logs I see

 172.23.140.1 - - [26/Oct/2017:05:08:19 +] "GET
 /openshift/token?account=serviceaccount=repository%3Ab
 imorl%2Fjboss-eap70%3Apush%2Cpull HTTP/1.1" 401 0 "" "docker/1.12.6
 go/go1.8.3 kernel/3.10.0-693.2.2.el7.x86_64 os/linux arch/amd64
 UpstreamClient(go-dockerclient)"
 time="2017-10-26T05:08:19.116844289Z" level=debug msg="invalid token:
 Get https://172.23.192.1:443/oapi/v1/users/~: *Service Unavailable*"
 go.version=go1.7.6 http.request.host="docker-registry.default.svc:5000"
 http.request.id=467674a1-8618-4986-9e7f-b92a06afa43d
 http.request.method=GET http.request.remoteaddr="172.23.140.1:38284"
 http.request.uri="/openshift/token?account=serviceaccount
 ope=repository%3Abimorl%2Fjboss-eap70%3Apush%2Cpull"
 http.request.useragent="docker/1.12.6 go/go1.8.3
 kernel/3.10.0-693.2.2.el7.x86_64 os/linux arch/amd64
 UpstreamClient(go-dockerclient)" 
 instance.id=e5e8a55e-c3bc-4dfa-a706-e844ddbbdf44
 openshift.logger=registry

>>>
>>> sounds like your registry is unable to reach your api server.  I would
>>> check if other pods running within your cluster are able to access the api
>>> server (ie run oc client commands from within a pod, against the kubernetes
>>> service ip)
>>>
>>>
>>>

 Any ideas?

 Thanks



 ___
 users mailing list
 users@lists.openshift.redhat.com
 http://lists.openshift.redhat.com/openshiftmm/listinfo/users


>>>
>>>
>>> --
>>> Ben Parees | OpenShift
>>>
>>>
>>
>


-- 
Ben Parees | OpenShift
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: OCP: Failed to push image: unauthorized: authentication req, uired

[Lionel Orellana]

Well this works from one of the hosts (using a token from oc whoami)

curl -X GET -H "Authorization: Bearer $TOKEN"
https://172.23.192.1/oapi/v1/users/~

In the error msg

msg="*invalid token*: Get https://172.23.192.1:443/oapi/v1/users/~
: Service Unavailable"

I wonder if the invalid toke part is the issue.

On 26 October 2017 at 19:16, Ben Parees  wrote:

>
>
> On Thu, Oct 26, 2017 at 8:11 AM, Lionel Orellana 
> wrote:
>
>> Hi,
>>
>> In a new OCP 3.6 installation I'm trying to deploy JBoss EAP 7.0 from the
>> catalog.
>>
>> This is in a project for which I am the admin.
>>
>> It's failing to push the image to the registry
>>
>> Pushing image docker-registry.default.svc:5000/bimorl/jboss-eap70:latest
>> ...
>> Registry server Address:
>> Registry server User Name: serviceaccount
>> Registry server Email: serviceacco...@example.org
>> Registry server Password: <>
>> error: build error: Failed to push image: unauthorized: authentication
>> required
>>
>
>> In the registry logs I see
>>
>> 172.23.140.1 - - [26/Oct/2017:05:08:19 +] "GET
>> /openshift/token?account=serviceaccount=repository%
>> 3Abimorl%2Fjboss-eap70%3Apush%2Cpull HTTP/1.1" 401 0 "" "docker/1.12.6
>> go/go1.8.3 kernel/3.10.0-693.2.2.el7.x86_64 os/linux arch/amd64
>> UpstreamClient(go-dockerclient)"
>> time="2017-10-26T05:08:19.116844289Z" level=debug msg="invalid token:
>> Get https://172.23.192.1:443/oapi/v1/users/~: *Service Unavailable*"
>> go.version=go1.7.6 http.request.host="docker-registry.default.svc:5000"
>> http.request.id=467674a1-8618-4986-9e7f-b92a06afa43d
>> http.request.method=GET http.request.remoteaddr="172.23.140.1:38284"
>> http.request.uri="/openshift/token?account=serviceaccount
>> ope=repository%3Abimorl%2Fjboss-eap70%3Apush%2Cpull"
>> http.request.useragent="docker/1.12.6 go/go1.8.3
>> kernel/3.10.0-693.2.2.el7.x86_64 os/linux arch/amd64
>> UpstreamClient(go-dockerclient)" 
>> instance.id=e5e8a55e-c3bc-4dfa-a706-e844ddbbdf44
>> openshift.logger=registry
>>
>
> sounds like your registry is unable to reach your api server.  I would
> check if other pods running within your cluster are able to access the api
> server (ie run oc client commands from within a pod, against the kubernetes
> service ip)
>
>
>
>>
>> Any ideas?
>>
>> Thanks
>>
>>
>>
>> ___
>> users mailing list
>> users@lists.openshift.redhat.com
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>
>>
>
>
> --
> Ben Parees | OpenShift
>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: OCP: Failed to push image: unauthorized: authentication req, uired

[Ben Parees]

On Thu, Oct 26, 2017 at 8:11 AM, Lionel Orellana  wrote:

> Hi,
>
> In a new OCP 3.6 installation I'm trying to deploy JBoss EAP 7.0 from the
> catalog.
>
> This is in a project for which I am the admin.
>
> It's failing to push the image to the registry
>
> Pushing image docker-registry.default.svc:5000/bimorl/jboss-eap70:latest
> ...
> Registry server Address:
> Registry server User Name: serviceaccount
> Registry server Email: serviceacco...@example.org
> Registry server Password: <>
> error: build error: Failed to push image: unauthorized: authentication
> required
>

> In the registry logs I see
>
> 172.23.140.1 - - [26/Oct/2017:05:08:19 +] "GET
> /openshift/token?account=serviceaccount=repository%3Abimorl%2Fjboss-eap70%3Apush%2Cpull
> HTTP/1.1" 401 0 "" "docker/1.12.6 go/go1.8.3 kernel/3.10.0-693.2.2.el7.x86_64
> os/linux arch/amd64 UpstreamClient(go-dockerclient)"
> time="2017-10-26T05:08:19.116844289Z" level=debug msg="invalid token: Get
> https://172.23.192.1:443/oapi/v1/users/~: *Service Unavailable*"
> go.version=go1.7.6 http.request.host="docker-registry.default.svc:5000"
> http.request.id=467674a1-8618-4986-9e7f-b92a06afa43d
> http.request.method=GET http.request.remoteaddr="172.23.140.1:38284"
> http.request.uri="/openshift/token?account=serviceaccount&
> scope=repository%3Abimorl%2Fjboss-eap70%3Apush%2Cpull"
> http.request.useragent="docker/1.12.6 go/go1.8.3
> kernel/3.10.0-693.2.2.el7.x86_64 os/linux arch/amd64 
> UpstreamClient(go-dockerclient)"
> instance.id=e5e8a55e-c3bc-4dfa-a706-e844ddbbdf44 openshift.logger=registry
>

sounds like your registry is unable to reach your api server.  I would
check if other pods running within your cluster are able to access the api
server (ie run oc client commands from within a pod, against the kubernetes
service ip)



>
> Any ideas?
>
> Thanks
>
>
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>


-- 
Ben Parees | OpenShift
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: oc cluster up - router not starting

[Jan Hellar]

Hi Cesar,

I stopped apache and now it works. Thanks a lot for help.

Best Regards,
Jan

On Wed, Oct 25, 2017 at 8:06 PM, Cesar Wong  wrote:

> Hi Jan,
>
> So I see this in your log:
>
> E1025 15:45:01.4085336242 pod_workers.go:182] Error syncing pod
> 6734f809-b99b-11e7-9b1d-3a4633f0fe38 ("router-1-fmvnv_default(
> 6734f809-b99b-11e7-9b1d-3a4633f0fe38)"), skipping: failed to
> "CreatePodSandbox" for 
> "router-1-fmvnv_default(6734f809-b99b-11e7-9b1d-3a4633f0fe38)"
> with CreatePodSandboxError: "CreatePodSandbox for pod
> \"router-1-fmvnv_default(6734f809-b99b-11e7-9b1d-3a4633f0fe38)\" failed:
> rpc error: code = 2 desc = failed to start sandbox container for pod
> \"router-1-fmvnv\": Error response from daemon: {\"message\":\"driver
> failed programming external connectivity on endpoint k8s_POD_router-1-fmvnv_
> default_6734f809-b99b-11e7-9b1d-3a4633f0fe38_23 (
> dc57db8d5856b460dd0b7ba84d320f5e24f46e4577e1d30288c28c086986237a): Error
> starting userland proxy: Bind for 0.0.0.0:80: unexpected error (Failure
> EADDRINUSE)\"}"
>
> Looks like either there is a pod or a process on your machine using port
> 80 and it's not letting the router bind to that port.
>



-- 
Jan Hellar
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: OCP: Failed to push image: unauthorized: authentication req, uired

[Lionel Orellana]

I've seen the issue
where
this error happens on the first build attempt. However I'm getting the
error on subsequent builds.

This is the first cluster I configure with the openshift-ovs-multitenant
plugin. Could that be interfering?

On 26 October 2017 at 17:11, Lionel Orellana  wrote:

> Hi,
>
> In a new OCP 3.6 installation I'm trying to deploy JBoss EAP 7.0 from the
> catalog.
>
> This is in a project for which I am the admin.
>
> It's failing to push the image to the registry
>
> Pushing image docker-registry.default.svc:5000/bimorl/jboss-eap70:latest
> ...
> Registry server Address:
> Registry server User Name: serviceaccount
> Registry server Email: serviceacco...@example.org
> Registry server Password: <>
> error: build error: Failed to push image: unauthorized: authentication
> required
>
> In the registry logs I see
>
> 172.23.140.1 - - [26/Oct/2017:05:08:19 +] "GET
> /openshift/token?account=serviceaccount=repository%3Abimorl%2Fjboss-eap70%3Apush%2Cpull
> HTTP/1.1" 401 0 "" "docker/1.12.6 go/go1.8.3 kernel/3.10.0-693.2.2.el7.x86_64
> os/linux arch/amd64 UpstreamClient(go-dockerclient)"
> time="2017-10-26T05:08:19.116844289Z" level=debug msg="invalid token: Get
> https://172.23.192.1:443/oapi/v1/users/~: *Service Unavailable*"
> go.version=go1.7.6 http.request.host="docker-registry.default.svc:5000"
> http.request.id=467674a1-8618-4986-9e7f-b92a06afa43d
> http.request.method=GET http.request.remoteaddr="172.23.140.1:38284"
> http.request.uri="/openshift/token?account=serviceaccount&
> scope=repository%3Abimorl%2Fjboss-eap70%3Apush%2Cpull"
> http.request.useragent="docker/1.12.6 go/go1.8.3
> kernel/3.10.0-693.2.2.el7.x86_64 os/linux arch/amd64 
> UpstreamClient(go-dockerclient)"
> instance.id=e5e8a55e-c3bc-4dfa-a706-e844ddbbdf44 openshift.logger=registry
>
> Any ideas?
>
> Thanks
>
>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

OCP: Failed to push image: unauthorized: authentication req,uired

[Lionel Orellana]

Hi,

In a new OCP 3.6 installation I'm trying to deploy JBoss EAP 7.0 from the
catalog.

This is in a project for which I am the admin.

It's failing to push the image to the registry

Pushing image docker-registry.default.svc:5000/bimorl/jboss-eap70:latest ...
Registry server Address:
Registry server User Name: serviceaccount
Registry server Email: serviceacco...@example.org
Registry server Password: <>
error: build error: Failed to push image: unauthorized: authentication
required

In the registry logs I see

172.23.140.1 - - [26/Oct/2017:05:08:19 +] "GET
/openshift/token?account=serviceaccount=repository%3Abimorl%2Fjboss-eap70%3Apush%2Cpull
HTTP/1.1" 401 0 "" "docker/1.12.6 go/go1.8.3
kernel/3.10.0-693.2.2.el7.x86_64 os/linux arch/amd64
UpstreamClient(go-dockerclient)"
time="2017-10-26T05:08:19.116844289Z" level=debug msg="invalid token: Get
https://172.23.192.1:443/oapi/v1/users/~: *Service Unavailable*"
go.version=go1.7.6 http.request.host="docker-registry.default.svc:5000"
http.request.id=467674a1-8618-4986-9e7f-b92a06afa43d
http.request.method=GET http.request.remoteaddr="172.23.140.1:38284"
http.request.uri="/openshift/token?account=serviceaccount=repository%3Abimorl%2Fjboss-eap70%3Apush%2Cpull"
http.request.useragent="docker/1.12.6 go/go1.8.3
kernel/3.10.0-693.2.2.el7.x86_64 os/linux arch/amd64
UpstreamClient(go-dockerclient)"
instance.id=e5e8a55e-c3bc-4dfa-a706-e844ddbbdf44
openshift.logger=registry

Any ideas?

Thanks
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users