Re: Simple yum update to version 1.4 and docker 1.9 destroyed system

2016-03-20 Thread Clayton Coleman 
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 - this is what I am asking) and after restarting of
origin-nodes and master and also restarting docker master web UI and
kubernetes seemed to work but old docker images won't start and also image
push failed wit i/o error.

Is this my fault somehow? Should I use different approach to upgrade my
systems? Is this caused by migration to docker 1.9.1 and Open Shift 1.1.4
at the same time?

Thanks for advices!
David Strejc
t: +420734270131
e: david.str...@gmail.com

___
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: Simple yum update to version 1.4 and docker 1.9 destroyed system

2016-03-20 Thread David Strejc 
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 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 docker cleanup
> > openshift/origin-docker-registry:v1.1.3 after docker cleanup
> >
> > I suppose I shold run some command for redeploying or upgrading to 1.1.4
> after upgrade of OS?
>
> These can be updated by using 'oc edit dc '
>
> >
> > but pods are
> >
> > openshift/origin-pod:v1.1.4 on master and also on nodes.
> >
> > Now when I've delted docker images and docker processes and restarting
> everything I got:
> >
> > Error: build error: timeout while waiting for remote repository "
> https://github.com/david-strejc/nginx.git;
>
> It sounds like there may be some network issues present.
>
> I would try the following:
> systemctl stop origin-node docker openvswitch
>
> systemctl start origin-node
>
> If that doesn't do the trick, I would suggest the network troubleshooting
> guide next.
>
> >
> > When I try to build from my dockerfile repo.
> >
> >
> > David Strejc
> > t: +420734270131
> > e: david.str...@gmail.com
> >
> > On Fri, Mar 18, 2016 at 2:05 PM, David Strejc 
> wrote:
> >>
> >> Image which won't start was my simplest Nginx from this repo:
> >>
> >> https://github.com/david-strejc/nginx/blob/master/Dockerfile
> >>
> >> Just openshift/centos7 with nginx and telnet and one html page. But I
> suppose this was because of docker upgrade.
> >>
> >> When I've rebuilded image Open Shift said that it cannot push image due
> to i/o timeout error.
> >>
> >>
> >> David Strejc
> >> t: +420734270131
> >> e: david.str...@gmail.com
> >>
> >> On Fri, Mar 18, 2016 at 1:59 PM, Clayton Coleman 
> wrote:
> >>>
> >>> 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 - this is what I am asking) and after
> restarting of origin-nodes and master and also restarting docker master web
> UI and kubernetes seemed to work but old docker images won't start and also
> image push failed wit i/o error.
> 
>  Is this my fault somehow? Should I use different approach to upgrade
> my systems? Is this caused by migration to docker 1.9.1 and Open Shift
> 1.1.4 at the same time?
> 
>  Thanks for advices!
>  David Strejc
>  t: +420734270131
>  e: david.str...@gmail.com
> 
>  ___
>  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
> >
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Simple yum update to version 1.4 and docker 1.9 destroyed system

2016-03-20 Thread David Strejc 
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 I shold run some command for redeploying or upgrading to 1.1.4
after upgrade of OS?

but pods are

openshift/origin-pod:v1.1.4 on master and also on nodes.

Now when I've delted docker images and docker processes and restarting
everything I got:

Error: build error: timeout while waiting for remote repository "
https://github.com/david-strejc/nginx.git;

When I try to build from my dockerfile repo.


David Strejc
t: +420734270131
e: david.str...@gmail.com

On Fri, Mar 18, 2016 at 2:05 PM, David Strejc 
wrote:

> Image which won't start was my simplest Nginx from this repo:
>
> https://github.com/david-strejc/nginx/blob/master/Dockerfile
>
> Just openshift/centos7 with nginx and telnet and one html page. But I
> suppose this was because of docker upgrade.
>
> When I've rebuilded image Open Shift said that it cannot push image due to
> i/o timeout error.
>
>
> David Strejc
> t: +420734270131
> e: david.str...@gmail.com
>
> On Fri, Mar 18, 2016 at 1:59 PM, Clayton Coleman 
> wrote:
>
>> 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 - this is what I am asking) and after restarting of
>> origin-nodes and master and also restarting docker master web UI and
>> kubernetes seemed to work but old docker images won't start and also image
>> push failed wit i/o error.
>>
>> Is this my fault somehow? Should I use different approach to upgrade my
>> systems? Is this caused by migration to docker 1.9.1 and Open Shift 1.1.4
>> at the same time?
>>
>> Thanks for advices!
>> David Strejc
>> t: +420734270131
>> e: david.str...@gmail.com
>>
>> ___
>> 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: Simple yum update to version 1.4 and docker 1.9 destroyed system

2016-03-19 Thread David Strejc 
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

But there was involved upgrade of docker from 1.8 to 1.9 (docker is running
fine).

I haven't found any upgrade info in release notes to 1.1.4



David Strejc
t: +420734270131
e: david.str...@gmail.com

On Fri, Mar 18, 2016 at 1:49 PM, Jason DeTiberus 
wrote:

>
> 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 kubernetes seemed to work but old docker images won't start and also
> image push failed wit i/o error.
> >
> > Is this my fault somehow? Should I use different approach to upgrade my
> systems? Is this caused by migration to docker 1.9.1 and Open Shift 1.1.4
> at the same time?
>
> You'll need to follow the upgrade section of the docs to complete the
> upgrade:
> https://docs.openshift.org/latest/install_config/upgrading/index.html
>
> >
> > Thanks for advices!
> > David Strejc
> > t: +420734270131
> > e: david.str...@gmail.com
> >
> > ___
> > 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: Simple yum update to version 1.4 and docker 1.9 destroyed system

2016-03-19 Thread Philippe Lafoucrière 
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).
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Simple yum update to version 1.4 and docker 1.9 destroyed system

2016-03-19 Thread Jason DeTiberus 
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 docker cleanup
> openshift/origin-docker-registry:v1.1.3 after docker cleanup
>
> I suppose I shold run some command for redeploying or upgrading to 1.1.4
after upgrade of OS?

These can be updated by using 'oc edit dc '

>
> but pods are
>
> openshift/origin-pod:v1.1.4 on master and also on nodes.
>
> Now when I've delted docker images and docker processes and restarting
everything I got:
>
> Error: build error: timeout while waiting for remote repository "
https://github.com/david-strejc/nginx.git;

It sounds like there may be some network issues present.

I would try the following:
systemctl stop origin-node docker openvswitch

systemctl start origin-node

If that doesn't do the trick, I would suggest the network troubleshooting
guide next.

>
> When I try to build from my dockerfile repo.
>
>
> David Strejc
> t: +420734270131
> e: david.str...@gmail.com
>
> On Fri, Mar 18, 2016 at 2:05 PM, David Strejc 
wrote:
>>
>> Image which won't start was my simplest Nginx from this repo:
>>
>> https://github.com/david-strejc/nginx/blob/master/Dockerfile
>>
>> Just openshift/centos7 with nginx and telnet and one html page. But I
suppose this was because of docker upgrade.
>>
>> When I've rebuilded image Open Shift said that it cannot push image due
to i/o timeout error.
>>
>>
>> David Strejc
>> t: +420734270131
>> e: david.str...@gmail.com
>>
>> On Fri, Mar 18, 2016 at 1:59 PM, Clayton Coleman 
wrote:
>>>
>>> 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 - this is what I am asking) and after
restarting of origin-nodes and master and also restarting docker master web
UI and kubernetes seemed to work but old docker images won't start and also
image push failed wit i/o error.

 Is this my fault somehow? Should I use different approach to upgrade
my systems? Is this caused by migration to docker 1.9.1 and Open Shift
1.1.4 at the same time?

 Thanks for advices!
 David Strejc
 t: +420734270131
 e: david.str...@gmail.com

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

Re: Simple yum update to version 1.4 and docker 1.9 destroyed system

2016-03-19 Thread Scott Dodson 
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
https://docs.openshift.org/latest/install_config/upgrading/manual_upgrades.html#upgrading-the-registry

We also offer playbooks that automate this if you used ansible to
install I'd suggest using those.
https://docs.openshift.org/latest/install_config/upgrading/automated_upgrades.html

--
Scott

On Fri, Mar 18, 2016 at 9:51 AM, David Strejc  wrote:
> 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 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 docker cleanup
>> > openshift/origin-docker-registry:v1.1.3 after docker cleanup
>> >
>> > I suppose I shold run some command for redeploying or upgrading to 1.1.4
>> > after upgrade of OS?
>>
>> These can be updated by using 'oc edit dc '
>>
>> >
>> > but pods are
>> >
>> > openshift/origin-pod:v1.1.4 on master and also on nodes.
>> >
>> > Now when I've delted docker images and docker processes and restarting
>> > everything I got:
>> >
>> > Error: build error: timeout while waiting for remote repository
>> > "https://github.com/david-strejc/nginx.git;
>>
>> It sounds like there may be some network issues present.
>>
>> I would try the following:
>> systemctl stop origin-node docker openvswitch
>>
>> systemctl start origin-node
>>
>> If that doesn't do the trick, I would suggest the network troubleshooting
>> guide next.
>>
>> >
>> > When I try to build from my dockerfile repo.
>> >
>> >
>> > David Strejc
>> > t: +420734270131
>> > e: david.str...@gmail.com
>> >
>> > On Fri, Mar 18, 2016 at 2:05 PM, David Strejc 
>> > wrote:
>> >>
>> >> Image which won't start was my simplest Nginx from this repo:
>> >>
>> >> https://github.com/david-strejc/nginx/blob/master/Dockerfile
>> >>
>> >> Just openshift/centos7 with nginx and telnet and one html page. But I
>> >> suppose this was because of docker upgrade.
>> >>
>> >> When I've rebuilded image Open Shift said that it cannot push image due
>> >> to i/o timeout error.
>> >>
>> >>
>> >> David Strejc
>> >> t: +420734270131
>> >> e: david.str...@gmail.com
>> >>
>> >> On Fri, Mar 18, 2016 at 1:59 PM, Clayton Coleman 
>> >> wrote:
>> >>>
>> >>> 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 - this is what I am asking) and after
>>  restarting of origin-nodes and master and also restarting docker master 
>>  web
>>  UI and kubernetes seemed to work but old docker images won't start and 
>>  also
>>  image push failed wit i/o error.
>> 
>>  Is this my fault somehow? Should I use different approach to upgrade
>>  my systems? Is this caused by migration to docker 1.9.1 and Open Shift 
>>  1.1.4
>>  at the same time?
>> 
>>  Thanks for advices!
>>  David Strejc
>>  t: +420734270131
>>  e: david.str...@gmail.com
>> 
>>  ___
>>  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
>> >
>
>
>
> ___
> 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: Simple yum update to version 1.4 and docker 1.9 destroyed system

2016-03-19 Thread Jason DeTiberus 
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
kubernetes seemed to work but old docker images won't start and also image
push failed wit i/o error.
>
> Is this my fault somehow? Should I use different approach to upgrade my
systems? Is this caused by migration to docker 1.9.1 and Open Shift 1.1.4
at the same time?

You'll need to follow the upgrade section of the docs to complete the
upgrade:
https://docs.openshift.org/latest/install_config/upgrading/index.html

>
> Thanks for advices!
> David Strejc
> t: +420734270131
> e: david.str...@gmail.com
>
> ___
> 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