Bug 234647 – innacurate message if no systems exist

This service will be undergoing maintenance at 00:00 UTC, 2016-09-28. It is expected to last about 1 hours

Bug 234647 - innacurate message if no systems exist

Summary:	innacurate message if no systems exist

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Satellite 5
Classification:	Red Hat
Component:	WebUI (Show other bugs)
Sub Component:
Version:	500
Hardware:	All Linux

Priority	low Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Miroslav Suchý
QA Contact:	Red Hat Satellite QA List
Docs Contact:

URL:	https://rhn.redhat.com/
Whiteboard:
Keywords:

Depends On:
Blocks:	462714
	Show dependency tree / graph

Reported:	2007-03-30 15:18 EDT by Wes
Modified:	2011-09-16 10:41 EDT (History)
CC List:	3 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2011-09-16 10:41:00 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Wes 2007-03-30 15:18:49 EDT

Description of problem:
on the landing page in the inactive systems box it says (even if no systems are
active or exist):

All of your systems are actively checking into RHN at this time. You can view a
list of all of your systems at Systems > All.

... this is not exactly accurate, i have no systems, how can they be activly
checking into RHN? 


How reproducible:
Login to an account with no systems attached tot he account

Comment 2 Miroslav Suchý 2011-09-16 10:41:00 EDT

I see this as NOTABUG. Empty set is also set. So if everything is true for some set, even if it is empty set.... :)

Well and without that text it looks soo empty. All that apply not even for inactive system box, but also errata, schedled actions, recently registred system.

So I would rather leave it there.

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