Bug 2083149 - "Update blocked" label incorrectly displays on new minor versions in the "Other available paths" modal
Summary: "Update blocked" label incorrectly displays on new minor versions in the "Oth...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.11
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.11.0
Assignee: Robb Hamilton
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks: 2083385
TreeView+ depends on / blocked
 
Reported: 2022-05-09 13:01 UTC by Robb Hamilton
Modified: 2022-08-10 11:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-10 11:10:43 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Screenshot of bug (120.26 KB, image/png)
2022-05-09 13:01 UTC, Robb Hamilton 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 11459 0 None open Bug 2083149: fix bug where "Update blocked" label incorrectly displa… 2022-05-09 13:21:08 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 11:10:59 UTC

Description Robb Hamilton 2022-05-09 13:01:48 UTC 
Created attachment 1878088 [details]
Screenshot of bug

Description of problem:  https://github.com/openshift/console/blob/d33daabd7755d28627f09cc5b6e64ff4d3362e4a/frontend/public/components/modals/cluster-more-updates-modal.tsx#L51 does not include a `!!getConditionUpgradeableFalse(cv)` but should.  As a result, the `Update blocked` badge is incorrectly displaying for any version that is newer than the current minor version.


How reproducible:  Always


Steps to Reproduce:
1. Visit /settings/cluster using a 4.9.31 cluster
2. Click `+More`
3. Note the 4.10.12 listing incorrectly has a `Update blocked` label beside t
Comment 1 Robb Hamilton 2022-05-09 13:10:44 UTC 
Amend step 1 above:  Visit /settings/cluster using a 4.9.31 cluster with channel set to `candidate-4.10`
Comment 3 Yadan Pei 2022-05-11 05:53:33 UTC 
Hi Robb,

Shall we backport the fix to +4.9 versions?
Comment 4 Yadan Pei 2022-05-11 06:24:23 UTC 
1. setup a 4.9.31 cluster
2. update upgrade channel set to `candidate-4.10`
2. Click `+More`
3. Note that 4.10.12 listing doesn't have 'Updated blocked' label

verified on latest master
Comment 5 Robb Hamilton 2022-05-11 11:34:46 UTC 
Yes, this should be back ported to 4.9.  I've started that process.  See https://github.com/openshift/console/pull/11466 and https://github.com/openshift/console/pull/11466#issuecomment-1122266748.
Comment 7 errata-xmlrpc 2022-08-10 11:10:43 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:5069
Note You need to log in before you can comment on or make changes to this bug.