Back to bug 1020930
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| RHEL Program Management | 2013-10-18 14:40:18 UTC | Target Release | --- | 4.0 |
| Dave Allan | 2013-10-28 21:35:25 UTC | Status | NEW | ASSIGNED |
| CC | dallan | |||
| Assignee | rhos-maint | vpopovic | ||
| Nikola Dipanov | 2013-10-29 18:38:09 UTC | Status | ASSIGNED | ON_DEV |
| Assignee | vpopovic | ndipanov | ||
| Nikola Dipanov | 2013-10-29 18:40:23 UTC | Summary | nova: rebuild of backup which had no volume attached will detach the volume in cinder/nova but not in the instance | nova: rebuild with volume attached leaves instance without the volume and in an inconsistent state |
| Nikola Dipanov | 2013-10-30 18:57:04 UTC | Link ID | OpenStack gerrit 54545 | |
| Nikola Dipanov | 2013-11-18 13:11:12 UTC | Status | ON_DEV | MODIFIED |
| Nikola Dipanov | 2013-11-18 13:11:42 UTC | Status | MODIFIED | POST |
| Xavier Queralt | 2013-12-02 15:53:42 UTC | CC | xqueralt | |
| Target Milestone | --- | rc | ||
| Xavier Queralt | 2013-12-02 16:55:10 UTC | Status | POST | MODIFIED |
| Fixed In Version | openstack-nova-2013.2-6.el6ost | |||
| Doc Text | After the changes in the block device mappings, the rebuild action was not reattaching the volumes used by an instance. This left the volume in an state where it could not be attached any more to an instance. We've updated the rebuild action to use the new block device mappings so they are not ignored. | |||
| Dave Allan | 2013-12-04 18:56:09 UTC | Assignee | ndipanov | xqueralt |
| errata-xmlrpc | 2013-12-04 21:10:54 UTC | Status | MODIFIED | ON_QA |
| Don Domingo | 2013-12-11 00:18:54 UTC | CC | ddomingo | |
| Doc Text | After the changes in the block device mappings, the rebuild action was not reattaching the volumes used by an instance. This left the volume in an state where it could not be attached any more to an instance. We've updated the rebuild action to use the new block device mappings so they are not ignored. | Previously, rebuilding an instance with a volume attached would leave the volume in an inconsistent state; the instance would be rebuilt without the volume attached, and the volume could not be attached to any instance. This was because during rebuilds, Nova did not check for any changes in block device mappings to attached volumes first. With this fix, Nova now checks for new block device mappings during rebuilds. When rebuilding an instance, any attached volumes will be reattached after the rebuild process. |
||
| Dafna Ron | 2013-12-11 15:00:38 UTC | Docs Contact | dron | |
| Dafna Ron | 2013-12-11 19:02:47 UTC | Status | ON_QA | VERIFIED |
| Don Domingo | 2013-12-11 23:34:08 UTC | Doc Text | Previously, rebuilding an instance with a volume attached would leave the volume in an inconsistent state; the instance would be rebuilt without the volume attached, and the volume could not be attached to any instance. This was because during rebuilds, Nova did not check for any changes in block device mappings to attached volumes first. With this fix, Nova now checks for new block device mappings during rebuilds. When rebuilding an instance, any attached volumes will be reattached after the rebuild process. | Previously, rebuilding an instance with a volume attached would leave the volume in an inconsistent state; the instance would be rebuilt without the volume attached, and the volume could not be attached to any instance. This was because during rebuilds, the Compute service did not check for any changes in block device mappings to attached volumes first. With this fix, the Compute service now checks for new block device mappings during rebuilds. When rebuilding an instance, any attached volumes will be reattached after the rebuild process. |
| errata-xmlrpc | 2013-12-19 17:35:28 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2013-12-20 00:29:44 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2013-12-19 19:29:44 UTC | |||
| Russell Bryant | 2019-09-09 15:48:14 UTC | CC | rbryant |
Back to bug 1020930