question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Correctly handle absence of "eth0" for on-prem install

See original GitHub issue

Installation 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:closed
  • Created 7 years ago
  • Comments:7 (6 by maintainers)

github_iconTop GitHub Comments

1reaction
bmickleacommented, Oct 7, 2016

Ah, I see okay - then what about this:

The Codenvy master node needs to advertise itself on a network interface. By default we use “eth0” but can’t find that interface on this machine. Please enable “eth0” and hit enter (leaving the name blank) or enter the name of an available network interface:

Read more comments on GitHub >

github_iconTop Results From Across the Web

Updating node network configuration | OpenShift Virtualization
Create an interface on nodes in the cluster by applying a NodeNetworkConfigurationPolicy manifest to the cluster. The manifest details the requested ...
Read more >
VeloCloud Operator Guide - VMware SD-WAN 3.3
This section describes installation. Cloud-init Preparation. This section describes how to use the cloud-init package to handle the early initialization of.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found