FQDN issue after Puppet configuration on OpenShift nodes

Solution Verified - Updated -

Issue

  • facter -p command returns the wrong FQDN for puppetmaster.
  • The cluster nodes when configured as puppet-agents are trying to reach out to the Puppet master with a wrong FQDN during the server startup.

Environment

  • Red Hat OpenShift Container Platform [RHOCP]
    • v3.11

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