Gluster config.yml playbook fails with "New Node doesn't have glusterd running"

Solution In Progress - Updated -

Issue

  • Attempting to run openshift-glusterfs/config.yml is failing:
[heketi] ERROR 2020/01/08 18:54:42 heketi/apps/glusterfs/app_node.go:107:glusterfs.(*App).NodeAdd: ssh: handshake failed: ssh: unable to authenticate, attempted methods [publickey none], no supported methods remain
[heketi] ERROR 2020/01/08 18:54:42 heketi/apps/glusterfs/app_node.go:108:glusterfs.(*App).NodeAdd: New Node doesn't have glusterd running
  • Even with heketi.json sshexec configured correctly as documented in this KCS, SSH is not passing the correct SSH credential and is resulting in a failure:
./jin.heketi.sh topology load --json=/tmp/openshift-glusterfs-ansible-aWfp6r/topology.json
Creating cluster ... ID: 3d818bf26ec6f701bfdf63e2179f5abe
Allowing file volumes on cluster.
Allowing block volumes on cluster.
Creating node server.example.com ... Unable to create node: New Node doesn't have glusterd running
Creating node server.example.com . ... Unable to create node: New Node doesn't have glusterd running
Creating node server.example.com . ... Unable to create node: New Node doesn't have glusterd running

Environment

  • OpenShift Container Platform
    • 3.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

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content