OpenShift gear move fails with bonded network interface

Solution Verified - Updated -

Issue

My OpenShift Enterprise nodes have bonded network interfaces.

When I try to move a gear I get an error, e.g.:

URL: http://abc.com
Login: xyz
App UUID: 54b7d8588552571d240003de
Gear UUID: 54b7d8588552571d240003de
DEBUG: Source district uuid: 546b4dac8552577c77000001
DEBUG: Destination district uuid: 546b4dac8552577c77000001
DEBUG: Getting existing app 'abc' status before moving
DEBUG: Gear component 'jbosseap-6.3' was running
DEBUG: Stopping existing app cartridge 'jbosseap-6.3' before moving
DEBUG: Stopping existing app cartridge 'haproxy-1.5' before moving
DEBUG: Force stopping existing app before moving
DEBUG: Gear platform is 'linux'
DEBUG: Creating new account for gear 'abc' on gbrdsr10479
DEBUG: Moving content for app 'abc', gear 'abc' to node2
Identity added: /etc/openshift/rsync_id_rsa (/etc/openshift/rsync_id_rsa)
ssh: Could not resolve hostname : Name or service not known

Environment

  • OpenShift Enterprise (OSE) 2 prior to 2.2.5
  • Networking on the nodes uses an interface other than eth0

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.