Re: Image pull error when using the integrated registry

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

Re: Image pull error when using the integrated registry

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

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

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

Re: [EXTERNAL] Re: Upgrade bug from 3.6 to 3.7

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

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

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

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

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

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

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

Re: Upgrade bug from 3.6 to 3.7

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,

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

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

suggestion for a long running python container for a demo

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

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

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,

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

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?

Re: Image pull error when using the integrated registry

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

Upgrade bug from 3.6 to 3.7

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:

Image pull error when using the integrated registry

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

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

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