Shouldn't this be easy to implement, i.e. low hanging fruit? Either directly in code, or via foreman hooks (or its replacement)?
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.
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.
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
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!
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
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
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.
*** Bug 1914263 has been marked as a duplicate of this bug. ***