Bug 1610874

Summary: "Host not found" error after deleting host
Product: Red Hat Satellite Reporter: Perry Gagne <pgagne>
Component: HostsAssignee: Adam Ruzicka <aruzicka>
Status: CLOSED ERRATA QA Contact: Perry Gagne <pgagne>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4CC: aruzicka, egolov, inecas
Target Milestone: 6.4.0Keywords: Triaged, UserExperience
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-katello-3.7.0.12-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-16 19:11:43 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:

Description Perry Gagne 2018-08-01 14:28:50 UTC
Created attachment 1472114 [details]
screen shot of error page

Description of problem: When a user deletes a provisioned host, they are directed to 


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


How reproducible: Always 


Steps to Reproduce:
1. Provision a host
2. Delete the host


Actual results: Directed to page with error message that says "host not found". See attached screen shot. 


Expected results: Probably should bring the user back to the main host page or the age they where last on 


Additional info:

Comment 4 Adam Ruzicka 2018-08-10 12:36:27 UTC
Created redmine issue https://projects.theforeman.org/issues/24584 from this bug

Comment 5 Satellite Program 2018-08-10 14:16:12 UTC
Upstream bug assigned to aruzicka

Comment 6 Satellite Program 2018-08-10 14:16:14 UTC
Upstream bug assigned to aruzicka

Comment 7 Satellite Program 2018-08-13 16:15:57 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/24584 has been resolved.

Comment 10 Bryan Kearney 2018-10-16 19:11:43 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, 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-2018:2927