OpenShift traffic control (openshift-tc) service not starting at boot

Solution Verified - Updated -

Issue

My OpenShift nodes have network bonding configured and I customized EXTERNAL_ETH_DEV in /etc/openshift/node.conf accordingly.

I also enabled traffic control for OpenShift gears (TRAFFIC_CONTROL_ENABLED=true).

When I book my nodes the openshift-tc service fails to start, and I see this in boot.log:

...
/opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-node-1.23.9.21/lib/openshift-origin-node/utils/tc.rb:107:in `get_interface_mtu': Unable to determine external network interface IP address. (RuntimeError)
        from /opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-node-1.23.9.21/lib/openshift-origin-node/utils/tc.rb:80:in `initialize'
        from /usr/sbin/oo-admin-ctl-tc:28:in `new'
        from /usr/sbin/oo-admin-ctl-tc:28:in `<main>'
iptables: Applying firewall rules: [  OK  ]
...

Environment

OpenShift Enterprise 2.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.