Bug 1449819 - Calendar control on Azure Availability zone Utilization page gets clipped
Summary: Calendar control on Azure Availability zone Utilization page gets clipped
Keywords:
Status: CLOSED DUPLICATE of bug 1450463
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: cfme-future
Assignee: Eric Winchell
QA Contact: Nandini Chandra
URL:
Whiteboard: ui:c&u
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-10 19:39 UTC by Nandini Chandra
Modified: 2017-05-19 22:37 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-16 19:24:22 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
screen shot of Azure Availability zone Utilization page (123.35 KB, image/png)
2017-05-12 16:16 UTC, Nandini Chandra 		no flags Details
View All

Description Nandini Chandra 2017-05-10 19:39:40 UTC 
Description of problem:
----------------------
The Calendar control on the Utilization page of Azure Availability zones  gets clipped.See attached screen shot.

This issue is not seen on the Utilization page of Azure instances.


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


How reproducible:
----------------
Always


Steps to Reproduce:
-------------------
1.Navigate to the summary page of an Availability zone.
2.Click 'Monitoring', click 'Utilization'.


Actual results:
---------------
Calendar control on Azure Availability zone Utilization page gets clipped


Expected results:
-----------------
Calendar control shouldn't get clipped.


Additional info:
----------------
Comment 3 Nandini Chandra 2017-05-12 16:16:31 UTC 
Created attachment 1278275 [details]
screen shot of Azure Availability zone Utilization page
Comment 4 Eric Winchell 2017-05-16 19:24:22 UTC 

*** This bug has been marked as a duplicate of bug 1450463 ***
Note You need to log in before you can comment on or make changes to this bug.