AWS openshift node hostnames changed unexpectedly when upgrading from 4.13 to 4.14.10

Solution Verified - Updated -

Issue

AWS node hostnames changed unexpectedly from IP-address.ec2.internal to IP-address.custom.internal when upgrading cluster from openshift container platform 4.13.24 to 4.14.10. The first two nodes being upgraded lost their AWS .ec2.internal hostnames and booted up with a customer specific hostname suffix instead.

Environment

  • Red Hat Openshift Container Platform (RHOCP) 4.14.10 on AWS.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content