yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #15154
[Bug 1298494] Re: "nova server-group-list" doesn't show members of the group
** Also affects: nova/icehouse
Importance: Undecided
Status: New
** Changed in: nova/icehouse
Status: New => Fix Committed
** Changed in: nova/icehouse
Milestone: None => 2014.1.1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1298494
Title:
"nova server-group-list" doesn't show members of the group
Status in OpenStack Compute (Nova):
Fix Committed
Status in OpenStack Compute (nova) icehouse series:
Fix Committed
Bug description:
With current devstack I ensured I had "GroupAntiAffinityFilter" in
scheduler_default_filters in /etc/nova/nova.conf, restarted nova-
scheduler, then ran:
nova server-group-create --policy anti-affinity antiaffinitygroup
nova server-group-list
+--------------------------------------+-------------------+--------------------+---------+----------+
| Id | Name | Policies | Members | Metadata |
+--------------------------------------+-------------------+--------------------+---------+----------+
| 5d639349-1b77-43df-b13f-ed586e73b3ac | antiaffinitygroup | [u'anti-affinity'] | [] | {} |
+--------------------------------------+-------------------+--------------------+---------+----------+
nova boot --flavor=1 --image=cirros-0.3.1-x86_64-uec --hint group=5d639349-1b77-43df-b13f-ed586e73b3ac cirros0
nova list
+--------------------------------------+---------+--------+------------+-------------+--------------------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+---------+--------+------------+-------------+--------------------+
| a7a3ec40-85d9-4b72-a522-d1c0684f3ada | cirros0 | ACTIVE | - | Running | private=10.4.128.2 |
+--------------------------------------+---------+--------+------------+-------------+--------------------+
Then I tried listing the groups, and it didn't print the newly-booted
instance as a member:
nova server-group-list
+--------------------------------------+-------------------+--------------------+---------+----------+
| Id | Name | Policies | Members | Metadata |
+--------------------------------------+-------------------+--------------------+---------+----------+
| 5d639349-1b77-43df-b13f-ed586e73b3ac | antiaffinitygroup | [u'anti-affinity'] | [] | {} |
+--------------------------------------+-------------------+--------------------+---------+----------+
Rerunning the nova command with --debug we see that the problem is in nova, not novaclient:
RESP BODY: {"server_groups": [{"members": [], "metadata": {}, "id":
"5d639349-1b77-43df-b13f-ed586e73b3ac", "policies": ["anti-affinity"],
"name": "antiaffinitygroup"}]}
Looking at the database, we see that the instance is actually tracked as a member of the list (along with two other instances that haven't been marked as deleted yet, which is also a bug I think).
mysql> select * from instance_group_member;
+---------------------+------------+------------+---------+----+--------------------------------------+----------+
| created_at | updated_at | deleted_at | deleted | id | instance_id | group_id |
+---------------------+------------+------------+---------+----+--------------------------------------+----------+
| 2014-03-26 20:19:14 | NULL | NULL | 0 | 1 | d289502b-57fc-46f6-b39d-66a1db3a9ebc | 1 |
| 2014-03-26 20:25:04 | NULL | NULL | 0 | 2 | e07f1f15-4e93-4845-9203-bf928c196a78 | 1 |
| 2014-03-26 20:35:11 | NULL | NULL | 0 | 3 | a7a3ec40-85d9-4b72-a522-d1c0684f3ada | 1 |
+---------------------+------------+------------+---------+----+--------------------------------------+----------+
3 rows in set (0.00 sec)
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1298494/+subscriptions
References