+++ 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
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
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?
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.
(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.
This was addressed in https://errata.devel.redhat.com/advisory/79439