xenapi: secgroups are not in place for a short duration after live-migration

[John Garbutt]

The previous bug on security groups was only a partial fix:
https://bugs.launchpad.net/nova/+bug/1202266

There is a small amount of time where the security group is not in place.

The full fix for this may be possible using XenServer hooks, but may require modifications to XenServer.

(this is a security bug has already been made public in the other bugs around this issue)

[Kurt Seifried (kseifried)]

Does this issue require a CVE?

[John Garbutt (johngarbutt)]

I thought it was mentioned in an existing CVE around the fix.

[John Garbutt (johngarbutt)]

The best fix involves XenAPI starting the instance paused, so nova can make changes, maybe in a hook, maybe then starting the instance. Either way, needs XenServer changes really :(

[Sean Dague (sdague)]

Definitely not Triaged

[Sean Dague (sdague)]

Marking as low as it is a single hypervisor backend

[Bob Ball (bob-ball)]

Sorry - my mistake. I thought Huan's change fixed this; I don't believe so now and need further thought.

[Markus Zoeller (markus_z) (mzoeller)]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY