| 2015-02-06 08:25:37 |
Rajesh Tailor |
bug |
|
|
added bug |
| 2015-02-06 08:26:16 |
Rajesh Tailor |
bug |
|
|
added subscriber Tushar Patil |
| 2015-02-06 08:27:18 |
Rajesh Tailor |
bug |
|
|
added subscriber Kentaro Takeda |
| 2015-02-06 08:32:33 |
Rajesh Tailor |
nova: assignee |
|
Rajesh Tailor (rajesh-tailor) |
|
| 2015-02-06 12:47:39 |
Jeremy Stanley |
description |
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/ |
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/ |
|
| 2015-02-06 12:48:02 |
Jeremy Stanley |
bug task added |
|
ossa |
|
| 2015-02-06 12:48:20 |
Jeremy Stanley |
ossa: status |
New |
Incomplete |
|
| 2015-02-06 12:48:40 |
Jeremy Stanley |
bug |
|
|
added subscriber Nova Core security contacts |
| 2015-02-06 13:23:43 |
Rajesh Tailor |
attachment added |
|
0001-Delete-instance-files-from-dest-host-in-revert-resize.patch https://bugs.launchpad.net/nova/+bug/1418855/+attachment/4313870/+files/0001-Delete-instance-files-from-dest-host-in-revert-resize.patch |
|
| 2015-02-09 15:35:44 |
Tristan Cacqueray |
information type |
Private Security |
Public Security |
|
| 2015-02-09 15:35:54 |
Tristan Cacqueray |
ossa: status |
Incomplete |
Won't Fix |
|
| 2015-02-09 19:41:49 |
Belmiro Moreira |
bug |
|
|
added subscriber Belmiro Moreira |
| 2015-02-11 00:30:52 |
Davanum Srinivas (DIMS) |
nova: status |
New |
Confirmed |
|
| 2015-02-11 00:30:57 |
Davanum Srinivas (DIMS) |
nova: importance |
Undecided |
Medium |
|
| 2015-02-11 06:07:35 |
OpenStack Infra |
nova: status |
Confirmed |
In Progress |
|
| 2015-03-23 21:38:32 |
OpenStack Infra |
nova: status |
In Progress |
Fix Committed |
|
| 2015-04-10 09:20:59 |
Thierry Carrez |
nova: status |
Fix Committed |
Fix Released |
|
| 2015-04-10 09:20:59 |
Thierry Carrez |
nova: milestone |
|
kilo-rc1 |
|
| 2015-04-14 21:26:59 |
Jeremy Stanley |
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/ |
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/ |
|
| 2015-04-30 09:27:54 |
Thierry Carrez |
nova: milestone |
kilo-rc1 |
2015.1.0 |
|
