Bug 1735722

Summary: [RFE] Removing a host from satellite WebUI should remove a host from cloud.redhat.com Inventory of insights.
Product: Red Hat Satellite Reporter: Amaani S Karimi <akarimi>
Component: RH Cloud - InsightsAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Jameer Pathan <jpathan>
Severity: high Docs Contact:
Priority: high    
Version: UnspecifiedCC: ahuchcha, ahumbe, aprice, bkearney, cmarinea, dsinglet, grbrown, jangerrit.kootstra, jpathan, jsenkyri, kdixon, lphiri, mgoyal, ngupta, pcreech, peter.vreman, pmoravec, rlavi, snemeth, sshtein, wpinheir
Target Milestone: 6.14.0Keywords: FutureFeature, PrioBumpGSS, Reopened, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: foreman_rh_cloud 8.0.51 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-11-08 14:17:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 5 Pavel Moravec 2020-07-26 21:03:08 UTC
Shouldn't this be easy to implement, i.e. low hanging fruit? Either directly in code, or via foreman hooks (or its replacement)?

Comment 15 Mike McCune 2022-01-28 22:33:49 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team. Thank you.

Comment 17 Mike McCune 2022-07-08 17:15:31 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 23 ir. Jan Gerrit Kootstra 2022-07-25 05:57:21 UTC
From a Business perspective, does a registration in cloud.redhat.com count as entitlement/subscription consumption?
If so I will contact our Red Hat Account team.

Comment 30 Brad Buckingham 2022-11-03 21:48:51 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 33 ir. Jan Gerrit Kootstra 2022-11-22 15:51:04 UTC
Hi Brad,

I do not understand why in the last 5 month no has answered my question about the impact on the usage of entitlements/subscriptions and still you wish to close the ticket.
If I cannot determine the business impact, it is hard to determine the cause of action.


Regards,


Jan Gerrit Kootstra

Comment 36 Brad Buckingham 2022-12-02 17:19:53 UTC
Hi Jan,

My apologies for not replying earlier.  The message that you saw in comment 30 is part of an automated process for maintaining the Satellite backlog.  It is actually helpful in getting responses and feedback similar to your's.  Thanks!

I am updating the bugzilla to ensure that it is not included as part of the next stage of closure.  We also have confirmed that the bugzilla is being investigated/discussed with the Insights team.

To your earlier question in comment 23, the lack of reply is likely a result of the comment being missed as only folks on the CC List for the bugzilla will see it and often there is a lot of email sent from bugzilla.  For awareness, the best way to ensure responses is to use the NEEDINFO option that you see below where comment is added.

To comment 23, the feedback that I received is that that scenario should not consume subscriptions.  Only registrations via RHSM (to customer portal or Satellite) consume entitlement/subscription from the available pool.

Thanks!

Comment 37 ir. Jan Gerrit Kootstra 2022-12-03 10:27:26 UTC
Hi Brad,


Thanks for the update.

I hope this feature will someday be available, it would make automation of removal of decommissioned VMs much easier.


Regards,


Jan Gerrit

Comment 38 Marek Hulan 2022-12-09 09:53:29 UTC
We have considered few options. One was to use webhooks and upon the host deletion trigger the insights API. However it seems the best option would be the foreman_rh_cloud plugin adding a new orchestration step upon host deletion to trigger the insights API directly. The tricky part may be to detect, whether this steps should or should not be performed. This could probably be based on insights facet existence for a particular host. The API endpoint on the inventory side is DELETE on url 'https://' + server + '/api/inventory/v1/hosts/' + uuid

Comment 39 Shimon Shtein 2023-01-24 15:42:40 UTC
Note to self:

Insights profile should be removed/unregistered automatically from the console if:
- system is unregistered from RHSM.
- system is removed from the satellite server.
- system is deleted using API call.

Comment 40 Shimon Shtein 2023-01-24 15:42:55 UTC
*** Bug 1914263 has been marked as a duplicate of this bug. ***

Comment 51 errata-xmlrpc 2023-11-08 14:17:32 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Satellite 6.14 security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2023:6818