This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 1478846 - Does not display time scale on pod metrics page in iPhone vertical screen
Does not display time scale on pod metrics page in iPhone vertical screen
Status: NEW
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console (Show other bugs)
3.6.0
Unspecified Unspecified
medium Severity low
: ---
: ---
Assigned To: Samuel Padgett
XiaochuanWang
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-08-07 06:03 EDT by xipang
Modified: 2017-08-07 07:52 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
no show time sacle (23.91 KB, image/png)
2017-08-07 06:03 EDT, xipang
no flags Details

  None (edit)
Description xipang 2017-08-07 06:03:41 EDT
Created attachment 1309982 [details]
no show time sacle

Description of problem:
Metrics chart didn't display time scale on pod metrics page in iPhone vertical screen
When iPhone screen is put horizontally , no this problem

Version-Release number of selected component (if applicable):
OpenShift Master:   v3.6.173.0.5 (online version 3.5.0.20)
Kubernetes Master:  v1.6.1+5115d708d7 

How reproducible:
Always

Steps to Reproduce:
1.Login to web console and create a project
2.Create a application(e.g.Ruby)
3.Check chart time scale on pod metrics page

Actual results:
3.Metrics chart didn't display time scale

Expected results:
3.Time scale is displayed

Additional info:
Comment 1 Samuel Padgett 2017-08-07 07:52:25 EDT
This is intentional because the numbers run together and overlap at this screen width. We can investigate if there's a better solution, however.

Note You need to log in before you can comment on or make changes to this bug.