nova-manage vm list active
Bug #1494841 reported by
Kevin Fox
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Wishlist
|
Matt Riedemann |
Bug Description
Pre Kilo, nova-manage vm list only showed active vm's. This was useful for ops to track down what vms were on which hosts, etc.
After kilo, all the deleted ones are returned too. This is ok, but its much slower to query if you |grep active.
There needs to be an --active flag or something to filter on the db side for better performance.
Changed in nova: | |
assignee: | nobody → Sriteja (sriteja-alapati) |
tags: | added: nova-manage |
Changed in nova: | |
assignee: | Sriteja (sriteja-alapati) → nobody |
Changed in nova: | |
assignee: | nobody → Raga lahari (raga-lahari) |
Changed in nova: | |
importance: | Low → Wishlist |
Changed in nova: | |
assignee: | nobody → Sujitha (sujitha-neti) |
To post a comment you must log in.
I assume this changed with [1]. The DB api returns the deleted instances by default, as long as the filter says otherwise [2]. "nova-manage" defines this filter in the context, but this context isn't used by the DB api.
[1] commit "Convert nova-manage list to use Instance objects"; /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=ba5c71d8d38 136e804409f93d7 dc2cc7a79427fe get_all_ by_filters_ sort"; /github. com/openstack/ nova/blob/ master/ nova/db/ sqlalchemy/ api.py# L1883
https:/
[2] method "instance_
https:/