Correctly handle absence of "eth0" for on-prem install
See original GitHub issueInstallation of Codenvy on-prem of version starting from 5.0.0-M1 fails if there is no “eth0” network interface on the machine. There is puppet error in time of installing like the follow:
2016-10-06 06:48:12 -0700 Puppet (err): Could not start Service[docker]: Execution of '/usr/bin/systemctl start docker' returned 1: Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details.
2016-10-06 06:48:12 -0700 /Stage[main]/Third_party::Docker::Service/Service[docker]/ensure (err): change from stopped to running failed: Could not start Service[docker]: Execution of '/usr/bin/systemctl start docker' returned 1: Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details.
2016-10-06 06:48:15 -0700 /Stage[main]/All_in_one::Service/Service[codenvy] (notice): Dependency Service[docker] has failures: true
2016-10-06 06:48:15 -0700 /Stage[main]/All_in_one::Service/Service[codenvy] (warning): Skipping because of failed dependencies
Workaround: check does “eth0” network interface present in the system at the “Checking system pre-requisites” stage in Codenvy bootstrap script. If “eth0” network interface doesn’t present in system, hold on installation and ask user to enter correct network interface name in aim to fix docker_cluster_advertise codenvy property to have this name:
Your system doesn’t have network interface “eth0”. Codenvy on-prem requires a name of network interface that docker daemon instances should use when advertising itself to the cluster. Please, enter the replacement of “eth0”: …
Customer Nokia encountered this error.
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (6 by maintainers)
Top GitHub Comments
Ah, I see okay - then what about this:
@dmytro-ndp Added http://codenvy.readme.io/v5.0/docs/installation#install