Bug 1696737

Summary: upgrade dialog not expanding to show versions dropdown
Product: OpenShift Container Platform Reporter: Timothy Rees <trees>
Component: Management ConsoleAssignee: Robb Hamilton <rhamilto>
Status: CLOSED CURRENTRELEASE QA Contact: Yadan Pei <yapei>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.1.0CC: aos-bugs, jokerman, mmccomas, rhamilto, spadgett, vlaad, yapei
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-23 13:33:16 UTC 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:
Attachments:
Description Flags
upgrade dialog box
none
VersionDropdown none

Description Timothy Rees 2019-04-05 14:23:37 UTC 
Created attachment 1552524 [details]
upgrade dialog box

Description of problem:

OCP 4.1 Beta3 web console upgrade cluster dialog box does not resize showing the available versions to upgrade in the dropdown.

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

Beta 3 drop (4.0.0-0.9) release 0.16.1 , accessing console with Chrome Version 73.0.3683.86 (Official Build) (64-bit) on Fedora, the same issue exists with FireFox 66.0.1 (64-bit).

How reproducible:

100%

Steps to Reproduce:
1. Deploy openshift 4.1, login to web console
2. Nav to cluster settings (ie https://console-openshift-console.apps.trees-cluster.trees.rhcee.support/settings/cluster)
3. Click updates available and then the dropdown to select cluster version

Actual results:

Drop down does no expand the dialog box and selectable cluster versions are hidden from view. (see attachment)

Expected results:

Dialog box resizes to show scrollable content in the dropdown.

Additional info:
Comment 2 Robb Hamilton 2019-08-13 19:29:46 UTC 
This was fixed with https://github.com/openshift/console/pull/1416 and did *not* ship with 4.1.
Comment 4 Robb Hamilton 2019-08-14 13:40:33 UTC 
No doc update needed as this bug was not released.
Comment 5 Yadan Pei 2019-08-16 06:35:04 UTC 
Hi Robb,

I can't reproduce the issue on 4.1.0-0.nightly-2019-08-13-091918


I saw PR 1416 was merged to master branch at Apr 11, is it master branch == 4.1 at that time?
Comment 6 Yadan Pei 2019-08-16 06:35:28 UTC 
Created attachment 1604292 [details]
VersionDropdown
Comment 7 Yadan Pei 2019-08-16 08:08:06 UTC 
The screenshot in PR 1416 looks like a 4.2 cluster because there are Taint & Toleration & Network Policy Setting when create projects.
Comment 8 Samuel Padgett 2019-08-16 13:34:51 UTC 
Taints and tolerations as well as network policy settings were both in 4.1. I've confirmed commit 89dba6c78f35daa2b74f1ea3dfb37998fbd31fdd was in 4.1.0.
Comment 10 Yadan Pei 2019-08-19 03:16:13 UTC 
Moving to VERIFIED the issues reported no longer exists in 4.1.0-0.nightly-2019-08-14-043700
Comment 13 Samuel Padgett 2019-08-23 13:33:16 UTC 
This bug was never in a shipped release.