Comment 4 for bug 1207184

Thanks for pointing this. When looking around the bugs and reviews, I found bug 1203413 too.

With Neutron security group, we need to use ID as security group identifier. (bug 1203413 is correct).
What I haven't investigated is whether nova accepts security group ID in editing security groups for a instance.

There are three cases with security group. Very tricky...
(a1) nova security group API with nova-network backend
(a2) nova security group API with neutron backend
(b) neutron security group API (with neutron)

IMO we must cover at least (a1) and (b) and (a2) is optional.

If nova accepts ID, the solution of bug 1203413 is best.
Otherwise, (as a workaround) sg.name is copied to sg.id in SecurityGroupManager in api/nova.py.

However, if nova does not accept security group ID, (a1) and (a2) cannot be coexist and it seems to be a bug of Nova.

I will continue to investigate the situation tomorrow.