[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

OKD 3.11 on atomicOS (7.1811 or 7.1812) - multipath installation failure



Hi all

 

We’re trying to setup an OKD 3.11 cluster (3x master, 2x nodes) but are failing on “deploy_cluster” playbook at step where multipath should be configured:

                

<master3.oslab.lxusp.local> (1, '\n{"msg": "Path /etc/multipath.conf does not exist !", "failed": true, "rc": 257, "invocation": {"module_args": {"directory_mode": null, "force": null, "remote_src": null, "m

arker": "# <!-- {mark} ANSIBLE MANAGED BLOCK - LIO iSCSI device -->", "path": "/etc/multipath.conf", "owner": "root", "follow": false, "marker_begin": "BEGIN", "group": "root", "insertbefore": null, "unsafe_

writes": null, "create": false, "state": "present", "content": null, "serole": null, "setype": null, "selevel": null, "regexp": null, "validate": null, "marker_end": "END", "src": null, "seuser": null, "deli

miter": null, "mode": 384, "insertafter": "devices {", "attributes": null, "backup": true, "block": "device {\\n          vendor \\"LIO-ORG\\"\\n          product \\"TCMU device\\"\\n          user_friendly_

names \\"yes\\"\\n          path_grouping_policy \\"failover\\"\\n          path_selector \\"round-robin 0\\"\\n          failback immediate\\n          path_checker \\"tur\\"\\n          prio \\"alua\\"\\n

         hardware_handler \\"1 alua\\"\\n          no_path_retry 120\\n          rr_weight \\"uniform\\"\\n}\\n"}}}\n', '')

fatal: [master3.oslab.lxusp.local]: FAILED! => {

    "changed": false,

    "invocation": {

        "module_args": {

            "attributes": null,

            "backup": true,

            "block": "device {\n          vendor \"LIO-ORG\"\n          product \"TCMU device\"\n          user_friendly_names \"yes\"\n          path_grouping_policy \"failover\"\n          path_selector \"

round-robin 0\"\n          failback immediate\n          path_checker \"tur\"\n          prio \"alua\"\n          hardware_handler \"1 alua\"\n          no_path_retry 120\n          rr_weight \"uniform\"\n}\n",

            "content": null,

            "create": false,

            "delimiter": null,

            "directory_mode": null,

            "follow": false,

            "force": null,

            "group": "root",

            "insertafter": "devices {",

            "insertbefore": null,

            "marker": "# <!-- {mark} ANSIBLE MANAGED BLOCK - LIO iSCSI device -->",

            "marker_begin": "BEGIN",

            "marker_end": "END",

            "mode": 384,

            "owner": "root",

            "path": "/etc/multipath.conf",

            "regexp": null,

            "remote_src": null,

            "selevel": null,

            "serole": null,

            "setype": null,

            "seuser": null,

            "src": null,

            "state": "present",

            "unsafe_writes": null,

            "validate": null

        }

    },

    "msg": "Path /etc/multipath.conf does not exist !",

    "rc": 257

}

        to retry, use: --limit @/root/openshift-ansible/playbooks/deploy_cluster.retry

 

we’ve checked the nodes and indeed there is an empty directory /etc/multipath after atomic OS installation (both 7.1811 or 7.1812 CentOS atomic host). does anyone else see this?

Installation takes place on virtual machines (vsphere 6.7) running on top of a Dell Poweredge Appliance (R610).

 

We’ve tried to remove the empty /etc/multipath directory prior to the “deploy_cluster” run on all nodes, but this does not change anything. Did we miss something, isn’t atomicOS based installation not supported anymore?

 

 

Thank you very much for any hints!

 

Bes regards,

 

Rolf

 

Attachment: smime.p7s
Description: S/MIME cryptographic signature


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]