Re: Image pull error when using the integrated registry

[Ben Parees]

this looks like your main error:

level=error msg="OpenShift access denied: User
\"system:serviceaccount:slimmelden-dev:builder\"
cannot get imagestreams/layers.image.openshift.io in project \"generic\""

looks like you're trying to reference images in one project, from a build
in a different project.  So you'll need to grant permissions to the builder
SA to access the images in question.  You can grant the
system:image-pullers role.

oc policy add-role-to-user system:image-pullers
system:serviceaccount:slimmelden-dev:builder
-n generic

should do it.


On Tue, May 22, 2018 at 6:49 PM, Dan Pungă  wrote:

> I've caught another error like this one and one of the docker-registry
> pods gives some errors about authorization.
> I've tried adding, inside the web-interface for the docker-registry, the
> system:serviceaccount:slimmelde-dev:builder user to have pull access in
> the generic project.
>
> The docs that I've found/read about the integrated registry only describe
> direct access/manual to the registry: https://docs.openshift.org/
> latest/install_config/registry/accessing_registry.html
> Any other place to look, for my type of usage?
>
> Thank you!
>
> Logs below:
>
> time="2018-05-22T22:05:55.649683785Z" level=error msg="error authorizing
> context: authorization header required" go.version=go1.9.2
> http.request.host="docker-registry.default.svc:5000" http.request.id
> =3528f4c9-f729-4bcc-abf4-ef5a271399ff http.request.method=GET
> http.request.remoteaddr="10.128.2.1:42438" http.request.uri=/v2/
> http.request.useragent="docker/1.13.1 go/go1.8.3
> kernel/3.10.0-862.2.3.el7.x86_64 os/linux arch/amd64 
> UpstreamClient(go-dockerclient)"
> instance.id=be8746aa-b85c-40fb-978f-040a25b6c1d1
>
> time="2018-05-22T22:05:55.720645637Z" level=error msg="OpenShift access
> denied: User \"system:serviceaccount:slimmelden-dev:builder\" cannot get
> imagestreams/layers.image.openshift.io in project \"generic\""
> go.version=go1.9.2 http.request.host="docker-registry.default.svc:5000"
> http.request.id=8f5bacf4-7d34-448a-8f9b-12cb65499f5b
> http.request.method=GET http.request.remoteaddr="10.128.2.1:42442"
> http.request.uri="/v2/generic/ot-builder-npm-is/manifests/sha256:
> 9efdf954ec62e662e67d3f1c71f9d46faf9c82c76f8513338c2a4b19b6f318b5"
> http.request.useragent="docker/1.13.1 go/go1.8.3
> kernel/3.10.0-862.2.3.el7.x86_64 os/linux arch/amd64 
> UpstreamClient(go-dockerclient)"
> instance.id=be8746aa-b85c-40fb-978f-040a25b6c1d1
> openshift.auth.user="system:serviceaccount:slimmelden-dev:builder"
> vars.name=generic/ot-builder-npm-is vars.reference="sha256:
> 9efdf954ec62e662e67d3f1c71f9d46faf9c82c76f8513338c2a4b19b6f318b5"
>
> time="2018-05-22T22:05:55.720783744Z" level=error msg="error authorizing
> context: access denied" go.version=go1.9.2 
> http.request.host="docker-registry.default.svc:5000"
> http.request.id=8f5bacf4-7d34-448a-8f9b-12cb65499f5b
> http.request.method=GET http.request.remoteaddr="10.128.2.1:42442"
> http.request.uri="/v2/generic/ot-builder-npm-is/manifests/sha256:
> 9efdf954ec62e662e67d3f1c71f9d46faf9c82c76f8513338c2a4b19b6f318b5"
> http.request.useragent="docker/1.13.1 go/go1.8.3
> kernel/3.10.0-862.2.3.el7.x86_64 os/linux arch/amd64 
> UpstreamClient(go-dockerclient)"
> instance.id=be8746aa-b85c-40fb-978f-040a25b6c1d1 vars.name
> =generic/ot-builder-npm-is vars.reference="sha256:
> 9efdf954ec62e662e67d3f1c71f9d46faf9c82c76f8513338c2a4b19b6f318b5"
>
> time="2018-05-22T22:05:55.924000499Z" level=error msg="error authorizing
> context: authorization header required" go.version=go1.9.2
> http.request.host="docker-registry.default.svc:5000" http.request.id
> =5ac69bd6-f5f1-40cc-8f20-7bd3ed5dfb98 http.request.method=GET
> http.request.remoteaddr="10.128.2.1:42444" http.request.uri=/v2/
> http.request.useragent="docker/1.13.1 go/go1.8.3
> kernel/3.10.0-862.2.3.el7.x86_64 os/linux arch/amd64 
> UpstreamClient(go-dockerclient)"
> instance.id=be8746aa-b85c-40fb-978f-040a25b6c1d1
>
> time="2018-05-22T22:05:55.997011922Z" level=error msg="OpenShift access
> denied: User \"system:serviceaccount:slimmelden-dev:builder\" cannot get
> imagestreams/layers.image.openshift.io in project \"generic\""
> go.version=go1.9.2 http.request.host="docker-registry.default.svc:5000"
> http.request.id=a5327070-a760-441f-98b3-704cf181692c
> http.request.method=GET http.request.remoteaddr="10.128.2.1:42448"
> http.request.uri="/v2/generic/ot-builder-npm-is/manifests/sha256:
> 9efdf954ec62e662e67d3f1c71f9d46faf9c82c76f8513338c2a4b19b6f318b5"
> http.request.useragent="docker/1.13.1 go/go1.8.3
> kernel/3.10.0-862.2.3.el7.x86_64 os/linux arch/amd64 
> UpstreamClient(go-dockerclient)"
> instance.id=be8746aa-b85c-40fb-978f-040a25b6c1d1
> openshift.auth.user="system:serviceaccount:slimmelden-dev:builder"
> vars.name=generic/ot-builder-npm-is vars.reference="sha256:
> 9efdf954ec62e662e67d3f1c71f9d46faf9c82c76f8513338c2a4b19b6f318b5"
>
> time="2018-05-22T22:05:55.997142473Z" level=error msg="error authorizing
> 

Re: Image pull error when using the integrated registry

[Dan Pungă]

I've caught another error like this one and one of the docker-registry 
pods gives some errors about authorization.
I've tried adding, inside the web-interface for the docker-registry, the 
system:serviceaccount:slimmelde-dev:builder user to have pull access in 
the generic project.


The docs that I've found/read about the integrated registry only 
describe direct access/manual to the registry: 
https://docs.openshift.org/latest/install_config/registry/accessing_registry.html

Any other place to look, for my type of usage?

Thank you!

Logs below:

time="2018-05-22T22:05:55.649683785Z" level=error msg="error authorizing 
context: authorization header required" go.version=go1.9.2 
http.request.host="docker-registry.default.svc:5000" 
http.request.id=3528f4c9-f729-4bcc-abf4-ef5a271399ff 
http.request.method=GET http.request.remoteaddr="10.128.2.1:42438" 
http.request.uri=/v2/ http.request.useragent="docker/1.13.1 go/go1.8.3 
kernel/3.10.0-862.2.3.el7.x86_64 os/linux arch/amd64 
UpstreamClient(go-dockerclient)" 
instance.id=be8746aa-b85c-40fb-978f-040a25b6c1d1


time="2018-05-22T22:05:55.720645637Z" level=error msg="OpenShift access 
denied: User \"system:serviceaccount:slimmelden-dev:builder\" cannot get 
imagestreams/layers.image.openshift.io in project \"generic\"" 
go.version=go1.9.2 http.request.host="docker-registry.default.svc:5000" 
http.request.id=8f5bacf4-7d34-448a-8f9b-12cb65499f5b 
http.request.method=GET http.request.remoteaddr="10.128.2.1:42442" 
http.request.uri="/v2/generic/ot-builder-npm-is/manifests/sha256:9efdf954ec62e662e67d3f1c71f9d46faf9c82c76f8513338c2a4b19b6f318b5" 
http.request.useragent="docker/1.13.1 go/go1.8.3 
kernel/3.10.0-862.2.3.el7.x86_64 os/linux arch/amd64 
UpstreamClient(go-dockerclient)" 
instance.id=be8746aa-b85c-40fb-978f-040a25b6c1d1 
openshift.auth.user="system:serviceaccount:slimmelden-dev:builder" 
vars.name=generic/ot-builder-npm-is 
vars.reference="sha256:9efdf954ec62e662e67d3f1c71f9d46faf9c82c76f8513338c2a4b19b6f318b5" 



time="2018-05-22T22:05:55.720783744Z" level=error msg="error authorizing 
context: access denied" go.version=go1.9.2 
http.request.host="docker-registry.default.svc:5000" 
http.request.id=8f5bacf4-7d34-448a-8f9b-12cb65499f5b 
http.request.method=GET http.request.remoteaddr="10.128.2.1:42442" 
http.request.uri="/v2/generic/ot-builder-npm-is/manifests/sha256:9efdf954ec62e662e67d3f1c71f9d46faf9c82c76f8513338c2a4b19b6f318b5" 
http.request.useragent="docker/1.13.1 go/go1.8.3 
kernel/3.10.0-862.2.3.el7.x86_64 os/linux arch/amd64 
UpstreamClient(go-dockerclient)" 
instance.id=be8746aa-b85c-40fb-978f-040a25b6c1d1 
vars.name=generic/ot-builder-npm-is 
vars.reference="sha256:9efdf954ec62e662e67d3f1c71f9d46faf9c82c76f8513338c2a4b19b6f318b5" 



time="2018-05-22T22:05:55.924000499Z" level=error msg="error authorizing 
context: authorization header required" go.version=go1.9.2 
http.request.host="docker-registry.default.svc:5000" 
http.request.id=5ac69bd6-f5f1-40cc-8f20-7bd3ed5dfb98 
http.request.method=GET http.request.remoteaddr="10.128.2.1:42444" 
http.request.uri=/v2/ http.request.useragent="docker/1.13.1 go/go1.8.3 
kernel/3.10.0-862.2.3.el7.x86_64 os/linux arch/amd64 
UpstreamClient(go-dockerclient)" 
instance.id=be8746aa-b85c-40fb-978f-040a25b6c1d1


time="2018-05-22T22:05:55.997011922Z" level=error msg="OpenShift access 
denied: User \"system:serviceaccount:slimmelden-dev:builder\" cannot get 
imagestreams/layers.image.openshift.io in project \"generic\"" 
go.version=go1.9.2 http.request.host="docker-registry.default.svc:5000" 
http.request.id=a5327070-a760-441f-98b3-704cf181692c 
http.request.method=GET http.request.remoteaddr="10.128.2.1:42448" 
http.request.uri="/v2/generic/ot-builder-npm-is/manifests/sha256:9efdf954ec62e662e67d3f1c71f9d46faf9c82c76f8513338c2a4b19b6f318b5" 
http.request.useragent="docker/1.13.1 go/go1.8.3 
kernel/3.10.0-862.2.3.el7.x86_64 os/linux arch/amd64 
UpstreamClient(go-dockerclient)" 
instance.id=be8746aa-b85c-40fb-978f-040a25b6c1d1 
openshift.auth.user="system:serviceaccount:slimmelden-dev:builder" 
vars.name=generic/ot-builder-npm-is 
vars.reference="sha256:9efdf954ec62e662e67d3f1c71f9d46faf9c82c76f8513338c2a4b19b6f318b5" 



time="2018-05-22T22:05:55.997142473Z" level=error msg="error authorizing 
context: access denied" go.version=go1.9.2 
http.request.host="docker-registry.default.svc:5000" 
http.request.id=a5327070-a760-441f-98b3-704cf181692c 
http.request.method=GET http.request.remoteaddr="10.128.2.1:42448" 
http.request.uri="/v2/generic/ot-builder-npm-is/manifests/sha256:9efdf954ec62e662e67d3f1c71f9d46faf9c82c76f8513338c2a4b19b6f318b5" 
http.request.useragent="docker/1.13.1 go/go1.8.3 
kernel/3.10.0-862.2.3.el7.x86_64 os/linux arch/amd64 
UpstreamClient(go-dockerclient)" 
instance.id=be8746aa-b85c-40fb-978f-040a25b6c1d1 
vars.name=generic/ot-builder-npm-is 
vars.reference="sha256:9efdf954ec62e662e67d3f1c71f9d46faf9c82c76f8513338c2a4b19b6f318b5"







On 22.05.2018 19:49, Ben Parees wrote:



On Tue, May 22, 

Re: suggestion for a long running python container for a demo

[Graham Dumpleton]

Hello world type application:

* https://github.com/OpenShiftDemos/os-sample-python 


More involved application which can optionally be hooked up to database etc.

* https://github.com/openshift-katacoda/blog-django-py 


The latter example is what is used in the freely downlable eBook on OpenShift:

* https://www.openshift.com/deploying-to-openshift/ 


as well as in the OpenShift interactive learning environment for some of the 
scenarios describing OpenShift fundamentals.

* https://learn.openshift.com/ 

Would highly recommend you check out these later resources if you haven't done 
so already.

Graham

> On 23 May 2018, at 4:01 am, Brian Keyes  wrote:
> 
> I am looking for a long running non exiting example for python , maybe to 
> ping a pubilc ip or something , just some thing to keep the container/POD 
> alive
> 
> thanks 
> 
> -- 
> Brian Keyes
> Systems Engineer, Vizuri
> 703-855-9074(Mobile)
> 703-464-7030 x8239 (Office)
> 
> FOR OFFICIAL USE ONLY: This email and any attachments may contain information 
> that is privacy and business sensitive.  Inappropriate or unauthorized 
> disclosure of business and privacy sensitive information may result in civil 
> and/or criminal penalties as detailed in as amended Privacy Act of 1974 and 
> DoD 5400.11-R.
> 
> ___
> 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: [EXTERNAL] Re: Upgrade bug from 3.6 to 3.7

[Gary Franczyk]

Ah, I was upgrading OpenShift enterprise, which apparently is still at 3.7.46.

Thanks




Gary Franczyk
Unix Administrator, Expert, Infrastructure

Availity | 10752 Deerwood Park Blvd S. Ste 110, Jacksonville FL 32256
W 904.470.4953 | M 561.313.2866
gary.franc...@availity.com
From: Scott Dodson 
Date: Tuesday, May 22, 2018 at 2:42 PM
To: Gary Franczyk 
Cc: "users@lists.openshift.redhat.com" 
Subject: [EXTERNAL] Re: Upgrade bug from 3.6 to 3.7

WARNING: This email originated outside of the Availity email system.
DO NOT CLICK links or open attachments unless you recognize the sender and know 
the content is safe.

This was fixed recently, can you confirm it's fixed? It should be in 
openshift-ansible-3.7.48-1 or the latest release-3.7 branch of a github 
checkout.

https://github.com/openshift/openshift-ansible/pull/8311
https://bugzilla.redhat.com/show_bug.cgi?id=1573827

On Tue, May 22, 2018 at 12:44 PM, Gary Franczyk 
> wrote:
I’ve discovered what I believe is a bug when upgrading from 3.6 to 3.7.

There is a file that creates the components for the API Aggregator in the 
install scripts that does not get called during separate control-plane and node 
upgrades.

The file is:
/usr/share/ansible/openshift-ansible/playbooks/common/openshift-master/tasks/wire_aggregator.yml

It does not get called in the upgrade_control_plane.yml or the 
upgrade_nodes.yml playbooks, but is called in the upgrade.yml file.   In 
addition, the only time it is run is when there are hosts listed in the 
“oo_masters_to_config”, which is only before they are upgraded.  This means 
that if you try to run the upgrade.yml afterward, it does not apply these 
changes.

Perhaps I this list can notify someone that can correct this.

Gary Franczyk
Unix Administrator, Expert, Infrastructure

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
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: error Reason: DeploymentConfig "tueday204pm" is invalid: spec.template.spec.restartPolicy: Unsupported value: "OnFailure": supported values: Always

[Jordan Liggitt]

deployment configs spawn replication controllers, which maintain running
pods and only allow restart policies of "Always"

On Tue, May 22, 2018 at 2:58 PM, Brian Keyes  wrote:

> I am attempting to change this deployment config and getting this error ,
> why cant I set this to restart never or on failure ?
>
> why is Always the only option here ?
>
> Reason: DeploymentConfig "tueday204pm" is invalid: 
> spec.template.spec.restartPolicy:
> Unsupported value: "OnFailure": supported values: Always
>
>
> thanks 
>
>
> .
>
>
>
> ___
> 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

error Reason: DeploymentConfig "tueday204pm" is invalid: spec.template.spec.restartPolicy: Unsupported value: "OnFailure": supported values: Always

[Brian Keyes]

I am attempting to change this deployment config and getting this error ,
why cant I set this to restart never or on failure ?

why is Always the only option here ?

Reason: DeploymentConfig "tueday204pm" is invalid:
spec.template.spec.restartPolicy: Unsupported value: "OnFailure": supported
values: Always


thanks 


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

Re: suggestion for a long running python container for a demo

[Tim Dudgeon]

Why python? Why not bash (or even sh).
Once the pod/container is running you can rsh to it and do what ever you 
want.

Even execute python.

So, more basically how best to start a minimal centos|debian|whatever 
container so that it stays running so that you can rsh to it and then be 
inside the pod and debug things.



On 22/05/18 19:01, Brian Keyes wrote:
I am looking for a long running non exiting example for python , maybe 
to ping a pubilc ip or something , just some thing to keep the 
container/POD alive


thanks 

--
Brian Keyes
Systems Engineer, Vizuri
703-855-9074(Mobile)
703-464-7030 x8239 (Office)

FOR OFFICIAL USE ONLY: This email and any attachments may contain 
information that is privacy and business sensitive. Inappropriate or 
unauthorized disclosure of business and privacy sensitive information 
may result in civil and/or criminal penalties as detailed in as 
amended Privacy Act of 1974 and DoD 5400.11-R.




___
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: Upgrade bug from 3.6 to 3.7

[Scott Dodson]

This was fixed recently, can you confirm it's fixed? It should be in
openshift-ansible-3.7.48-1 or the latest release-3.7 branch of a github
checkout.

https://github.com/openshift/openshift-ansible/pull/8311
https://bugzilla.redhat.com/show_bug.cgi?id=1573827

On Tue, May 22, 2018 at 12:44 PM, Gary Franczyk 
wrote:

> I’ve discovered what I believe is a bug when upgrading from 3.6 to 3.7.
>
>
>
> There is a file that creates the components for the API Aggregator in the
> install scripts that does not get called during separate control-plane and
> node upgrades.
>
>
>
> The file is:
>
> /usr/share/ansible/openshift-ansible/playbooks/common/
> openshift-master/tasks/wire_aggregator.yml
>
>
>
> It does not get called in the upgrade_control_plane.yml or the
> upgrade_nodes.yml playbooks, but is called in the upgrade.yml file.   In
> addition, the only time it is run is when there are hosts listed in the
> “oo_masters_to_config”, which is only before they are upgraded.  This means
> that if you try to run the upgrade.yml afterward, it does not apply these
> changes.
>
>
>
> Perhaps I this list can notify someone that can correct this.
>
>
>
> *Gary Franczyk*
>
> Unix Administrator, Expert, Infrastructure
> --
> 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
> 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: suggestion for a long running python container for a demo

[Dave Neary]

Hi Brian,

How about this simple "web server in Python" example?
https://gist.github.com/bradmontgomery/2219997

Or this one: https://www.acmesystems.it/python_http

Thanks,
Dave.


On 05/22/2018 02:01 PM, Brian Keyes wrote:
> I am looking for a long running non exiting example for python , maybe
> to ping a pubilc ip or something , just some thing to keep the
> container/POD alive
> 
> thanks 
> 
> -- 
> Brian Keyes
> Systems Engineer, Vizuri
> 703-855-9074(Mobile)
> 703-464-7030 x8239 (Office)
> 
> FOR OFFICIAL USE ONLY: This email and any attachments may contain
> information that is privacy and business sensitive.  Inappropriate or
> unauthorized disclosure of business and privacy sensitive information
> may result in civil and/or criminal penalties as detailed in as amended
> Privacy Act of 1974 and DoD 5400.11-R.
> 
> 
> 
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
> 

-- 
Dave Neary - Open Source and Standards team
Red Hat - http://community.redhat.com
Ph: +1-978-399-2182 / Cell: +1-978-799-3338

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

suggestion for a long running python container for a demo

[Brian Keyes]

I am looking for a long running non exiting example for python , maybe to
ping a pubilc ip or something , just some thing to keep the container/POD
alive

thanks 

-- 
Brian Keyes
Systems Engineer, Vizuri
703-855-9074(Mobile)
703-464-7030 x8239 (Office)

FOR OFFICIAL USE ONLY: This email and any attachments may contain
information that is privacy and business sensitive.  Inappropriate or
unauthorized disclosure of business and privacy sensitive information may
result in civil and/or criminal penalties as detailed in as amended Privacy
Act of 1974 and DoD 5400.11-R.
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: simple hello world in python keeps crashing how to see why?

[Brian Keyes]

thanks so much , I would be LOST with out the help I am getting here

the oc debug POD_NAME was great but the  oc logs -p podname really told me
what is going on

I am attempting to get just a python example that is long running and
persistent

thanks again ALL!

On Mon, May 21, 2018 at 5:17 PM, Graham Dumpleton 
wrote:

> If that is really your whole application then as soon as the loop
> completes, the container will exit and the pod restarted. If that happens
> quick enough and keeps happening it would go into a fail state. For a
> normal deployment, you need to have an application, such as a WSGI
> application running on a WSGI server, which runs permanently. You wouldn't
> use a normal deployment for a short lived program that exits straight away.
>
> What is it that you are ultimately wanting to do?
>
> Graham
>
> On 22 May 2018, at 7:04 am, Brian Keyes  wrote:
>
> I have an very very simple hello python
>
>
> #start loop
> for x in range(0, 30):
> print ("hello python ")
>
> but every time I run this on openshift it keeps crashing , why , would it
> be best to scale this up so it is on all worker nodes let it crash and ssh
> into the worker node and look at the docker logs ?
>
> it has 2gb of ram allocated so I am not thinking that this is a memory
> issue
>
> any advice ?
> --
> thanks 
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>
>


-- 
Brian Keyes
Systems Engineer, Vizuri
703-855-9074(Mobile)
703-464-7030 x8239 (Office)

FOR OFFICIAL USE ONLY: This email and any attachments may contain
information that is privacy and business sensitive.  Inappropriate or
unauthorized disclosure of business and privacy sensitive information may
result in civil and/or criminal penalties as detailed in as amended Privacy
Act of 1974 and DoD 5400.11-R.
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: How could I re configure "openshift_master_cluster_public_hostname" after cluster setup?

[Aleksandar Lazic]

On 22/05/2018 10:12, Yu Wei wrote:

Hi,
I installed openshift origin cluster withe following variables set.
openshift_master_cluster_public_hostname
openshift_master_cluster_hostname

Then I want to reconfigure above variables to use different values.

Is it possible? If so, how could I do that?


Yes just rerun byo/config.yml


Thanks,

Jared, (韦煜）
Software developer
Interested in open source software, big data, Linux



___
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: Image pull error when using the integrated registry

[Ben Parees]

On Tue, May 22, 2018 at 11:46 AM, Dan Pungă  wrote:

> Hello all!
>
> I'm experiencing a problem when trying to pull an image from Openshift's
> container registry.
> I've recently installed OpenshiftOrigin 3.9 with docker-registry deployed.
>
> I'm using 2 projects, one where "generic" images are built and one for
> "applications". When running a build in the "application" project that is
> based on an image from the "generic" project, the build process fails at
> times with errors such:
>
> Pulling image docker-registry.default.svc:5000/generic/ot-builder-maven-
> is@sha256:ff3a7e558a44adc6212bd86dc3c0799537afd47f05be5678b0b986f7c7e3398c
> ...
> Checking for Docker config file for PULL_DOCKERCFG_PATH in path
> /var/run/secrets/openshift.io/pull
> Using Docker config file /var/run/secrets/openshift.io/pull/.dockercfg
> Step 1/11 : FROM docker-registry.default.svc:
> 5000/generic/ot-builder-maven-is@sha256:ff3a7e558a44adc6212bd86dc3c079
> 9537afd47f05be5678b0b986f7c7e3398c
> Trying to pull repository docker-registry.default.svc:
> 5000/generic/ot-builder-maven-is ...
> error: build error: unauthorized: authentication required
>
> The imagestream is there and the sha is the right one. This seems to
> happen at random and it goes away if I pause between build triesso
> random.
>

it might be enlightening to look at the logs from the registry pod(or pods
if you're running multiple replica instances) to see if it's getting errors
talking to the api server.

I haven't done some through tests to see if it's the same behaviour for
> source imageStreams inside the same project...
> Any idea what to try?
>
> Not sure if this is related, but I was trying to login to the registry and
> trying to this from outside the cluster, I get
> Error response from daemon: Get https://docker-registry-
> default..:5000/v2/: net/http: request canceled while waiting for
> connection (Client.Timeout exceeded while awaiting headers)
> This looks like timeout config/networking issues and I wonder if it's what
> causing the initial problem(even though the registry storage node, the
> registry pod and the application node where the build is executed are
> inside the same subnet).
>
>
> ___
> 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

Upgrade bug from 3.6 to 3.7

[Gary Franczyk]

I’ve discovered what I believe is a bug when upgrading from 3.6 to 3.7.

There is a file that creates the components for the API Aggregator in the 
install scripts that does not get called during separate control-plane and node 
upgrades.

The file is:
/usr/share/ansible/openshift-ansible/playbooks/common/openshift-master/tasks/wire_aggregator.yml

It does not get called in the upgrade_control_plane.yml or the 
upgrade_nodes.yml playbooks, but is called in the upgrade.yml file.   In 
addition, the only time it is run is when there are hosts listed in the 
“oo_masters_to_config”, which is only before they are upgraded.  This means 
that if you try to run the upgrade.yml afterward, it does not apply these 
changes.

Perhaps I this list can notify someone that can correct this.

Gary Franczyk
Unix Administrator, Expert, Infrastructure

--
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
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Image pull error when using the integrated registry

[Dan Pungă]

Hello all!

I'm experiencing a problem when trying to pull an image from Openshift's 
container registry.

I've recently installed OpenshiftOrigin 3.9 with docker-registry deployed.

I'm using 2 projects, one where "generic" images are built and one for 
"applications". When running a build in the "application" project that 
is based on an image from the "generic" project, the build process fails 
at times with errors such:


Pulling image 
docker-registry.default.svc:5000/generic/ot-builder-maven-is@sha256:ff3a7e558a44adc6212bd86dc3c0799537afd47f05be5678b0b986f7c7e3398c 
...
Checking for Docker config file for PULL_DOCKERCFG_PATH in path 
/var/run/secrets/openshift.io/pull

Using Docker config file /var/run/secrets/openshift.io/pull/.dockercfg
Step 1/11 : FROM 
docker-registry.default.svc:5000/generic/ot-builder-maven-is@sha256:ff3a7e558a44adc6212bd86dc3c0799537afd47f05be5678b0b986f7c7e3398c
Trying to pull repository 
docker-registry.default.svc:5000/generic/ot-builder-maven-is ...

error: build error: unauthorized: authentication required

The imagestream is there and the sha is the right one. This seems to 
happen at random and it goes away if I pause between build triesso 
random.
I haven't done some through tests to see if it's the same behaviour for 
source imageStreams inside the same project...

Any idea what to try?

Not sure if this is related, but I was trying to login to the registry 
and trying to this from outside the cluster, I get
Error response from daemon: Get 
https://docker-registry-default..:5000/v2/: net/http: request 
canceled while waiting for connection (Client.Timeout exceeded while 
awaiting headers)
This looks like timeout config/networking issues and I wonder if it's 
what causing the initial problem(even though the registry storage node, 
the registry pod and the application node where the build is executed 
are inside the same subnet).


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

How could I re configure "openshift_master_cluster_public_hostname" after cluster setup?

[Yu Wei]

Hi,
I installed openshift origin cluster withe following variables set.
openshift_master_cluster_public_hostname
openshift_master_cluster_hostname

Then I want to reconfigure above variables to use different values.

Is it possible? If so, how could I do that?


Thanks,

Jared, (韦煜）
Software developer
Interested in open source software, big data, Linux
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users