fuel2 env delete fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Roman Prykhodchenko | ||
6.1.x |
Won't Fix
|
High
|
Unassigned |
Bug Description
The fuel2 client fails each time when I try to delete an environment.
1. Create an environment:
# fuel2 env create -r 37 -n neutron -nst vlan just-new
2. Delete the newly created environment:
# fuel2 env delete 5
3. You will get an error (in the debug mode):
File "/usr/lib/
result = cmd.run(
File "/usr/lib/
File "/usr/lib/
if env.status == 'operational' and not parsed_args.force:
AttributeError: 'dict' object has no attribute 'status'
Traceback (most recent call last):
File "/usr/bin/fuel2", line 10, in <module>
File "/usr/lib/
return func(*args, **kwargs)
File "/usr/lib/
return fuelclient_
File "/usr/lib/
result = self.run_
File "/usr/lib/
result = cmd.run(
File "/usr/lib/
File "/usr/lib/
if env.status == 'operational' and not parsed_args.force:
AttributeError: 'dict' object has no attribute 'status'
summary: |
- fuel2 env delete failed + fuel2 env delete fails |
Changed in fuel: | |
status: | New → Confirmed |
importance: | Undecided → High |
assignee: | nobody → Roman Prykhodchenko (romcheg) |
milestone: | none → 7.0 |
Changed in fuel: | |
status: | Confirmed → In Progress |
Changed in fuel: | |
status: | In Progress → Fix Committed |
tags: | added: on-verification |
My concern is about targeting this to 7.0. The new client stops working in one of its major scenarios, sounds like a critical problem which has to be fixed in 6.1.
The solution is relatively simple: one line of a code is screwed up, so the fix is simple and easy. The bigger problem is that this particular bug was not detected because mocking of the client-library is done wrong. To fix that problem it's necessary to introduce plenty of similar changes to v2/cli tests to ensure, the same problem won't appear in a different place.
There is a workaround for this bug which is to use the old CLI, i. e., fuel, not fuel2.