| 2020-05-18 09:21:15 |
Jacky Wang |
bug |
|
|
added bug |
| 2020-05-18 09:23:03 |
Xuchu Jiang |
cinder: assignee |
|
Xuchu Jiang (xcnix) |
|
| 2020-05-20 02:35:59 |
OpenStack Infra |
cinder: status |
New |
In Progress |
|
| 2020-11-12 07:07:10 |
cao biao |
attachment added |
|
snapshot.png https://bugs.launchpad.net/cinder/+bug/1879285/+attachment/5433727/+files/snapshot.png |
|
| 2021-08-19 09:46:31 |
Jacky Wang |
description |
SVC version : 7.8.10
cinder (14.0.2.dev33)
------
Test steps:
Create 2 snapshots on the same base-volume
case1:
From 1st snapshot, create new-volume with the same size as base-volume : success
case2:
From 1st snapshot, create new-volume with the larger size than base-volume : success
i.e.
SVC clone new-volume from snapshot : success
SVC extend new-volume : success
case3:
From 2nd snapshot, create new-volume with the same size as base-volume : success
case4:
From 2nd snapshot, create new-volume with the larger size than base-volume : Fail - very high probablity > 95%
i.e.
SVC clone new-volume from snapshot : stuck in copy progress 100%
SVC extend new-volume : pending due to above stuck
case5:
Delete the 1st snapshot, then from 2nd snapshot, create new-volume with the larger size than base-volume : success
Summary:
Per tests so far, the issue only happens when meets a and b
a. more than one snapshot exists on base volume
b. from 2nd/3rd/... snapshot, create new-volume with the larger size than base-volume |
The issue can be recreated by the following steps:
1. Create 2 snapshots in sequence from the same base volume, naming as 1st_snapshot and 2nd_snapshot respectively.
(For example, the size of the base volume is 10 GB)
2. From the 2nd_snapshot, cloning a new volume with size larger than the base volume
fails frequently with the following phenomena:
(For example, the size of the new volume is 20 GB)
The clone progress stuck in 100% forever as shown in the screenshot,
resulting in the pending of extending the volume size. |
|
| 2021-08-19 09:51:42 |
Jacky Wang |
attachment added |
|
Storwize_GUI_shows_clone_progress_stuck.png https://bugs.launchpad.net/cinder/+bug/1879285/+attachment/5519051/+files/Storwize_GUI_shows_clone_progress_stuck.png |
|
| 2021-08-19 09:52:30 |
Jacky Wang |
description |
The issue can be recreated by the following steps:
1. Create 2 snapshots in sequence from the same base volume, naming as 1st_snapshot and 2nd_snapshot respectively.
(For example, the size of the base volume is 10 GB)
2. From the 2nd_snapshot, cloning a new volume with size larger than the base volume
fails frequently with the following phenomena:
(For example, the size of the new volume is 20 GB)
The clone progress stuck in 100% forever as shown in the screenshot,
resulting in the pending of extending the volume size. |
The issue can be recreated by the following steps:
1. Create 2 snapshots in sequence from the same base volume, naming as 1st_snapshot and 2nd_snapshot respectively.
(For example, the size of the base volume is 10 GB)
2. From the 2nd_snapshot, cloning a new volume with size larger than the base volume
fails frequently with the following phenomena:
(For example, the size of the new volume is 20 GB)
The clone progress stuck in 100% forever as shown in the screenshot from Storwize GUI,
resulting in the pending of extending the volume size.
Screenshot: (Storwize_GUI_shows_clone_progress_stuck.png) |
|
| 2021-08-19 10:33:17 |
Jacky Wang |
summary |
creating extending volume from 2nd snapshot stuck in 100% copy progress |
[SVF] creating extending volume from 2nd snapshot stuck in 100% copy progress |
|
| 2021-08-19 10:34:13 |
Jacky Wang |
description |
The issue can be recreated by the following steps:
1. Create 2 snapshots in sequence from the same base volume, naming as 1st_snapshot and 2nd_snapshot respectively.
(For example, the size of the base volume is 10 GB)
2. From the 2nd_snapshot, cloning a new volume with size larger than the base volume
fails frequently with the following phenomena:
(For example, the size of the new volume is 20 GB)
The clone progress stuck in 100% forever as shown in the screenshot from Storwize GUI,
resulting in the pending of extending the volume size.
Screenshot: (Storwize_GUI_shows_clone_progress_stuck.png) |
The issue can be recreated by the following steps:
Use Storwize volume driver to :
1. Create 2 snapshots in sequence from the same base volume, naming as 1st_snapshot and 2nd_snapshot respectively.
(For example, the size of the base volume is 10 GB)
2. From the 2nd_snapshot, cloning a new volume with size larger than the base volume
fails frequently with the following phenomena:
(For example, the size of the new volume is 20 GB)
The clone progress stuck in 100% forever as shown in the screenshot from Storwize GUI,
resulting in the pending of extending the volume size.
Screenshot: (Storwize_GUI_shows_clone_progress_stuck.png) |
|
