Controllers was not deleted from corosync after stop deployment and deleting added nodes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Invalid
|
High
|
Fuel Python (Deprecated) | ||
7.0.x |
Invalid
|
High
|
Fuel Python (Deprecated) |
Bug Description
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/
testMethod()
File "/usr/lib/
'differs from the actual controllers status.
File "/usr/lib/
self.
File "/usr/lib/
raise self.failureExc
AssertionError: Step 2 failed: Online/Offline nodes on the controller node-6.
......
l: {'Offline': ['node-
-------
What I saw in corosync.conf:
nodelist {
node {
# node-10.
ring0_addr: 10.109.2.6
nodeid: 10
}
node {
# node-6.
ring0_addr: 10.109.2.3
nodeid: 6
}
node {
# node-9.
ring0_addr: 10.109.2.7
nodeid: 9
}
}
Version:
7.0 Iso(301) with MU
description: | updated |
tags: | added: area-python |
Changed in fuel: | |
status: | New → Confirmed |
Changed in fuel: | |
milestone: | 7.0-updates → 8.0 |
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-37a44e59f8 9f", "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