Re: Ruby-ex deployment times out

[Gerard Braad]

On Fri, Sep 30, 2016 at 1:16 AM, Seth Jennings  wrote:
> You can go to koji and downgrade to an old version (this is the one I used):
> http://koji.fedoraproject.org/koji/buildinfo?buildID=796377

Currently on C7, and waiting for a fix instead

> I've opened a bug to track this:
> https://bugzilla.redhat.com/show_bug.cgi?id=1380474

Will follow-up and watch this issue...


Slightly off-topic
I have noticed that Docker in general on F24 has not been as stable to
this version.
I run:

   Git commit:  8b7fa4a/1.10.3

Experienced several crashes on issuing an `oc` command that brought
down docker and the OpenShift test cluster.
This happened on two instances of F24 with this Docker version.

-- 

   Gerard Braad | http://gbraad.nl
   [ Doing Open Source Matters ]

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

how can I force rolling deployment without any change in deployment config

[Ravi Kapoor]

I created a deployment config and it is working fine.
However I made a few changes in a file mounted using persistent volume.
Somehow the changed file is not being loaded and old file is being used.

I found that to load the modified file, I need to do a new deployment.
I also found that unless I change somethign in my deploymentconfig.yaml,
the rollign deployment is not triggered.
So my temporary solution was to change the file name on disk and reflect
the same in deplymentconfig and trigger use "oc replace -f
deploymentConfig.xml".

While this solves the problem, renaming the file on every deployment is way
too risky

I tried inserting a pseudo element in YAML file as "buildnumber: 1",
however changing this parameter does trigger the deployment either.

Is there a way for me to force reload the file from persistent volume or
force deployment without renaming the file?
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Secrets not available anymore with 1.3.0

[Philippe Lafoucrière]

Any news on this?
This is really a blocking issue to upgrade to 1.3.0 for us.
​
Thanks
Philippe
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Can't push images after 1.3.0 upgrade

[Philippe Lafoucrière]

We're using :443/namespace/imagestream
We had to rollback to previous snapshots, we never managed to get it
working :(
​
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users