Bug 2091681 - Auto replication policy type detection is not happneing on DRPolicy creation page when ceph cluster is external
Summary: Auto replication policy type detection is not happneing on DRPolicy creation ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: management-console
Version: 4.11
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ODF 4.11.0
Assignee: gowtham
QA Contact: akarsha
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-30 17:35 UTC by gowtham
Modified: 2023-08-09 16:46 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-24 13:54:12 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage odf-console pull 298 0 None open Bug 2091681: [release-4.11] Auto replication policy detection is not happening for external ceph cluster 2022-06-17 05:27:11 UTC
Github red-hat-storage odf-console pull 299 0 None open Bug 2091681: [release-4.11-compatibility] Auto replication policy detection is not happening for external ceph cluster 2022-06-17 05:28:42 UTC
Red Hat Product Errata RHSA-2022:6156 0 None None None 2022-08-24 13:54:26 UTC

Description gowtham 2022-05-30 17:35:37 UTC
Description of problem (please be detailed as possible and provide log
snippets):
On the hybrid console, the DR Policy creation page is not working as expected when the ceph cluster is external. Replication policy type auto-detection is not happening and it always asks to select the type manually using the dropdown.


Version of all relevant components (if applicable):
Hub:
  OCP         4.11.0-0.nightly-2022-05-25-193227
  ACM         2.5(pre-release)
  ODF-MCO     4.11 build '4.11.0-80

Managed Cluster:
  OCP              4.11.0-0.nightly-2022-05-25-193227
  ODF-Operator     4.11 build '4.11.0-80


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?


Is there any workaround available to the best of your knowledge?


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue be reproducible?
100%

Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1. Create one or more OCP setups with OCP 4.11.
2. Install ACM 2.5 pre-release downstream operator by following: 
    https://github.com/stolostron/deploy
3. Enable feature gate to convert OCP console to hybrid console:
    https://gist.github.com/TheRealJon/921905a74329891e1f2153a2d57aa44d#enable-the-tech-preview-feature-gate
4. Install ODF-Multicluster-Orchestrator operator of 4.11 version.
5. Enable the Plugin option while installing ODF-MCO.
6. Refresh the page.
7. Choose to "All Cluster" on the top left dropdown on the OCP console to enter into ACM view.
8. Go to Data Services -> Data Policies -> press "Create DRPolicy"
9. Select the managed cluster from the list which has an external ceph cluster.
10. Replication policy dropdown will always ask you to select the type: 
    Asynchronous / Synchronous

On Managed Clusters:
1. Create one or more OCP setups with OCP 4.11.
2. Install 4.11 ODF-Operator 
3. Create an external StorageSystem of OCS type.

Actual results:
Always ask the user to select Replication policy: Asynchronous / Synchronous

Expected results:
Once an external storage system is created on the managed cluster then, DR UI should auto-detect the Replication Policy.

Additional info:

Comment 8 akarsha 2022-08-01 10:51:21 UTC
Tested with 3 OCP clusters, say hub, c1 and c2

Version:
OCP: 4.11.0-0.nightly-2022-07-29-173905
ODF: 4.11.0-129
CEPH: 16.2.7-112.el8cp (e18db2ff03ac60c64a18f3315c032b9d5a0a3b8f) pacific (stable)
ACM: 2.5.1


Steps performed:
1. Create a MDR cluster following doc [1]
2. Create drpolicy via MCO console following doc [1]

Observation
When selecting managed clusters c1 and c2, the greyed-out dropdown option for Replication policy will automatically be selected as sync as attached screenshot here [2]
Based on observation moving to verified

[1]: https://red-hat-storage.github.io/ocs-training/training/ocs4/odf411-metro-ramen.html#_create_data_policy_on_hub_cluster
[2]: http://rhsqe-repo.lab.eng.blr.redhat.com/OCS/ocs-qe-bugs/bz2091681/dr_policy_sync_mode.png

Comment 10 errata-xmlrpc 2022-08-24 13:54:12 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Red Hat OpenShift Data Foundation 4.11.0 security, enhancement, & bugfix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:6156


Note You need to log in before you can comment on or make changes to this bug.