Activity log for bug #1893114
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2020-08-26 17:40:35 | Brian Rosmaita | bug | added bug | ||
| 2020-08-26 17:42:11 | Brian Rosmaita | cinder: importance | Undecided | High | |
| 2020-08-26 17:42:11 | Brian Rosmaita | cinder: status | New | Triaged | |
| 2020-08-26 17:42:11 | Brian Rosmaita | cinder: milestone | victoria-3 | ||
| 2020-08-26 17:42:43 | Brian Rosmaita | nominated for series | cinder/ussuri | ||
| 2020-08-26 17:42:43 | Brian Rosmaita | bug task added | cinder/ussuri | ||
| 2020-08-26 18:08:22 | Brian Rosmaita | summary | Cinder Ussuri is running wrong online-data-migrations | Remove untyped volume/snapshot online-data-migrations | |
| 2020-08-26 18:08:32 | Brian Rosmaita | bug task deleted | cinder/ussuri | ||
| 2020-08-26 18:11:37 | Brian Rosmaita | description | Online data migrations were added in Train; they should have been removed in Ussuri, but were not. Hence they need to be removed from master and Ussuri. Need to remove them and include an upgrade check in the status tool as was done to correct this problem previously for a different set of upgrades. See https://review.opendev.org/#/c/672466/ | Online data migrations were added in Train; they should have been removed in Ussuri, but were not. However, there was a bug in the Train online migration that needs to be fixed in Ussuri and backported to Train (see Bug #1893107), so the migrations should NOT be removed from Ussuri. No need to include a check in the upgrade status tool because the volume_type_id column was made non-nullable in Ussuri, and hence there can't be any untyped volumes/snapshots to worry about (whether deleted or not.) | |
| 2020-08-26 18:17:21 | Brian Rosmaita | cinder: assignee | Brian Rosmaita (brian-rosmaita) | ||
| 2020-08-26 20:24:39 | OpenStack Infra | cinder: status | Triaged | In Progress | |
| 2020-08-28 19:40:48 | OpenStack Infra | cinder: status | In Progress | Fix Released |
