On 24.09.19 11:13, Johan Schelling wrote:
> Goodmorning all,
> 
> I have been playing around for a while now with Openshift Origin  on our 
> LinuxONE system following the great “Getting_Started_with_OpenShift_v3.10”  
> guide….
> When using zVM as a hypervisor I can deploy an Openshift cluster with 
> multiple nodes with no problems at all (using zVM 6.4 and Clefos 7.5).  
> Everything works like a charm….
> 
> But when I try to deploy an Openshift cluster with one or multiple nodes 
> using KVM (using Ubuntu 16.04 KVM and Clefos 7.5) I run into problems 
> starting the docker daemon.
> Somehow the docker daemon freezes after which I have to cancel the ansible 
> playbook……   Starting the docker daemon by hand (systemctl start docker),  
> the same thing happens:


Can you say exactly what distro version run as host and what distro version 
runs as guest (the good and the bad variants)
This was not 100% clear.

> 
> ● docker.service - Docker Application Container Engine
>    Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor 
> preset: disabled)
>    Active: activating (start) since di 2019-09-24 11:00:01 CEST; 8min ago
>      Docs: http://docs.docker.com
>  Main PID: 27563 (dockerd-current)
>    CGroup: /system.slice/docker.service
>            └─27563 /usr/bin/dockerd-current --add-runtime 
> docker-runc=/usr/libexec/docker/docker-runc-current 
> --default-runtime=docker-runc --exec-...
> 
> sep 24 11:00:01 lnxicu20 systemd[1]: Starting Docker Application Container 
> Engine...

any chance to attach gdb to that hanging process and doing a "thread apply all 
bt"?
> The service will remain in status “activating (start)”  until I kill the 
> service.  No messages (other than “starting Docker Application Container 
> Engine”) the logs.  Every docker command that you try to give (e.g. docker 
> version
> 
> Anyone seen this behaviour before or any ideas on what is going wrong?
> 
> I have a couple of other linux guests (both Ubuntu and SLES) running Docker 
> in both zVM and KVM environment without any problems….

So that means that you have other guests under KVM where docker starts up just 
fine. 

> 
> Some additional information:   yum list installed | grep docker
> 
> cockpit-docker.s390x            176-4.el7.centos           @extras
> docker.s390x                    2:1.13.1-96.gitb2f74b2.el7.centos
> docker-client.s390x             2:1.13.1-96.gitb2f74b2.el7.centos
> docker-common.s390x             2:1.13.1-96.gitb2f74b2.el7.centos
> origin-docker-excluder.noarch   3.11.0-1.el7.git.0.62803d0 
> @centos-openshift-origin
> python-docker-py.noarch         1:1.10.6-9.el7_6           @extras
> python-docker-pycreds.noarch    1:0.3.0-9.el7_6            @extras

Or asked differently, is it just the clefos guest that does not work?
> 
> Same situation on linux guests running in zVM and KVM, but only on zVM the 
> docker service will start.
> 
> On the zVM guest the “docker version” command returns:
> 
> Client:
>  Version:         1.13.1
>  API version:     1.26
>  Package version: docker-1.13.1-96.gitb2f74b2.el7.centos.s390x
>  Go version:      go1.10.3
>  Git commit:      b2f74b2/1.13.1
>  Built:           Thu Jun 20 12:57:27 2019
>  OS/Arch:         linux/s390x
> 
> Server:
>  Version:         1.13.1
>  API version:     1.26 (minimum version 1.12)
>  Package version: docker-1.13.1-96.gitb2f74b2.el7.centos.s390x
>  Go version:      go1.10.3
>  Git commit:      b2f74b2/1.13.1
>  Built:           Thu Jun 20 12:57:27 2019
>  OS/Arch:         linux/s390x
>  Experimental:    false
> 
> Running the same “docker version”  on the guest in the KVM environment 
> results in a freeze …..
> 
> On an Ubuntu guest running in KVM an “apt list —installed | grep docker” 
> returns:
> 
> docker/xenial,now 1.5-1 s390x [installed]
> docker.io/xenial-updates,xenial-security,now 18.09.7-0ubuntu1~16.04.5 s390x 
> [installed]
> 
> and the “docker version” command shows:
> 
> Client:
>  Version:           18.09.7
>  API version:       1.39
>  Go version:        go1.10.4
>  Git commit:        2d0083d
>  Built:             Fri Aug 16 14:19:34 2019
>  OS/Arch:           linux/s390x
>  Experimental:      false
> 
> Server:
>  Engine:
>   Version:          18.09.7
>   API version:      1.39 (minimum version 1.12)
>   Go version:       go1.10.4
>   Git commit:       2d0083d
>   Built:            Thu Aug 15 15:12:41 2019
>   OS/Arch:          linux/s390x
>   Experimental:     false
> 
> The Ubuntu environment on KVM has been running perfectly OK for quite some 
> time now …..
> 
> Sorry for the long post, but this is driving me nuts…..
> 
> Regards
> Johan Schelling
> Infrastructure Solution Architect
> 
> 
> [cid:[email protected]]
> 
> 
> 
> ICU IT Services BV
> Transistorstraat 55b  I  1322 CK  ALMERE
> 
> M 06 – 21 245 992  I  E 
> [email protected]<mailto:[email protected]>
> T 088 – 5 234 123  I  www.icu-it.nl<http://www.icu-it.nl/>  I  KvK 32135776
> ICU Proclaimer<http://www.icu-it.nl/proclaimer/>
> 
> 
> 
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO LINUX-390 or visit
> http://www2.marist.edu/htbin/wlvindex?LINUX-390
> 

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to