Bug 1836755

Summary: Duration time can't be displayed on mobile browser
Product: OpenShift Container Platform Reporter: Junqi Zhao <juzhao>
Component: Management ConsoleAssignee: Robb Hamilton <rhamilto>
Status: CLOSED ERRATA QA Contact: Junqi Zhao <juzhao>
Severity: low Docs Contact:
Priority: low    
Version: 4.5CC: aos-bugs, hasha, jokerman, rhamilto
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:39:31 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
Duration time can't be displayed on mobile browser none

Description Junqi Zhao 2020-05-18 04:11:07 UTC
Created attachment 1689508 [details]
Duration time can't be displayed on mobile browser

Description of problem:
mobile browser, silent alert, there is not default duration time in the Silence Alert page, see the attached picture, no default value for "For" field
Even set the duration time, it can't be displayed either

Version-Release number of selected component (if applicable):
4.5.0-0.nightly-2020-05-17-201019
Chrome 81.0.4044.117
Android 8.1.0

How reproducible:
always

Steps to Reproduce:
1. silent alert with mobile browser
2.
3.

Actual results:
No default duration time in the Silence Alert page with mobile browser
Duration time can't be displayed

Expected results:
default time is 2h

Additional info:

Comment 4 shahan 2020-05-19 05:03:53 UTC
console can set the default duration time for " For " and user can update it well
The whole layout on mobile were improved
4.5.0-0.ci-2020-05-19-043243

Comment 5 errata-xmlrpc 2020-07-13 17:39:31 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, 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/RHBA-2020:2409