OpenShift Baremetal Deployment Fails Adding Keys

Solution Verified - Updated -

Issue

When using Advanced Cluster Management for Kubernetes to deploy a baremetal OpenShift cluster the deployment may fail because the private key defined in the baremetal provider connection cannot be added to the ssh-agent.

Environment

  • Red Hat Advanced Cluster Management for Kubernetes 2.2
  • Red Hat Advanced Cluster Management for Kubernetes 2.3

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