{"action":"created","issue":{"url":"https://api.github.com/repos/ClusterLabs/pacemaker/issues/873","labels_url":"https://api.github.com/repos/ClusterLabs/pacemaker/issues/873/labels{/name}","comments_url":"https://api.github.com/repos/ClusterLabs/pacemaker/issues/873/comments","events_url":"https://api.github.com/repos/ClusterLabs/pacemaker/issues/873/events","html_url":"https://github.com/ClusterLabs/pacemaker/pull/873","id":123846910,"number":873,"title":"High : fencing_topology is not reflected.","user":{"login":"HideoYamauchi","id":946043,"avatar_url":"https://avatars.githubusercontent.com/u/946043?v=3","gravatar_id":"","url":"https://api.github.com/users/HideoYamauchi","html_url":"https://github.com/HideoYamauchi","followers_url":"https://api.github.com/users/HideoYamauchi/followers","following_url":"https://api.github.com/users/HideoYamauchi/following{/other_user}","gists_url":"https://api.github.com/users/HideoYamauchi/gists{/gist_id}","starred_url":"https://api.github.com/users/HideoYamauchi/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/HideoYamauchi/subscriptions","organizations_url":"https://api.github.com/users/HideoYamauchi/orgs","repos_url":"https://api.github.com/users/HideoYamauchi/repos","events_url":"https://api.github.com/users/HideoYamauchi/events{/privacy}","received_events_url":"https://api.github.com/users/HideoYamauchi/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-12-25T02:52:35Z","updated_at":"2016-01-06T22:38:32Z","closed_at":"2016-01-06T22:38:32Z","pull_request":{"url":"https://api.github.com/repos/ClusterLabs/pacemaker/pulls/873","html_url":"https://github.com/ClusterLabs/pacemaker/pull/873","diff_url":"https://github.com/ClusterLabs/pacemaker/pull/873.diff","patch_url":"https://github.com/ClusterLabs/pacemaker/pull/873.patch"},"body":"Hi All,\r\n\r\nThe stonith understands only the last level even if I set fencing_topology.\r\n\r\nOnly prmStonith1-2 and prmStonith2-2 become effective in the next example.\r\n\r\n```\r\n<fencing-topology>\r\n<!--### Fencing Topology ###-->\r\n<fencing-level devices=\"prmStonith1-1\" index=\"1\" target=\"rh72-01\"\r\nid=\"fencing\"/>\r\n<fencing-level devices=\"prmStonith1-2\" index=\"2\" target=\"rh72-01\"\r\nid=\"fencing-0\"/>\r\n<fencing-level devices=\"prmStonith2-1\" index=\"1\" target=\"rh72-02\"\r\nid=\"fencing-1\"/>\r\n<fencing-level devices=\"prmStonith2-2\" index=\"2\" target=\"rh72-02\"\r\nid=\"fencing-2\"/>\r\n</fencing-topology>\r\n```\r\n\r\nPlease reflect this correction for release of Pacemaker1.1.14.\r\n\r\nBest Regards,\r\nHideo Yamauch."},"comment":{"url":"https://api.github.com/repos/ClusterLabs/pacemaker/issues/comments/169485069","html_url":"https://github.com/ClusterLabs/pacemaker/pull/873#issuecomment-169485069","issue_url":"https://api.github.com/repos/ClusterLabs/pacemaker/issues/873","id":169485069,"user":{"login":"kgaillot","id":8730570,"avatar_url":"https://avatars.githubusercontent.com/u/8730570?v=3","gravatar_id":"","url":"https://api.github.com/users/kgaillot","html_url":"https://github.com/kgaillot","followers_url":"https://api.github.com/users/kgaillot/followers","following_url":"https://api.github.com/users/kgaillot/following{/other_user}","gists_url":"https://api.github.com/users/kgaillot/gists{/gist_id}","starred_url":"https://api.github.com/users/kgaillot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kgaillot/subscriptions","organizations_url":"https://api.github.com/users/kgaillot/orgs","repos_url":"https://api.github.com/users/kgaillot/repos","events_url":"https://api.github.com/users/kgaillot/events{/privacy}","received_events_url":"https://api.github.com/users/kgaillot/received_events","type":"User","site_admin":false},"created_at":"2016-01-06T22:38:32Z","updated_at":"2016-01-06T22:38:32Z","body":"I have pulled this commit into the 1.1 branch and released it there with related fixes, so I am closing this request. It will be pulled back into master after the next release candidate (probably later this week). Thanks for finding and patching the issue!"}}