Back to bug 1881523

Who When What Removed Added
Yaniv Kaul 2020-09-22 15:28:04 UTC Flags needinfo?(vashastr)
Vasishta 2020-09-22 15:31:20 UTC Keywords Regression
Flags needinfo?(vashastr)
Vasishta 2020-09-22 15:33:34 UTC Keywords UpgradeBlocker
Vasishta 2020-09-22 15:34:02 UTC Target Milestone rc z2
Vasishta 2020-09-22 15:41:21 UTC CC gabrioux
Flags needinfo?(gabrioux)
Vasishta 2020-09-22 15:41:42 UTC Flags needinfo?(aschoen)
Vasishta 2020-09-22 15:42:16 UTC CC dsavinea
Flags needinfo?(dsavinea)
Yaniv Kaul 2020-09-22 15:56:21 UTC Flags needinfo?(vashastr)
Guillaume Abrioux 2020-09-22 19:35:02 UTC Flags needinfo?(gabrioux)
Vasishta 2020-09-23 10:02:14 UTC Keywords Regression, UpgradeBlocker
Flags needinfo?(vashastr)
Vasishta 2020-09-23 10:07:19 UTC Target Release 4.1 4.2
Target Milestone z2 rc
Doc Type If docs needed, set a value Known Issue
Guillaume Abrioux 2020-09-23 14:27:17 UTC Status NEW ASSIGNED
Target Release 4.2 4.3
Flags needinfo?(aschoen) needinfo?(dsavinea)
Guillaume Abrioux 2020-09-23 14:31:24 UTC Link ID Github ceph/ceph-ansible/pull/5821
Amrita 2020-09-29 09:15:54 UTC CC asakthiv
Flags needinfo?(gabrioux)
Amrita 2020-09-29 09:26:32 UTC Docs Contact asakthiv
Guillaume Abrioux 2020-09-29 13:13:56 UTC Doc Text Cause: the filestore-to-bluestore playbook doesn't support the `osd_auto_discovery` scenario

Consequence: RHCS deployments based on the `osd_auto_discovery` scenario can't use the filestore-to-bluestore playbook in order to ease the bluestore migration.
Anjana Suparna Sriram 2020-09-29 13:50:00 UTC CC asriram
Blocks 1816167
Guillaume Abrioux 2020-09-29 14:52:54 UTC Status ASSIGNED POST
Amrita 2020-09-29 15:39:24 UTC Doc Text Cause: the filestore-to-bluestore playbook doesn't support the `osd_auto_discovery` scenario

Consequence: RHCS deployments based on the `osd_auto_discovery` scenario can't use the filestore-to-bluestore playbook in order to ease the bluestore migration.
.The `filestore-to-bluestore` playbook does not support the
`osd_auto_discovery` scenario

{storage-product} 4 deployments based on `osd_auto_recovery` scenario can't use the `filestore-to-bluestore` playbook to ease the `BlueStore` migration.
Flags needinfo?(gabrioux)
Guillaume Abrioux 2020-09-29 15:53:23 UTC Flags needinfo?(gabrioux) needinfo?(gabrioux)
Amrita 2020-09-29 19:33:13 UTC Doc Text .The `filestore-to-bluestore` playbook does not support the
`osd_auto_discovery` scenario

{storage-product} 4 deployments based on `osd_auto_recovery` scenario can't use the `filestore-to-bluestore` playbook to ease the `BlueStore` migration.
.The `filestore-to-bluestore` playbook does not support the`osd_auto_discovery` scenario

{storage-product} 4 deployments based on `osd_auto_recovery` scenario can't use the `filestore-to-bluestore` playbook to ease the `BlueStore` migration.
Guillaume Abrioux 2020-09-30 06:13:59 UTC Doc Text .The `filestore-to-bluestore` playbook does not support the`osd_auto_discovery` scenario

{storage-product} 4 deployments based on `osd_auto_recovery` scenario can't use the `filestore-to-bluestore` playbook to ease the `BlueStore` migration.
.The `filestore-to-bluestore` playbook does not support the`osd_auto_discovery` scenario

{storage-product} 4 deployments based on `osd_auto_recovery` scenario can't use the `filestore-to-bluestore` playbook to ease the `BlueStore` migration.

Workaround is to use shrink-osd playbook and redeploy the shrinked OSD with `osd_objectstore: bluestore`
Flags needinfo?(asakthiv)
Amrita 2020-09-30 06:50:10 UTC Doc Text .The `filestore-to-bluestore` playbook does not support the`osd_auto_discovery` scenario

{storage-product} 4 deployments based on `osd_auto_recovery` scenario can't use the `filestore-to-bluestore` playbook to ease the `BlueStore` migration.

Workaround is to use shrink-osd playbook and redeploy the shrinked OSD with `osd_objectstore: bluestore`
.The `filestore-to-bluestore` playbook does not support the`osd_auto_discovery` scenario

{storage-product} 4 deployments based on `osd_auto_recovery` scenario can't use the `filestore-to-bluestore` playbook to ease the `BlueStore` migration.

The workaround is to use `shrink-osd` playbook and redeploy the shrinked OSD with `osd_objectstore: bluestore`
Flags needinfo?(asakthiv)
Amrita 2020-09-30 06:52:16 UTC Doc Text .The `filestore-to-bluestore` playbook does not support the`osd_auto_discovery` scenario

{storage-product} 4 deployments based on `osd_auto_recovery` scenario can't use the `filestore-to-bluestore` playbook to ease the `BlueStore` migration.

The workaround is to use `shrink-osd` playbook and redeploy the shrinked OSD with `osd_objectstore: bluestore`
.The `filestore-to-bluestore` playbook does not support the`osd_auto_discovery` scenario

{storage-product} 4 deployments based on `osd_auto_recovery` scenario can't use the `filestore-to-bluestore` playbook to ease the `BlueStore` migration.

The workaround is to use `shrink-osd` playbook and redeploy the shrinked OSD with `osd_objectstore: bluestore`.
Amrita 2020-09-30 06:54:32 UTC Doc Text .The `filestore-to-bluestore` playbook does not support the`osd_auto_discovery` scenario

{storage-product} 4 deployments based on `osd_auto_recovery` scenario can't use the `filestore-to-bluestore` playbook to ease the `BlueStore` migration.

The workaround is to use `shrink-osd` playbook and redeploy the shrinked OSD with `osd_objectstore: bluestore`.
.The `filestore-to-bluestore` playbook does not support the`osd_auto_discovery` scenario

{storage-product} 4 deployments based on `osd_auto_recovery` scenario can't use the `filestore-to-bluestore` playbook to ease the `BlueStore` migration.

To work around this issue, use `shrink-osd` playbook and redeploy the shrinked OSD with `osd_objectstore: bluestore`.
Guillaume Abrioux 2020-10-01 14:54:10 UTC Target Release 4.3 4.2
Target Milestone rc z1
Drew Harris 2020-11-09 16:53:32 UTC Target Release 4.2 4.2z1
Target Milestone z1 ---
Guillaume Abrioux 2020-11-12 16:12:53 UTC Target Release 4.2z1 4.2
Veera Raghava Reddy 2020-11-25 14:48:01 UTC CC vereddy
errata-xmlrpc 2020-11-25 18:24:52 UTC Status POST MODIFIED
CC tserlin
Fixed In Version ceph-ansible-4.0.38-1.el8cp, ceph-ansible-4.0.38-1.el7cp
Status MODIFIED ON_QA
Amrita 2020-12-03 08:23:21 UTC Blocks 1890121
Ameena Suhani S H 2020-12-09 20:14:33 UTC Status ON_QA VERIFIED
errata-xmlrpc 2021-01-12 11:51:55 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2021-01-12 14:57:21 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2021-01-12 14:57:21 UTC
errata-xmlrpc 2021-01-12 14:57:43 UTC Link ID Red Hat Product Errata RHSA-2021:0081
Amrita 2021-06-04 11:46:09 UTC Blocks 1890121
Aron Gunn 2021-06-09 16:16:59 UTC Blocks 1890121

Back to bug 1881523