Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1018239 - [RFE] need to have some sort of node status available from CLI
Summary: [RFE] need to have some sort of node status available from CLI
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Foreman Proxy
Version: 6.0.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-11 14:20 UTC by Corey Welton
Modified: 2017-08-10 20:19 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-10 20:19:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 19510 0 Normal New Hammer should provide information about proxy status 2020-01-15 13:08:32 UTC

Description Corey Welton 2013-10-11 14:20:16 UTC
Description of problem:
There's no reason we shouldn't do some sort of periodic ping checks and/or other diagnostics to get (and be able to provide) status of child nodes.

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


How reproducible:


Steps to Reproduce:
1.  Set up a node on parent side but don't do requisite work on child side  
2.  katello --user admin --password admin node list
3.  view results.

Actual results:
We know the node exists from this query, but we know nothing about it.

Expected results:
We should be able to do at least one of a couple of things:
* have a "Status" column for the results in 'katello --user admin --password admin node list'
* be able to have a more robust query, i.e., 'katello --user admin --password admin node status --id 1'


Additional info:
Status could be any of "Responding, Unresponsive, Syncing" etc etc etc.

Comment 6 Bryan Kearney 2017-08-10 20:19:11 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.


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