Bug 2321386

Description of problem:
On a RDR setup, when the following odf-cli cmd is run on the managed clusters using peer cluster name after installing submariner where globalnet is not enabled and both the managed clusters are on the same service network, meaning globalnet has to be enabled, the output currently shows it like a info.

odf get dr-prereq amagrawa-23o-c2
Info: Submariner is installed.
Info: Globalnet is required.
Info: Globalnet is not enabled.

odf get dr-prereq amagrawa-23o-c1
Info: Submariner is installed.
Info: Globalnet is required.
Info: Globalnet is not enabled.



amagrawa-23o-c2 ==>

oc get networks.config.openshift.io cluster -o json | jq .spec
{
  "clusterNetwork": [
    {
      "cidr": "10.128.0.0/14",
      "hostPrefix": 23
    }
  ],
  "externalIP": {
    "policy": {}
  },
  "networkDiagnostics": {
    "mode": "",
    "sourcePlacement": {},
    "targetPlacement": {}
  },
  "networkType": "OVNKubernetes",
  "serviceNetwork": [
    "172.30.0.0/16"
  ]
}


amagrawa-23o-c1 ==>

oc get networks.config.openshift.io cluster -o json | jq .spec
{
  "clusterNetwork": [
    {
      "cidr": "10.128.0.0/14",
      "hostPrefix": 23
    }
  ],
  "externalIP": {
    "policy": {}
  },
  "networkDiagnostics": {
    "mode": "",
    "sourcePlacement": {},
    "targetPlacement": {}
  },
  "networkType": "OVNKubernetes",
  "serviceNetwork": [
    "172.30.0.0/16"
  ]
}
Version-Release number of selected component (if applicable):

ODF CLI 4.17


How reproducible:


Steps to Reproduce:
1. On a RDR setup, install ACM and submariner without globalet when both the ODF clusters are on the same service network and run odf-cli cmd as mentioned above.
2.
3.

Actual results: [RDR] When globalnet is needed but it's not enabled, output shows this as a info


Expected results: [RDR] When globalnet is needed but it's not enabled, this should be highlighted to the cluster admin in the form of a warning/error message instead of info.


Additional info: