Which old docker images won't start, and what error do they have? What
errors in the registry logs for the push error?
On Mar 18, 2016, at 8:40 AM, David Strejc wrote:
I've updated my testing system just with yum update (I don't know if this
is recommended approach -
I've already rebooted machines and everything seems to be allright now.
I will edit dc for those two deployments.
Thanks.
David Strejc
t: +420734270131
e: david.str...@gmail.com
On Fri, Mar 18, 2016 at 2:50 PM, Jason DeTiberus
wrote:
>
> On Mar 18, 2016 9:29 AM, "David
I've removed docker images from my machines and restarted openshift-master
and node processes
On master (which is also node) where is HA-Proxy located I still got:
openshift/origin-haproxy-router:v1.1.3 after docker cleanup
openshift/origin-docker-registry:v1.1.3 after docker cleanup
I suppose
Quote:
Unless noted otherwise, node and masters within a major version are forward
and backward compatible, so upgrading your cluster should go smoothly.
However, you should not run mismatched versions longer than necessary to
upgrade the entire cluster.
I've just upgraded from 1.1.3 to 1.1.4
And ​make sure Swap is still disabled after reboot.
We learned, the hard way, that it wasn't persistent (due to a bad fstab
config) over reboot.
With swap enabled, the performance of some services was very bad (2500ms
response time vs less than 200ms in normal conditions).
On Mar 18, 2016 9:29 AM, "David Strejc" wrote:
>
> I've removed docker images from my machines and restarted
openshift-master and node processes
>
> On master (which is also node) where is HA-Proxy located I still got:
>
> openshift/origin-haproxy-router:v1.1.3 after
You'll definitely need to follow the upgrade documentation, in
particular upgrading those two components are here but you should give
the whole doc a read through.
https://docs.openshift.org/latest/install_config/upgrading/manual_upgrades.html#upgrading-the-router
On Mar 18, 2016 8:40 AM, "David Strejc" wrote:
>
> I've updated my testing system just with yum update (I don't know if this
is recommended approach - this is what I am asking) and after restarting of
origin-nodes and master and also restarting docker master web UI and