-
Bug
-
Resolution: Done-Errata
-
Undefined
-
odf-4.18
-
None
Description of problem - Provide a detailed description of the issue encountered, including logs/command-output snippets and screenshots if the issue is observed in the UI:
ODF for FlashSystem version 1.7.0 shall be used by ODF 4.18, for use on OCP 4.18. ODF for FlashSystem v1.7.0 is NOT GA'D YET, but once available, it should be used by ODF for fully qualified behavior.
The relevant PR to merge - https://github.com/red-hat-storage/odf-operator/pull/517
Once this ticket is completed, the documentation note introduced in DFBUGS-1676 can be removed and DFBUGS-198 can be fully tested and verified (not just by CR)
The OCP platform infrastructure and deployment type (AWS, Bare Metal, VMware, etc. Please clarify if it is platform agnostic deployment), (IPI/UPI):
Agnostic
The ODF deployment type (Internal, External, Internal-Attached (LSO), Multicluster, DR, Provider, etc):
External (ODF for IBM FlashSystem)
The version of all relevant components (OCP, ODF, RHCS, ACM whichever is applicable):
OCP - 4.18
ODF - 4.18
ODF for IBM Flash - 1.7.0
Does this issue impact your ability to continue to work with the product?
Yes, without merging ODF for IBM FlashSystem 1.7.0 into ODF 4.18, the ODF for FlashSystem cannot be used on the OCP 4.18 platform.
Is there any workaround available to the best of your knowledge?
No, customer must not updated to OCP 4.18 if they wish to continue using a qualified ODF for IBM FlashSystem release.
Can this issue be reproduced? If so, please provide the hit rate
Until the new version is merged, all attempts to use ODF for IBM FlashSystem with ODF 4.18 on OCP 4.18 will run a non-qualified version.
Can this issue be reproduced from the UI?
Yes
If this is a regression, please provide more details to justify this:
No
Steps to Reproduce:
1. Create a new storage system
2. Select external -> IBM FlashSystem
The exact date and time when the issue was observed, including timezone details:
ODF 4.18 day-1
Actual results:
Until the new version is merged, all attempts to use ODF for IBM FlashSystem with ODF 4.18 on OCP 4.18 will run a non-qualified version.
Expected results:
Use ODF for IBM FlashSystem 1.7.0 with ODF 4.18 for fully qualified behavior on OCP 4.18
Logs collected and log location:
N/A
Additional info:
N/A
- is cloned by
-
DFBUGS-1918 Need to merge new version of ODF for IBM FlashSystem to 4.17
-
- Closed
-
-
DFBUGS-1919 Need to merge new version of ODF for IBM FlashSystem to 4.16
-
- Closed
-
-
DFBUGS-1920 Need to merge new version of ODF for IBM FlashSystem to 4.15
-
- Closed
-
-
DFBUGS-2486 Need to merge new version 1.7.1 of ODF for IBM FlashSystem to 4.18
-
- Closed
-
- is related to
-
DFBUGS-198 [2294843] [RFE] Deploying ODF for external IBM FlashSystem storage using thick volumes that do not format as thin volumes causes warnings/errors on the Flashsystem side with storage calculations which disables the pool from creating new volumes
-
- Closed
-
-
DFBUGS-1676 Need note that ODF for IBM FlashSystem is not supported yet in 4.18
-
- Closed
-
- links to
-
RHBA-2025:148869 Red Hat OpenShift Data Foundation 4.18.3 Bug Fix Update