Bug 1953520

Summary:	[OCP v48] Unreachable url shows in links section of Compliance Operator over GUI
Product:	OpenShift Container Platform	Reporter:	Jakub Hrozek <jhrozek>
Component:	Compliance Operator	Assignee:	Jakub Hrozek <jhrozek>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Prashant Dhamdhere <pdhamdhe>
Severity:	low	Docs Contact:
Priority:	low
Version:	4.6.z	CC:	josorior, mrogers, pdhamdhe, xiyuan
Target Milestone:	---
Target Release:	4.6.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1953517	Environment:
Last Closed:	2021-09-08 15:43:04 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1946512, 1953517
Bug Blocks:

Description Jakub Hrozek 2021-04-26 10:08:37 UTC

+++ This bug was initially created as a clone of Bug #1953517 +++

+++ This bug was initially created as a clone of Bug #1946512 +++

Description of problem:

Unreachable url shows in links section of Compliance Operator over GUI


Version-Release number of selected component (if applicable):

4.8.0-0.nightly-2021-04-03-092337 + compliance-operator.v0.1.29


How reproducible:

Always

Steps to Reproduce:

1. Install Compliance Operator through Web Console
2. After installation of operator click on Compliance Operator -> Operator Details
3. In Links section, unreachable url will get find https://compliance-operator.domain/

Actual results:
 
The mentioned url should be reachable or it should point to product page or documentation


Expected results:

Unreachable url shows in links section of Compliance Operator over GUI

Additional info:

--- Additional comment from Matt Rogers on 2021-04-09 16:30:14 UTC ---


Fixed upstream: https://github.com/openshift/compliance-operator/pull/614

Comment 3 Prashant Dhamdhere 2021-04-27 10:37:08 UTC

Hi Jakub,

The Compliance Operator documentation link should point to 4.6 instead of 4.7 on OCP 4.6 cluster.

$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.6.0-0.nightly-2021-04-23-181645   True        False         132m    Cluster version is 4.6.0-0.nightly-2021-04-23-181645


$ oc get csv compliance-operator.v0.1.31 -o yaml |grep -A9 "Compliance Operator documentation"
  - name: Compliance Operator documentation
    url: https://docs.openshift.com/container-platform/4.7/security/compliance_operator/compliance-operator-understanding.html  <<-----
  maintainers:
  - email: support
    name: Red Hat Support
  maturity: alpha
  provider:
    name: Red Hat Inc.
    url: www.redhat.com
  version: 0.1.31

Comment 4 Jakub Hrozek 2021-04-27 11:39:52 UTC

Honestly I'm not sure if it's much of a problem. All OCP versions ship the same version of the operator, so the contents will be the same for all OCP versions.

What is it exactly you're concerned about, that the users wouldn't like seeing 4.7 in the URL or that the contents might diverge?

Comment 5 Prashant Dhamdhere 2021-04-27 12:57:38 UTC

Yes, the contents will be the same for all OCP versions as we are shipping the same version of the operator.
But, I am concerned about the version in URL which users wouldn't like see 4.7 on OCP 4.6 cluster console.

Comment 6 Jakub Hrozek 2021-05-03 14:11:34 UTC

(In reply to Prashant Dhamdhere from comment #5)
> Yes, the contents will be the same for all OCP versions as we are shipping
> the same version of the operator.
> But, I am concerned about the version in URL which users wouldn't like see
> 4.7 on OCP 4.6 cluster console.

Since we are always backporting the latest changes and as I confirmed with Ashley, the docs are also always backported, I think we could as well use /latest/ to avoid any version numbering confusion.

Comment 11 Jakub Hrozek 2021-09-08 15:43:04 UTC

This was addressed in https://errata.devel.redhat.com/advisory/79439