Controllers was not deleted from corosync after stop deployment and deleting added nodes

[Vasily Gorin]

Scenario:
1. Deploy any environment with 1 controller and NeutronTUN or NeutronVLAN
2. Add 2 controllers to the cluster
3. Deploy changes
4. Stop deployment at the middle of deployment of added controllers
5. Remove these added controllers from the cluster
6. Run OSTF

Expected result:
OSTF passed

Actual result:
OSTF Failed with following exception:

Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/unittest2/case.py", line 340, in run
    testMethod()
  File "/usr/lib/python2.6/site-packages/fuel_health/tests/ha/test_pacemaker_status.py", line 72, in test_check_pacemaker_resources
    'differs from the actual controllers status.'.format(fqdn))
  File "/usr/lib/python2.6/site-packages/fuel_health/common/test_mixins.py", line 164, in verify_response_true
    self.fail(message.format(failed_step_msg, msg))
  File "/usr/lib/python2.6/site-packages/unittest2/case.py", line 415, in fail
    raise self.failureException(msg)
AssertionError: Step 2 failed: Online/Offline nodes on the controller node-6.test.domain.local differs from the actual controllers status.. Please refer to OpenStack logs for more details.

......

l: {'Offline': ['node-10.test.domain.local', 'node-9.test.domain.local'], 'Online': ['node-6.test.domain.local']}.
--------------------- >> end captured logging << ---------------------

What I saw in corosync.conf:

nodelist {
  node {
    # node-10.test.domain.local
    ring0_addr: 10.109.2.6
    nodeid: 10
  }
  node {
    # node-6.test.domain.local
    ring0_addr: 10.109.2.3
    nodeid: 6
  }
  node {
    # node-9.test.domain.local
    ring0_addr: 10.109.2.7
    nodeid: 9
  }
}

Version:
7.0 Iso(301) with MU

[Tatyanka (tatyana-leontovich)]

Sorry guys but looks like test scenario was not fully completed so that nodes stay in corosync. Last task in astute is a015-11-05T13:47:14 info: [669] Casting message to Nailgun: {"method"=>"stop_deployment_resp", "args"=>{"task_uuid"=>"de6cddbc-61d9-412a-a027-37a44e59f89f", "status"=>"ready", "progress"=>100,]}} and node deletion without re-deployment - so that those nodes stays in corosync. Move issue in invalid according to explanation above