When deploying rdo-ocata on rhel 7.3, overcloud deployment fails

[David Hill]

When deploying rdo-ocata on rhel 7.3, overcloud deployment fails because the iptables firewall is denying everything and the pacemaker cluster isn't forming properly.

[David Hill (david-hill-ubisoft)]

[root@overcloud-controller-0 cluster]# traceroute overcloud-controller-2
traceroute to overcloud-controller-2 (172.17.0.14), 30 hops max, 60 byte packets
 1 overcloud-controller-2.localdomain (172.17.0.14) 0.787 ms !X 0.681 ms !X 0.635 ms !X
[root@overcloud-controller-0 cluster]# /usr/bin/python /sbin/pcs --debug cluster auth overcloud-controller-0 overcloud-controller-1 overcloud-controller-2 -u hacluster -p eiiAvTbJGvbPVokW --force
Running: /usr/bin/ruby -I/usr/lib/pcsd/ /usr/lib/pcsd/pcsd-cli.rb auth
--Debug Input Start--
{"username": "hacluster", "local": false, "nodes": ["overcloud-controller-2", "overcloud-controller-1", "overcloud-controller-0"], "password": "eiiAvTbJGvbPVokW", "force": true}
--Debug Input End--
Return Value: 0
--Debug Output Start--
{
  "status": "ok",
  "data": {
    "auth_responses": {
      "overcloud-controller-2": {
        "status": "noresponse"
      },
      "overcloud-controller-1": {
        "status": "noresponse"
      },
      "overcloud-controller-0": {
        "status": "ok",
        "token": "8bc0f73a-394d-4dab-ba04-de4018df4a5f"
      }
    },
    "sync_successful": true,
    "sync_nodes_err": [

    ],
    "sync_responses": {
    }
  },
  "log": [
    "I, [2017-03-10T14:20:08.265162 #2270] INFO -- : PCSD Debugging enabled\n",
    "D, [2017-03-10T14:20:08.265251 #2270] DEBUG -- : Did not detect RHEL 6\n",
    "I, [2017-03-10T14:20:08.265296 #2270] INFO -- : Running: /usr/sbin/corosync-cmapctl totem.cluster_name\n",
    "I, [2017-03-10T14:20:08.265329 #2270] INFO -- : CIB USER: hacluster, groups: \n",
    "D, [2017-03-10T14:20:08.268641 #2270] DEBUG -- : []\n",
    "D, [2017-03-10T14:20:08.268695 #2270] DEBUG -- : [\"Failed to initialize the cmap API. Error CS_ERR_LIBRARY\\n\"]\n",
    "D, [2017-03-10T14:20:08.268754 #2270] DEBUG -- : Duration: 0.003288473s\n",
    "I, [2017-03-10T14:20:08.268822 #2270] INFO -- : Return Value: 1\n",
    "W, [2017-03-10T14:20:08.268882 #2270] WARN -- : Cannot read config 'corosync.conf' from '/etc/corosync/corosync.conf': No such file\n",
    "W, [2017-03-10T14:20:08.268947 #2270] WARN -- : Cannot read config 'corosync.conf' from '/etc/corosync/corosync.conf': No such file or directory - /etc/corosync/corosync.conf\n",
    "I, [2017-03-10T14:20:08.272840 #2270] INFO -- : No response from: overcloud-controller-2 request: /auth, exception: No route to host - connect(2)\n",
    "I, [2017-03-10T14:20:08.272969 #2270] INFO -- : No response from: overcloud-controller-1 request: /auth, exception: No route to host - connect(2)\n",
    "I, [2017-03-10T14:20:08.429989 #2270] INFO -- : Running: /usr/sbin/pcs status nodes corosync\n",
    "I, [2017-03-10T14:20:08.430061 #2270] INFO -- : CIB USER: hacluster, groups: \n",
    "D, [2017-03-10T14:20:09.100646 #2270] DEBUG -- : []\n",
    "D, [2017-03-10T14:20:09.100763 #2270] DEBUG -- : [\"Error: Unable to read /etc/corosync/corosync.conf: No such file or directory\\n\"]\n",
    "D, [2017-03-10T14:20:09.100818 #2270] DEBUG -- : Duration: 0.670553772s\n",
    "I, [2017-03-10T14:20:09.100913 #2270] INFO -- : Return Value: 1\n",
    "I, [2017-03-10T14:20:09.101561 #2270] INFO -- : Saved config 'tokens' version 665 327998fb8...

[Michele Baldessari (michele)]

Seems like a duplicate of https://bugs.launchpad.net/tripleo/+bug/1657108. If you build an image with the fixed-in tripleo-common you should not see this issue.

[Emilien Macchi (emilienm)]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE