"heat stack-adopt" command gives all the stacks in output instead of specified stack

Bug #1432547 reported by rajiv
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-heatclient
New
Undecided
rajiv

Bug Description

"heat stack-adopt" command gives all the stacks in output instead giving only the specified stack in the command. For example

[root@packstack ~(keystone_admin)]# heat stack-adopt -a stack_data test
+--------------------------------------+-------------+--------------------+----------------------+
| id | stack_name | stack_status | creation_time |
+--------------------------------------+-------------+--------------------+----------------------+
| 631ba443-eb88-4c56-852d-17e664e21212 | thenakliman | CREATE_COMPLETE | 2015-03-12T11:36:11Z |
| c43fff88-e4b0-41b0-8780-42071ce48890 | test | CREATE_IN_PROGRESS | 2015-03-13T03:51:39Z |
+--------------------------------------+-------------+--------------------+----------------------+
[root@packstack ~(keystone_admin)]# heat stack-list
+--------------------------------------+-------------+-----------------+----------------------+
| id | stack_name | stack_status | creation_time |
+--------------------------------------+-------------+-----------------+----------------------+
| 631ba443-eb88-4c56-852d-17e664e21212 | thenakliman | CREATE_COMPLETE | 2015-03-12T11:36:11Z |
| c43fff88-e4b0-41b0-8780-42071ce48890 | test | ADOPT_COMPLETE | 2015-03-13T03:51:39Z |
+--------------------------------------+-------------+-----------------+----------------------+

output must have been only the second row. In my setup, i am using following version

[root@packstack ~(keystone_admin)]# heat-manage --version
2014.2.1

rajiv (rajiv-kumar)
Changed in python-heatclient:
assignee: nobody → rajiv (rajiv-kumar)
Revision history for this message
rajiv (rajiv-kumar) wrote :

If i fix bug for https://bugs.launchpad.net/python-heatclient/+bug/1432533 , it won't fix this reported bug. To make this bug being fixed by stack-create bug will make me to change stack-list method.

 I thinks above change won't be a good idea. I think better idea is to use stack-show instead of stack-list for this bug. All the components of openstack also uses this approach.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.