Back to bug 2178500
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat One Jira (issues.redhat.com) | 2023-03-15 06:12:24 UTC | Link ID | Red Hat Issue Tracker OSP-23090 | |
| Amit Uniyal | 2023-03-15 06:20:14 UTC | Summary | 16.2 - Fix issues with nova-manage volume_attachment subcommand - vms in locked state | 16.2 - #3 - VMs in locked state - Fix issues with nova-manage volume_attachment subcommand |
| Artom Lifshitz | 2023-03-21 17:54:36 UTC | Assignee | nova-maint | osp-dfg-compute |
| Artom Lifshitz | 2023-03-21 20:04:17 UTC | QA Contact | nova-maint | osp-dfg-compute |
| René Ribaud | 2023-03-22 08:33:15 UTC | Keywords | Triaged | |
| Severity | unspecified | high | ||
| Priority | unspecified | high | ||
| Artom Lifshitz | 2023-05-30 17:56:27 UTC | CC | alifshit | |
| Link ID | OpenStack gerrit 873648 | |||
| Keywords | Patch | |||
| Status | NEW | ON_DEV | ||
| Artom Lifshitz | 2023-06-01 15:52:56 UTC | Target Milestone | --- | z6 |
| RHEL Program Management | 2023-06-01 15:54:50 UTC | Target Release | --- | 16.2 (Train on RHEL 8.4) |
| Artom Lifshitz | 2023-06-19 15:25:10 UTC | Assignee | osp-dfg-compute | auniyal |
| Artom Lifshitz | 2023-07-17 16:01:59 UTC | Target Milestone | z6 | z2 |
| RHEL Program Management | 2023-07-17 16:02:10 UTC | Target Release | 16.2 (Train on RHEL 8.4) | 17.1 |
| Ian Frangs | 2023-08-03 15:46:23 UTC | Flags | needinfo?(auniyal) | |
| Amit Uniyal | 2023-08-08 05:26:37 UTC | Flags | needinfo?(auniyal) | |
| Doc Text | Cause: nova-manage volume refresh failed. Consequence: Sometimes on volume refresh fail, the instance stays in the locked state. Fix: add a context manager which will lock and unlock instance for volume refresh, irrespective of volume refresh execution status. Result: after volume refresh instance will stay at the same state as before running volume refresh. | |||
| Doc Type | If docs needed, set a value | Bug Fix | ||
| Erin Peterson | 2023-08-09 18:47:01 UTC | CC | erpeters | |
| Doc Text | Cause: nova-manage volume refresh failed. Consequence: Sometimes on volume refresh fail, the instance stays in the locked state. Fix: add a context manager which will lock and unlock instance for volume refresh, irrespective of volume refresh execution status. Result: after volume refresh instance will stay at the same state as before running volume refresh. | Before this update, the failure of a refresh of a nova-manage volume caused the instance to stay in a locked state. With this update, the addition of a context manager will lock and unlock an instance for a volume refresh regardless of volume refresh execution status. This resolves the issue by returning the instance to the same state it was in before the volume refresh was attempted. | ||
| Ian Frangs | 2023-08-14 14:36:42 UTC | Doc Text | Before this update, the failure of a refresh of a nova-manage volume caused the instance to stay in a locked state. With this update, the addition of a context manager will lock and unlock an instance for a volume refresh regardless of volume refresh execution status. This resolves the issue by returning the instance to the same state it was in before the volume refresh was attempted. | If a volume refresh fails when using the nova-manage CLI, this causes the instance to stay in a locked state. |
| Doc Type | Bug Fix | Known Issue | ||
| Flags | needinfo?(auniyal) | |||
| CC | ifrangs | |||
| Amit Uniyal | 2023-08-14 15:38:55 UTC | Flags | needinfo?(auniyal) |
Back to bug 2178500