On Mar 27, 2014, at 4:38 PM, Chris Friesen chris.frie...@windriver.com wrote:
On 03/27/2014 04:47 PM, Chris Friesen wrote:
Interestingly, unit test
nova.tests.api.openstack.compute.contrib.test_server_groups.ServerGroupTest.test_display_members
passes just fine, and it seems to be running
On 03/31/2014 03:56 PM, Vishvananda Ishaya wrote:
On Mar 27, 2014, at 4:38 PM, Chris Friesen chris.frie...@windriver.com wrote:
On 03/27/2014 04:47 PM, Chris Friesen wrote:
Interestingly, unit test
I've filed this as a bug (https://bugs.launchpad.net/nova/+bug/1298494)
but I thought I'd post it here as well to make sure it got visibility.
If I create a server group, then boot a server as part of the group,
then run nova server-group-list it doesn't show the server as being a
member of
On 03/27/2014 03:57 PM, Chris Friesen wrote:
If I change the filter to use
'deleted': False
instead of
'deleted_at': None
then it works as expected.
The leads to a couple of questions:
1) There is a column deleted_at in the database table, why can't we
filter on it?
I wonder if maybe
On 03/27/2014 03:57 PM, Chris Friesen wrote:
The leads to a couple of questions:
1) There is a column deleted_at in the database table, why can't we
filter on it?
2) How did this get submitted when it doesn't work?
I've updated to the current codebase in devstack and I'm still seeing
the
On 03/27/2014 04:47 PM, Chris Friesen wrote:
Interestingly, unit test
nova.tests.api.openstack.compute.contrib.test_server_groups.ServerGroupTest.test_display_members
passes just fine, and it seems to be running the same sqlalchemy code.
Is this a case where sqlite behaves differently from
