yahoo-eng-team team mailing list archive

[Jeremy Stanley <fungi@xxxxxxxxxxx>]

** Summary changed:

- nova rescue doesn't put VM into RESCUE status on vmware (CVE-2014-2573)
+ [OSSA 2014-017] nova rescue doesn't put VM into RESCUE status on vmware (CVE-2014-2573)

** Changed in: ossa
       Status: Fix Committed => Fix Released

-- 
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/1269418

Title:
  [OSSA 2014-017] nova rescue doesn't put VM into RESCUE status on
  vmware (CVE-2014-2573)

Status in OpenStack Compute (Nova):
  Fix Committed
Status in OpenStack Compute (nova) havana series:
  Fix Committed
Status in OpenStack Compute (nova) icehouse series:
  Fix Committed
Status in The OpenStack VMwareAPI subTeam:
  In Progress
Status in OpenStack Security Advisories:
  Fix Released

Bug description:
  nova rescue of VM on vmWare will create a additional VM ($ORIGINAL_ID-
  rescue), but after that, the original VM has status ACTIVE. This leads
  to

  [root@jhenner-node ~(keystone_admin)]# nova unrescue foo
  ERROR: Cannot 'unrescue' while instance is in vm_state stopped (HTTP 409) (Request-ID: req-792cabb2-2102-47c5-9b15-96c74a9a4819)

  the original can be deleted, which then causes leaking of the -rescue
  VM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1269418/+subscriptions