Bug 1885231 - [RFE] Hammer Control Of Red Hat Access Insights
Summary: [RFE] Hammer Control Of Red Hat Access Insights
Keywords:
Status: NEW
Alias: None
Product: Cloud Software Services (cloud.redhat.com)
Classification: Red Hat
Component: Insights - Satellite Integration
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Rex White
QA Contact: Eduardo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-05 13:32 UTC by Bernie Hoefer
Modified: 2021-06-15 11:42 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description Bernie Hoefer 2020-10-05 13:32:48 UTC
With Insights having become a large selling-point of Red Hat's portfolio, the lack of a command line interface (CLI) to control it is seen as a deficiency.  This RFE seeks a CLI interface (preferably through hammer) to administer Insights clients in relation to Satellite.

A Red Hat customer does not have sole control over their provisioned machines.  Sometimes the application teams will decommission a server without running:
  insights-client --unregister
  subscription-manager remove --all
  subscription-manager unregister
Although that procedural oversight is being corrected, the operating system team still runs scripts to check for systems that have not checked in for 30 days and unregisters them.  Although they can use the cloud.redhat.com API to remove such machines from cloud.redhat.com, there is no CLI or API way to unregister an Insights client from Satellite.

The customer believes there should be an insights sub-command to Satellite's hammer command to do this (and other Insight-related work).  At a minimum, the customer would like to see a command like "hammer insights unregister --name client.example.com".  This command would unregister the client.example.com Insights client from Satellite *and* from cloud.redhat.com.


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