Bug 1709270

Summary:	Inventory - Missing delete server
Product:	Red Hat Hybrid Cloud Console (console.redhat.com)	Reporter:	Peter Vreman <peter.vreman>
Component:	Inventory	Assignee:	dhorton
Status:	CLOSED DUPLICATE	QA Contact:	Brandon Tweed <btweed>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	ihands, lphiri, robwilli
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-05-13 13:01:28 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:
Bug Depends On:
Bug Blocks:	1122832

Description Peter Vreman 2019-05-13 10:11:23 UTC

Description of problem:
I am unable to delete decommissioned servers from the UI.

In the old Insights my use case was to select 'Stale' servers and then Select All (optionally uncheck a few i still want to keep) and then click Remove Action.

This is a mandatory action to make the Rules hit show a realistic overview, because normally the decommissioned servers have more hits due to not being updated with the latest errata and config.

Note that i cannot logon to the servers anymore to type 'unregister' because they are already shutdown, because that is also how i see them as Stale.


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


How reproducible:


Steps to Reproduce:
1. Goto Inventory
2. Select Stale filter
3. Select All on listed Stale servers
4. Click action Delete

Actual results:
Step 2-4 are not available

Expected results:
USe case as worked with the old Insights portal works again to do housekeeping


Additional info:

Comment 1 Rob Williams 2019-05-13 13:01:28 UTC

Hey Peter,
This is a known gap we're looking to address. There is another BZ filed which we're tracking reporters of this issue under one bug. I'm going to mark this one as a duplicate of 1707950 to track.

*** This bug has been marked as a duplicate of bug 1707950 ***