Rodrigo

I retried having replaced the node that failed and this time all 3 pods started correctly.

If this happens again (I suspect it will) I will report the outputs you mention.

Tim


On 16/04/18 14:06, Rodrigo Bersa wrote:
Hi Tim,

Looks like there's a problem to access the Node, or the device (/dev/vdb) on this Node.

Can you share the output of: oc logs of the failing glusterfs POD and the heketi POD?


Best regards,


Rodrigo Bersa

Cloud Consultant, RHCVA, RHCE

Red Hat Brasil <https://www.redhat.com>

rbe...@redhat.com <mailto:rbe...@redhat.com> M: +55-11-99557-5841 <tel:+55-11-99557-5841>

<https://red.ht/sig>      
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

Red Hat é reconhecida entre as melhores empresas para trabalhar no Brasil pelo *Great Place to Work*.

On Mon, Apr 16, 2018 at 8:07 AM, Tim Dudgeon <tdudgeon...@gmail.com <mailto:tdudgeon...@gmail.com>> wrote:

    I'm having problems deploying GlusterFS to an Origin cluster.

    I have 3 identical nodes for running glusterfs, but the deployment
    seems to randomly fail on one of the nodes sometimes. This is a
    typical error (with the json reformatted). Notice how node 001 and
    003 work fine, but 002 fails.
    All three nodes are equivalent in config.

    TASK [openshift_storage_glusterfs : Load heketi topology]
    
************************************************************************************************************************************
    Monday 16 April 2018  10:49:57 +0000 (0:00:01.414) 0:44:22.372
    **********

    {
      "changed": true,
      "cmd": [
        "oc",
    "--config=/tmp/openshift-glusterfs-ansible-Eb85yA/admin.kubeconfig",
        "rsh",
        "--namespace=glusterfs",
        "deploy-heketi-storage-1-5svjh",
        "heketi-cli",
        "-s",
        "http://localhost:8080";,
        "--user",
        "admin",
        "--secret",
        "JsSOzmoF6nP6nfuJJ1RQigRQNkUiD88xl8FLfu+xhpk=",
        "topology",
        "load",
    "--json=/tmp/openshift-glusterfs-ansible-Eb85yA/topology.json",
        "2>&1"
      ],
      "delta": "0:02:08.608619",
      "end": "2018-04-16 10:52:06.930155",
      "failed_when_result": true,
      "rc": 0,
      "start": "2018-04-16 10:49:58.321536",
      "stderr": "",
      "stderr_lines": [],
      "stdout": "Creating cluster ... ID:
    69b19096f118186c5a09f9e78f9cb9aa\n\tAllowing file volumes on
    cluster.\n\tAllowing block volumes on cluster.\n\tCreating node
    orn-gluster-storage-001.openstacklocal ... ID:
    ec9d615910d52bc5db9f4b18fdb714f3\n\t\tAdding device /dev/vdb ...
    OK\n\tCreating node orn-gluster-storage-002.openstacklocal ...
    Unable to create node: Unable to execute command on
    glusterfs-storage-gbzd8:\n\tCreating node
    orn-gluster-storage-003.openstacklocal ... ID:
    9e69ad050cdc41af61707319612e5f58\n\t\tAdding device /dev/vdb ... OK",
      "stdout_lines": [
        "Creating cluster ... ID: 69b19096f118186c5a09f9e78f9cb9aa",
        "\tAllowing file volumes on cluster.",
        "\tAllowing block volumes on cluster.",
        "\tCreating node orn-gluster-storage-001.openstacklocal ...
    ID: ec9d615910d52bc5db9f4b18fdb714f3",
        "\t\tAdding device /dev/vdb ... OK",
        "\tCreating node orn-gluster-storage-002.openstacklocal ...
    Unable to create node: Unable to execute command on
    glusterfs-storage-gbzd8:",
        "\tCreating node orn-gluster-storage-003.openstacklocal ...
    ID: 9e69ad050cdc41af61707319612e5f58",
        "\t\tAdding device /dev/vdb ... OK"
      ]
    }

    Any idea what's going wrong?

    Tim

    _______________________________________________
    users mailing list
    users@lists.openshift.redhat.com
    <mailto:users@lists.openshift.redhat.com>
    http://lists.openshift.redhat.com/openshiftmm/listinfo/users
    <http://lists.openshift.redhat.com/openshiftmm/listinfo/users>



_______________________________________________
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Reply via email to