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

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

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

On Mon, May 21, 2018 at 5:04 PM, 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

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

Find the name of one of your crashing pods and run: $ oc debug POD_NAME That'll put you into a copy of that pod at a shell and you can debug further from there. On Mon, May 21, 2018 at 5:04 PM, Brian Keyes wrote: > I have an very very simple hello python > > > #start

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

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

Re: Provisioning persistence for metrics with GlusterFS

Hi Dan! Now what I also don't understand is how did the initial volume group for > the registry got created with just 26GB of storage if the default is for > 100GB? Is there a rule such as: "create block-hosting volume of default > size=100GB or max available"? > The integrated registry's

Re: [logging]

On 05/20/2018 12:31 PM, Himmat Singh wrote: Hi Team, I am using openshift logging image  with below version for provides us centralize logging capability for our openshift cluster and external environment logs. |registry.access.redhat.com/openshift3/logging-fluentd:v3.9

Re: RPMs for 3.9 on Centos

OK, so do this on the nodes before running the ansible installer seems to do the trick: yum -y install centos-release-openshift-origin On 21/05/18 11:46, Joel Pearson wrote: You shouldn’t need testing. It looks like they’ve been in the repo for about a month. Not sure about the ansible

Re: Logging fails when using cinder volume for elasticsearch

On 21/05/18 13:30, Jeff Cantrill wrote: Consider logging and issue so that it is properly addressed by the development team. https://github.com/openshift/openshift-ansible/issues/8456 ___ users mailing list users@lists.openshift.redhat.com

Re: Logging fails when using cinder volume for elasticsearch

Consider logging and issue so that it is properly addressed by the development team. On Mon, May 21, 2018 at 7:05 AM, Tim Dudgeon wrote: > I'm seeing a strange problem with trying to use a Cinder volume for the > elasticsearch PVC when installing logging with Origin 3.7.

Logging fails when using cinder volume for elasticsearch

I'm seeing a  strange problem with trying to use a Cinder volume for the elasticsearch PVC when installing logging with Origin 3.7. If I use NFS or GlusterFS volumes it all works fine. If I try a Cinder volume elastic search fails to start because of permissions problems: [2018-05-21

Re: Provisioning persistence for metrics with GlusterFS

Hello Rodrigo, I appreciate your answer! In the meantime I had reached for the heketi-cli related support(chat) and I got the same reference. There's a config map generated by the installer for the heketi-registry pod that has the default for block-hosting volumes size set at 100GB. What I

Re: RPMs for 3.9 on Centos

You shouldn’t need testing. It looks like they’ve been in the repo for about a month. Not sure about the ansible side I haven’t actually tried to install 3.9 yet. And when I do I plan on using system containers. But you could grep through the ansible scripts looking for what installs to repo so

Re: RPMs for 3.9 on Centos

Seems like Ansible isn't doing so for me. Are there any special params needed for this? I did try setting these two, but to no effect: openshift_enable_origin_repo=true openshift_repos_enable_testing=true On 21/05/18 11:32, Joel Pearson wrote: They’re in the paas repo. You don’t have that

Re: RPMs for 3.9 on Centos

They’re in the paas repo. You don’t have that repo installed for some reason. Ansible is supposed to lay that down http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin/ Why don’t you use the system container version instead? Or you prefer rpms? On Mon, 21 May 2018 at 8:30 pm, Tim

RPMs for 3.9 on Centos

I looks like RPMs for Origin 3.9 are still not available from the Centos repos: $ yum search origin Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile  * base: ftp.lysator.liu.se  * extras: ftp.lysator.liu.se  * updates: ftp.lysator.liu.se