Bug 471501 - Scheduler "Server" should give FQHN of schedd node
Summary: Scheduler "Server" should give FQHN of schedd node
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: cumin
Version: 1.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: 1.3
: ---
Assignee: messaging-bugs
QA Contact: Jan Sarenik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-11-14 00:47 UTC by William Henry
Modified: 2010-10-20 11:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-10-20 11:30:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Current Scheduler screen (30.08 KB, image/png)
2010-09-15 20:46 UTC, Matthew Farrellee 		no flags Details
View All

Description William Henry 2008-11-14 00:47:50 UTC 
Description of problem:

When you Select the Scheduler tab under Grid the list gives the name of the schedd daemon but doesn't give the name of the Server it is on. Perhaps server is supposed to be something else?? If it's supposed to be the machine that the scheed is on the the fully qualified host name should be listed. Currently it says "None".

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Matthew Farrellee 2008-11-14 01:47:54 UTC 
This data is currently available as via the System reference or the Machine property
Comment 2 William Henry 2008-11-14 03:16:27 UTC 
And should also be here - otherwise remove the column if it's just going to say None
Comment 3 Matthew Farrellee 2010-09-15 20:46:26 UTC 
This appears resolved in cumin-0.1.4279-1.el5.noarch

Please reopen if not.
Comment 4 Matthew Farrellee 2010-09-15 20:46:55 UTC 
Created attachment 447570 [details]
Current Scheduler screen
Comment 5 Jan Sarenik 2010-09-23 12:11:15 UTC 
Verified in cumin-0.1.4332-1.el5
Note You need to log in before you can comment on or make changes to this bug.