For Fuel 7.0 and later this bug is reproduced only when serialization in enabled ("fuel task --delete -f --tid 11 --yaml"). Is it unexpected behaviour too, which has to be fixed?
Now by default python-fuelclient doesn't print serialized response when 'delete' action for task is performed. We only see message "Tasks with id's ... deleted":
[root@fuel ~]# fuel network --env 1 --verify
Verification status is 'running'. message: None
For Fuel 7.0 and later this bug is reproduced only when serialization in enabled ("fuel task --delete -f --tid 11 --yaml"). Is it unexpected behaviour too, which has to be fixed?
Now by default python-fuelclient doesn't print serialized response when 'delete' action for task is performed. We only see message "Tasks with id's ... deleted":
[root@fuel ~]# fuel network --env 1 --verify
Verification status is 'running'. message: None
[root@fuel ~]# fuel task ------| ------- ------- ------- ----|-- ------- |------ ----|-- ------- ------- ------- ------- ------- 886f-46e6- bf2a-f6adfbe3dd f7 e3bf-46f8- 9d5a-216f2fb9d4 68 5cd4-4d0d- adf8-72a462cf23 2f availability | 1 | 0 | a0f2036c- 3c82-4ac2- 825b-c6798fea62 a6 7a3c-4f9c- a204-6b14d25c5b 04 c0a9-40f6- 9b94-fbdeff2c33 a2
id | status | name | cluster | progress | uuid
---|---
6 | ready | deployment | 1 | 100 | a9e97e69-
1 | ready | deploy | 1 | 100 | 251ba3d2-
19 | running | check_dhcp | 1 | 0 | 07ec3ced-
20 | running | check_repo_
18 | running | verify_networks | 1 | 0 | 4b0a9da5-
5 | ready | provision | 1 | 100 | c737a8d8-
[root@fuel ~]# fuel task --delete -f --tid 18
Tasks with id's 18 deleted.