Activity log for bug #1555045

Date Who What changed Old value New value Message
2016-03-09 11:45:35 Chung Chih, Hung bug added bug
2016-03-09 11:45:41 Chung Chih, Hung nova: assignee Chung Chih, Hung (lyanchih)
2016-03-10 03:02:19 Matt Riedemann tags volumes
2016-03-10 03:02:22 Matt Riedemann nova: status New Triaged
2016-03-10 03:02:24 Matt Riedemann nova: importance Undecided Medium
2016-03-10 03:03:15 Matt Riedemann tags volumes compute volumes
2016-03-10 03:58:58 Chung Chih, Hung description Nova can assign seconds to reclaim_instance_interval option which is Interval in seconds for reclaiming deleted instances. If users delete server which had attached volumes ( or boot from volume), those servers will been disappear in server list. Their volumes would still in use and it will have "Attached to **** on /dev/vdb". After interval seconds, nova compute would begin to reclaim those servers. But it will not release those volumes. This cause those volumes became "Attached to None on /dev/vdb". Users need to reset volumes state then can use they again. But those volumes will have "Attached to None on /dev/vdb Attached to **** on /dev/vdb"" We should not only actually delete instances but also detach volumes in reclaiming instances. Nova can assign seconds to reclaim_instance_interval option which is Interval in seconds for reclaiming deleted instances. If users delete server which had attached volumes ( or boot from volume), those servers will been disappear in server list. Their volumes would still in use and it will have "Attached to **** on /dev/vdb". After interval seconds, nova compute would begin to reclaim those servers. But it will not release those volumes. This cause those volumes became "Attached to None on /dev/vdb". Users need to reset volumes state then can use they again. But those volumes will have "Attached to None on /dev/vdb Attached to **** on /dev/vdb"" We should not only actually delete instances but also detach volumes in reclaiming instances. My environment was deployed by devstack. devstack: 6fff3cc03589cb0fdf02b4bedf1c35bcb000f28d nova-client: 3.3.0 nova: 3d7e403cc7a5d9ebcd9a011d6c2055bfbf56cb05
2016-03-10 03:59:29 Chung Chih, Hung description Nova can assign seconds to reclaim_instance_interval option which is Interval in seconds for reclaiming deleted instances. If users delete server which had attached volumes ( or boot from volume), those servers will been disappear in server list. Their volumes would still in use and it will have "Attached to **** on /dev/vdb". After interval seconds, nova compute would begin to reclaim those servers. But it will not release those volumes. This cause those volumes became "Attached to None on /dev/vdb". Users need to reset volumes state then can use they again. But those volumes will have "Attached to None on /dev/vdb Attached to **** on /dev/vdb"" We should not only actually delete instances but also detach volumes in reclaiming instances. My environment was deployed by devstack. devstack: 6fff3cc03589cb0fdf02b4bedf1c35bcb000f28d nova-client: 3.3.0 nova: 3d7e403cc7a5d9ebcd9a011d6c2055bfbf56cb05 Nova can assign seconds to reclaim_instance_interval option which is Interval in seconds for reclaiming deleted instances. If users delete server which had attached volumes ( or boot from volume), those servers will been disappear in server list. Their volumes would still in use and it will have "Attached to **** on /dev/vdb". After interval seconds, nova compute would begin to reclaim those servers. But it will not release those volumes. This cause those volumes became "Attached to None on /dev/vdb". Users need to reset volumes state then can use they again. But those volumes will have "Attached to None on /dev/vdb Attached to **** on /dev/vdb"" We should not only actually delete instances but also detach volumes in reclaiming instances. My environment was deployed by devstack which is upstream code. devstack: 6fff3cc03589cb0fdf02b4bedf1c35bcb000f28d nova-client: 3.3.0 nova: 3d7e403cc7a5d9ebcd9a011d6c2055bfbf56cb05
2016-04-19 06:53:55 Chung Chih, Hung nova: assignee Chung Chih, Hung (lyanchih)
2016-05-26 09:20:20 Enol Fernández bug added subscriber Enol Fernández
2016-05-30 09:41:01 Alvaro Lopez nova: assignee Alvaro Lopez (aloga)
2016-05-31 06:54:35 Alvaro Lopez nova: assignee Alvaro Lopez (aloga)
2016-06-14 20:20:21 Alvaro Lopez nova: assignee Alvaro Lopez (aloga)
2016-12-07 06:24:13 hebin nova: assignee Alvaro Lopez (aloga) hebin (491309649-t)
2016-12-07 06:25:07 hebin nova: status Triaged In Progress
2016-12-07 06:32:58 hebin nova: status In Progress Confirmed
2017-01-20 21:38:21 Anusha Unnam marked as duplicate 1463856
2018-05-23 15:48:53 Matt Riedemann changed duplicate marker 1463856 1733736