Bug 978261 - Hardcoded references to eth0 in oo-accept-node
Summary: Hardcoded references to eth0 in oo-accept-node
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: Containers
Version: 2.x
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Rob Millner
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-26 08:27 UTC by Brenton Leanhardt
Modified: 2015-05-14 23:12 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-22 15:13:00 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Brenton Leanhardt 2013-06-26 08:27:10 UTC
Description of problem:
If a Node does not have eth0 oo-accept-node will display a confusing error message.  The offending code line is:

$TC_DATA = %x[/sbin/tc clas show dev eth0].split("\n").grep(/parent/)

However, there are more instance of eth0 in that file that need to be replaced.

Version-Release number of selected component (if applicable):
openshift-origin-node-util-1.10.4-1

Comment 1 Rob Millner 2013-06-27 22:27:24 UTC
The node.conf file is used, baring that the ethernet device is probed for by finding what device either routes from or routes to the public IP address.

https://github.com/openshift/origin-server/pull/2957

Comment 2 openshift-github-bot 2013-06-27 22:50:23 UTC
Commit pushed to master at https://github.com/openshift/origin-server

https://github.com/openshift/origin-server/commit/fa5184e8a1c458c8331657d14dc57eabe6fc16f1
Bug 978261 - find the external ethernet device rather than hard-code eth0

Comment 3 Meng Bo 2013-06-28 12:46:11 UTC
Check this on devenv_3427,

Modify the EXTERNAL_ETH_DEV to non-exist one in node.conf
Use oo-accept-node to check the issue.

# oo-accept-node -v
INFO: loading node configuration file /etc/openshift/node.conf
INFO: loading resource limit file /etc/openshift/resource_limits.conf
INFO: finding external network device
Device "ethi10" does not exist.
FAIL: SEVERE: not a valid ethernet device: 'ethi10'
Cannot find device "ethi10"
INFO: checking node public hostname resolution

It will detect the nic dynamically, but not the hardcode one.


Note You need to log in before you can comment on or make changes to this bug.