yahoo-eng-team team mailing list archive

[Tristan Cacqueray <tristan.cacqueray@xxxxxxxxxxxx>]

This bug is not affecting a released version, let's open it. Feel free
to send patch directly to gerrit now.

** Information type changed from Private Security to Public Security

** Changed in: ossa
       Status: Incomplete => Won't Fix

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

Title:
  Instance files doesn't clean up from destination node in revert-resize
  api for non-shared environment

Status in OpenStack Compute (Nova):
  New
Status in OpenStack Security Advisories:
  Won't Fix

Bug description:
  This issue is being treated as a potential security risk under
  embargo. Please do not make any public mention of embargoed (private)
  security vulnerabilities before their coordinated publication by the
  OpenStack Vulnerability Management Team in the form of an official
  OpenStack Security Advisory. This includes discussion of the bug or
  associated fixes in public forums such as mailing lists, code review
  systems and bug trackers. Please also avoid private disclosure to
  other individuals not already approved for access to this information,
  and provide this same reminder to those who are made aware of the
  issue prior to publication. All discussion should remain confined to
  this private bug report, and any proposed fixes should be added as to
  the bug as attachments.

  When user reverts previously resized instance then it doesn’t clean up
  instance files from destination node in non-shared environment
  (instance path not mounted on shared storage).

  Steps to reproduce:

  1. Create an instance and wait until it's status is set to 'active'
  2. Resize the instance
  3. Check instance files are present on the source and destination compute nodes in the instance file path
  4. Revert the instance previously resized in Step#2

  Instance files are not deleted from the destination compute node.

  This issue is introduced because of the LP bug [1] fixed lately.
  Patch merged [2] in kilo-2 is also back ported to the stable/juno branch [3].

  I have a fix for this problem. I am working on unit tests. As soon as
  patch is ready, I will attached it to this bug.

  [1] https://bugs.launchpad.net/nova/+bug/1399244
  [2] https://review.openstack.org/139693/
  [3] https://review.openstack.org/#/c/149371/

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