Bug 886961 – Information about data not available in case cumin without plumage

Bug 886961 - Information about data not available in case cumin without plumage

Summary:	Information about data not available in case cumin without plumage

Status:	CLOSED WONTFIX

Aliases:	None

Product:	Red Hat Enterprise MRG
Classification:	Red Hat
Component:	cumin (Show other bugs)
Sub Component:
Version:	Development
Hardware:	Unspecified Unspecified

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	grid-maint-list
QA Contact:	MRG Quality Engineering
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2012-12-13 11:56 EST by Stanislav Graf
Modified:	2016-05-26 15:54 EDT (History)
CC List:	2 users (show)

See Also:	807838 789351 903150
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2016-05-26 15:54:51 EDT
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)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Stanislav Graf 2012-12-13 11:56:19 EST

Description of problem:
Display information about data not available in case cumin without plumage.

For example:
Grid - Overview - History
It is confusing on RHEL5 because Bug 807838 is unique‑mrg‑rhel‑6‑bug+

Or on RHEL6 machine without plumage.

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

How reproducible:
100%

Steps to Reproduce:
1. Grid - Overview - History
2. Grid - Overview - Slot capacity

Actual results:
History RFE is not available on RHEL5 but charts is there - empty.

Expected results:
Remove 'History' button or display 'data not available' instead of empty charts.

Additional info:

Comment 1 Anne-Louise Tangring 2016-05-26 15:54:51 EDT

MRG-Grid is in maintenance and only customer escalations will be considered. This issue can be reopened if a customer escalation associated with it occurs.

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