Bug 2180410

Summary: View details link on DR alert card is redirecting to empty page
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: gowtham <gshanmug>
Component: management-consoleAssignee: Timothy Asir <tjeyasin>
Status: VERIFIED --- QA Contact: kmanohar
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.13CC: amagrawa, badhikar, 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:

Description gowtham 2023-03-21 12:11:23 UTC
Description of problem (please be detailed as possible and provide log
snippests):
In the alert card on the DR dashboard, For every alert, there is a href link with the name "View details". This link is redirecting to the empty page instead of any alert document.

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. Whitlist DR metrics and create alert rules:
https://docs.google.com/document/d/1pcgnZvVdD7PuvURPqEhBkbqwRoDzs4HUMxEFmMHhx2A/edit?usp=sharing

6. Adjust the alert condition to manually trigger alerts.

7. Check alerts on the DR dashboard
    All clusters -> Data services -> Data policies -> Overview -> Click 
Warning/Critical alerts on the alert card.

Actual results:
"View details" link on the alert card is redirecting to an empty page.

Expected results:
"View details" link on the alert card should redirect to some document or useful page.

Additional info:

Comment 8 Sanjal Katiyar 2023-06-02 11:42:22 UTC
RDT not needed, introduced and fixed in 4.13 itself...

Comment 12 kmanohar 2023-06-21 06:54:52 UTC
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. Whitlist DR metrics and create alert rules:
https://docs.google.com/document/d/1pcgnZvVdD7PuvURPqEhBkbqwRoDzs4HUMxEFmMHhx2A/edit?usp=sharing

6. Adjust the alert condition to manually trigger alerts.

7. Check alerts on the DR dashboard
    All clusters -> Data services -> Data policies -> Overview -> Click 
Warning/Critical alerts on the alert card.

Actual results:
"View details" link on the alert card is redirecting to an empty page.

Expected results:
"View details" link on the alert card should redirect to some document or useful page.


_______________________________________________

Verified on

ODF - 4.13.0-219
OCP - 4.13.0-0.nightly-2023-06-19-032103
ACM - 2.8
Submariner - submariner.v0.15.0

As the hyper link has been removed attached the screenshot of verification