Back to bug 2184834
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| RHEL Program Management | 2023-04-05 21:55:33 UTC | Target Release | 17.1 --- | --- 17.1 |
| Red Hat One Jira (issues.redhat.com) | 2023-04-05 21:56:38 UTC | Link ID | Red Hat Issue Tracker OSP-24012 | |
| Brian Rosmaita | 2023-04-05 21:58:35 UTC | Link ID | OpenStack gerrit 874865 Launchpad 2008259 | |
| Status | ASSIGNED | POST | ||
| Martin Kopec | 2023-04-06 09:50:48 UTC | Blocks | 2184840 | |
| Martin Kopec | 2023-04-21 13:06:51 UTC | CC | mkopec | |
| Martin Kopec | 2023-05-04 05:36:59 UTC | Blocks | 2184840 | |
| Depends On | 2184840 | |||
| Yogev Rabl | 2023-05-10 16:03:12 UTC | CC | yrabl | |
| QA Contact | eshames | ybenshim | ||
| Brian Rosmaita | 2023-05-31 12:49:34 UTC | Target Milestone | ga | z1 |
| Brian Rosmaita | 2023-07-27 00:14:59 UTC | Status | POST | MODIFIED |
| Fixed In Version | openstack-cinder-18.2.2-17.1.20230726051053.f6b44fc.el9osttrunk | |||
| Paul Grist | 2023-07-27 18:41:54 UTC | CC | pgrist | |
| Brian Rosmaita | 2023-07-31 21:20:46 UTC | Doc Text | Cause: In OSP 13, the ability to create a multiattach volume by passing a request parameter in the volume-create request was deprecated for removal as unsafe. The preferred method for creating a multiattach volume is to use a volume-type that enables multiattach. Consequence: Creating a multattach volume on a backend that does not provide proper multiattach support can lead to data loss. Fix: It is no longer possible to create a multiattach volume independently of using a volume-type that allows multiattach. Result: Some Block Storage API requests that were previously acceptable will be rejected with a 400 (Bad Request) response code accompanied by an informative error message. | |
| Doc Type | If docs needed, set a value | Bug Fix | ||
| Ian Frangs | 2023-08-03 15:46:23 UTC | Flags | needinfo?(rdhasman) | |
| Brian Rosmaita | 2023-08-03 21:38:17 UTC | Flags | needinfo?(rdhasman) | |
| Ian Frangs | 2023-08-08 09:21:20 UTC | CC | ifrangs | |
| Doc Text | Cause: In OSP 13, the ability to create a multiattach volume by passing a request parameter in the volume-create request was deprecated for removal as unsafe. The preferred method for creating a multiattach volume is to use a volume-type that enables multiattach. Consequence: Creating a multattach volume on a backend that does not provide proper multiattach support can lead to data loss. Fix: It is no longer possible to create a multiattach volume independently of using a volume-type that allows multiattach. Result: Some Block Storage API requests that were previously acceptable will be rejected with a 400 (Bad Request) response code accompanied by an informative error message. | Before this update, the ability to create a Block Storage multi-attach volume by passing a parameter in the volume-create request was deprecated for removal because it was unsafe and could lead to data loss when creating a multi-attach volume on a back end that does not support multi-attach volumes. With this update, you can only create a multi-attach volume by using a multi-attach volume-type. Therefore some Block Storage API requests that used to work will be rejected with a 400 (Bad Request) response code and an informative error message. | ||
| Flags | needinfo?(brian.rosmaita) | |||
| Docs Contact | astillma | ifrangs | ||
| Ian Frangs | 2023-08-08 13:08:39 UTC | Doc Type | Bug Fix | Known Issue |
| Doc Text | Before this update, the ability to create a Block Storage multi-attach volume by passing a parameter in the volume-create request was deprecated for removal because it was unsafe and could lead to data loss when creating a multi-attach volume on a back end that does not support multi-attach volumes. With this update, you can only create a multi-attach volume by using a multi-attach volume-type. Therefore some Block Storage API requests that used to work will be rejected with a 400 (Bad Request) response code and an informative error message. | The Block Storage API supports the creation of a Block Storage multi-attach volume by passing a parameter in the volume-create request, even though this method of creating multi-attach volume has been deprecated for removal because it is unsafe and can lead to data loss when creating a multi-attach volume on a back end that does not support multi-attach volumes. Workaround: create a multi-attach volume by using a multi-attach volume-type, which is the only method of creating multi-attach volumes provided by the `openstack` and `cinder` CLI. | ||
| Brian Rosmaita | 2023-08-08 14:48:32 UTC | Flags | needinfo?(brian.rosmaita) | |
| Mike Burns | 2023-08-11 13:59:33 UTC | Target Milestone | z1 | z2 |
| Mike Burns | 2023-08-11 14:56:05 UTC | Target Milestone | z2 | z1 |
| Brian Rosmaita | 2023-08-17 15:04:25 UTC | Priority | medium | high |
Back to bug 2184834