[Container-tools] CDK doesn't come up (again)

[Praveen Kumar]

On Tue, Aug 16, 2016 at 11:56 AM, Michael Melsen
<michael.melsen at itris.nl> wrote:
> hi everyone,

Hi Michael,

>
> I've been working with CDK 2.1 for a few weeks now using Vagrant, VirtualBox
> and the RHEL image that Redhat provides. Every now and then (5x times
> already) when issuing Vagrant up the Openshift script failes to run on the
> RHEL. The journal states (using journalctl -u openshift.service) that no
> journal files are found.
>
> If I enter RHEL using vagrant ssh and issue a status on openshift.service,
> this is the output:
>
> Loaded: loaded (/usr/lib/systemd/system/openshift.service; enabled; vendor
> preset: disabled) Active: activating (auto-restart) (Result: exit-code)
> since ma 2016-08-15 05:39:20 EDT; 17s ago Docs: https://docs.openshift.org/
> Process: 4865 ExecStop=/usr/bin/sh -c /opt/adb/openshift/openshift_stop
> (code=exited, status=0/SUCCESS) Process: 4546 ExecStartPost=/usr/bin/sh
> /opt/adb/openshift/openshift_provision (code=exited, status=0/SUCCESS)
> Process: 4545 ExecStart=/usr/bin/sh /opt/adb/openshift/openshift
> (code=exited, status=1/FAILURE) Process: 4539 ExecStartPre=/usr/bin/docker
> rm openshift (code=exited, status=0/SUCCESS) Process: 4534
> ExecStartPre=/usr/bin/docker stop openshift (code=exited, status=0/SUCCESS)
> Main PID: 4545 (code=exited, status=1/FAILURE)
>
> I also see issuing a docker ps that no containers are running. There has
> been a container running but is stopped after a few seconds. the log of this
> registry container shows:
>
> [vagrant at rhel-cdk ~]$ docker logs 2 W0815 05:52:24.302304 7428
> start_master.go:270] assetConfig.loggingPublicURL: Invalid value: "":
> required to view aggregated container logs in the console W0815
> 05:52:24.305200 7428 start_master.go:270] assetConfig.metricsPublicURL:
> Invalid value: "": required to view cluster metrics in the console I0815
> 05:52:24.804504 7428 plugins.go:71] No cloud provider specified. I0815
> 05:52:24.902068 7428 genericapiserver.go:81] Adding storage destination for
> group I0815 05:52:24.902124 7428 genericapiserver.go:81] Adding storage
> destination for group extensions I0815 05:52:24.902152 7428
> start_master.go:383] Starting master on 0.0.0.0:8443 (v3.2.0.44) I0815
> 05:52:24.902158 7428 start_master.go:384] Public master address is
> https://10.1.2.2:8443 I0815 05:52:24.902171 7428 start_master.go:388] Using
> images from "openshift3/ose-<component>:v3.2.0.44"
>
> I can't get Openshift to run anymore, so the only way to go for me is now
> reinstall RHEL. Hope you can help me out

Can you check available resource on your host machine and which
provider you had this issue?  We tried to reproduce it to our internal
setup (libvirt provider) and openshift started as expected. Also
before you do `vagrant up` again try to destroy the VM using `vagrant
destroy -f && rm -fr .vagrant`. Please put logs to pastebin[0] and
share that link (which makes easy to read).

[0] https://paste.fedoraproject.org/




-- 
Praveen Kumar
http://fedoraproject.org/wiki/User:Kumarpraveen
http://fedoraproject.org/
http://kumar-pravin.blogspot.com