Fuel CLI doesn't really deletes nodes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Invalid
|
High
|
Fuel Python (Deprecated) | ||
8.0.x |
Invalid
|
High
|
Fuel Python (Deprecated) | ||
Mitaka |
Invalid
|
High
|
Fuel Python (Deprecated) |
Bug Description
Step to reproduce:
1) Deploy 3 controller 1 compute
2) Shutdown one node offline and wait when it goes offline
3) Delete this node from CLI
[root@nailgun ~]# fuel --env 1 node remove --node 1
Nodes with ids [1] were removed from environment with id 1.
4) List nodes on CLI/UI
Expected result:
Node should be deleted.
node_deletion task should exists
Actual result:
Node still in list.
node_deletion task not in task list
Retrying for deletion return:
[root@nailgun ~]# fuel node remove --node 1
400 Client Error: Bad Request (Can't unassign nodes with ids <nailgun.
release: "8.0"
api: "1.0"
build_number: "496"
build_id: "496"
fuel-nailgun_sha: "934c2d11b23419
python-
fuel-agent_sha: "e40bcfbb1f5518
fuel-
astute_sha: "b81577a5b7857c
fuel-library_sha: "b91e96e848057b
fuel-ostf_sha: "ab5fd151fc6c1a
fuel-mirror_sha: "351d568fa3b3e4
fuelmenu_sha: "234cb4cbb30fbd
shotgun_sha: "63645dea384a37
network-
fuel-upgrade_sha: "616a7490ec7199
fuelmain_sha: "6b993b3004e8d9
Changed in fuel: | |
status: | New → Confirmed |
This bug is invalid because you should have used
`fuel node --node-id 1 --delete-from-db` and taken care of this node by yourselves