Bug 2180448
| Summary: | Create DRPolicy action is redirecitng to DR dashbaord instead of DRPolicy list page | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Data Foundation | Reporter: | gowtham <gshanmug> |
| Component: | management-console | Assignee: | Timothy Asir <tjeyasin> |
| Status: | VERIFIED --- | QA Contact: | kmanohar |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.13 | CC: | amagrawa, kramdoss, odf-bz-bot, skatiyar, tjeyasin |
| Target Milestone: | --- | Flags: | sheggodu:
needinfo?
(tjeyasin) |
| Target Release: | ODF 4.13.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
*** Bug 2179340 has been marked as a duplicate of this bug. *** RDT not needed, introduced and fixed in 4.13 itself... VERIFICATION COMMENTS
Steps to Reproduce:
1. Configure GitOPS server
2. Create ApplicationSet type application from the ACM application page.
All clusters -> Applications -> Create application -> Application set
3. Apply DRPolicy to the application set type application on UI.
All clusters -> Data services -> Data policies -> click DRPolicy action menu(three dots button) -> Manage policy for ApplicationSets -> move application from left to right -> enter PVC selector label using expand section -> click save.
4. Enable ACM observability by following the document(you can also use ACM observability doc): https://docs.google.com/document/d/1hl9BOShVpHQKZPXmMZJes3rrQdvy3IHBHmQSfqMSJr8/edit?usp=sharing
5. Once observability is enabled, the DR dashboard is started displaying.
6. Create new DRPolicy
All clusters -> Data services -> Data policies -> Click create DRPolicy
7. Once DRPolicy is created UI will auto-redirect to the dashboard instead of the DRPolicy list page.
Actual results:
Once DRPolicy is created UI is auto re-directing to the DR dashbaord instead of the list page.
Expected results:
After the successful creation of a DRPolicy, UI should auto-redirect to the DRPolicy list page.
______________________________________
Verified on
ODF - 4.13.0-219
ACM - 2.8 GA'ed
MCO - 4.13.0-219
OCP - 4.13.0-0.nightly-2023-06-19-032103
Submariner - submariner.v0.15.0
Attached the video
|
Description of problem (please be detailed as possible and provide log snippests): Once the DRPolicy creation is finished, UI is auto-redirecting to the DR dashboard instead of the DRPolicy list page. This is happening only when ACM observability is enabled and the DR dashboard is started displaying. Version of all relevant components (if applicable): 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)? 1 Can this issue reproducible? 100% Can this issue reproduce from the UI? 100% If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. Configure GitOPS server --- # Create cluster Set in openshift-gitops namespace apiVersion: cluster.open-cluster-management.io/v1beta2 kind: ManagedClusterSet metadata: name: all-openshift-clusters spec: clusterSelector: labelSelector: matchLabels: vendor: OpenShift selectorType: LabelSelector --- # Creates a ManagedClusterSetBinding to the openshift-gitops project apiVersion: cluster.open-cluster-management.io/v1beta2 kind: ManagedClusterSetBinding metadata: name: all-openshift-clusters namespace: openshift-gitops spec: clusterSet: all-openshift-clusters --- # Create placement to choose managed clusters from cluster set apiVersion: cluster.open-cluster-management.io/v1beta1 kind: Placement metadata: name: all-openshift-clusters namespace: openshift-gitops spec: predicates: - requiredClusterSelector: labelSelector: matchExpressions: - key: vendor operator: "In" values: - OpenShift --- # Creates a gitopscluster resource # Requires: Openshift-GitOps operator be installed in the project "openshift-gitops" apiVersion: apps.open-cluster-management.io/v1beta1 kind: GitOpsCluster metadata: name: gitops-cluster-sample namespace: openshift-gitops spec: argoServer: cluster: local-cluster argoNamespace: openshift-gitops placementRef: kind: Placement apiVersion: cluster.open-cluster-management.io/v1beta1 name: all-openshift-clusters --- 2. Create ApplicationSet type application from the ACM application page. All clusters -> Applications -> Create application -> Application set 3. Apply DRPolicy to the application set type application on UI. All clusters -> Data services -> Data policies -> click DRPolicy action menu(three dots button) -> Manage policy for ApplicationSets -> move application from left to right -> enter PVC selector label using expand section -> click save. 4. Enable ACM observability by following the document(you can also use ACM observability doc): https://docs.google.com/document/d/1hl9BOShVpHQKZPXmMZJes3rrQdvy3IHBHmQSfqMSJr8/edit?usp=sharing 5. Once observability is enabled, the DR dashboard is started displaying. 6. Create new DRPolicy All clusters -> Data services -> Data policies -> Click create DRPolicy 7. Once DRPolicy is created UI will auto-redirect to the dashboard instead of the DRPolicy list page. Actual results: Once DRPolicy is created UI is auto re-directing to the DR dashbaord instead of the list page. Expected results: After the successful creation of a DRPolicy, UI should auto-redirect to the DRPolicy list page. Additional info: