How and why should the hosts in an OpenShift Enterprise deployment be kept synchronized with the same errata release version (e.g. 2.1.5)?

Solution In Progress - Updated -

Issue

In an existing OpenShift Enterprise deployment, a host (node or broker) must be added, but the existing hosts have not been updated against the latest errata. The new host has been installed with the lasted content available from the OpenShift repositories. Will this be an issue? How can new hosts be added matching the exact version that is already installed on the existing hosts?

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