{"push_id":948489530,"size":1,"distinct_size":1,"ref":"refs/heads/ignore-node-cibs2","head":"b26127f994a9db2e634db4086443bf01800e108e","before":"990bceb662e6fc737fa36b184677ffc6e4c7c594","commits":[{"sha":"b26127f994a9db2e634db4086443bf01800e108e","author":{"email":"4342b29caadd28ff38359776cc35a8cfc392e9cf@suse.com","name":"Vincent Untz"},"message":"pacemaker: Be stricter when parsing \"crm configure show\" output\n\nIn some very rare cases, we can get \"crm configure show $foo\" return\nmore than one CIB objects. This seems to happen for remote nodes that\nhave attributes.\n\n$ crm configure show remote-d52-54-77-77-77-04\nnode remote-d52-54-77-77-77-04:remote \\\n        attributes OpenStack-role=compute\nprimitive remote-d52-54-77-77-77-04 ocf:pacemaker:remote \\\n        params reconnect_interval=60s server=d52-54-77-77-77-04.h9.cloud.suse.de \\\n        op monitor interval=20s \\\n        op start timeout=60s interval=0 \\\n        op stop timeout=60s interval=0\n\nTo avoid this situation, we are stricter and only keep for parsing the\nobject definition that has the exact name\n(\"remote-d52-54-77-77-77-04:remote\" is different from\n\"remote-d52-54-77-77-77-04\").\n\nUnfortunately, a side effect is that we cannot use anymore the CIBObject\nclass to parse remote node.","distinct":true,"url":"https://api.github.com/repos/vuntz/crowbar-ha/commits/b26127f994a9db2e634db4086443bf01800e108e"}]}