Bug 1743681

Summary:	Create host in breadcrumbs in host detail page after creating a host
Product:	Red Hat Satellite	Reporter:	Tomer Brisker <tbrisker>
Component:	Hosts	Assignee:	Tomer Brisker <tbrisker>
Status:	CLOSED ERRATA	QA Contact:	tstrych
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.4	CC:	egolov, inecas
Target Milestone:	6.6.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	foreman-1.22.0.19-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-22 19:49:03 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Tomer Brisker 2019-08-20 12:59:50 UTC

In Foreman 1.22.0-RC1 you can reproduce this by:
* Going to the Create Host form
* Fill in all the fields and submit
* See what happens

Expected result:
* The breadcrumbs are All Hosts >> $HOSTNAME

Actual result:
* The breadcrumbs are All Hosts >> Create Host | $HOSTNAME

Additional info:
* When you refresh the page, it does show the correct breadcrumb
* See attached screenshot

Comment 1 Tomer Brisker 2019-08-20 12:59:53 UTC

Created from redmine issue https://projects.theforeman.org/issues/26822

Comment 3 Tomer Brisker 2019-08-20 13:03:45 UTC

*** Bug 1743683 has been marked as a duplicate of this bug. ***

Comment 5 Bryan Kearney 2019-08-20 14:07:32 UTC

Upstream bug assigned to tbrisker

Comment 6 Bryan Kearney 2019-08-20 14:07:34 UTC

Upstream bug assigned to tbrisker

Comment 7 Bryan Kearney 2019-08-21 14:07:27 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26822 has been resolved.

Comment 11 tstrych 2019-08-26 15:43:36 UTC

I looked on error by using sat 6.6 snap 16 and after that steps were reproduced with sat 6.6 snap 17 where it works correctly. Verified

Comment 12 Bryan Kearney 2019-10-22 19:49:03 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-2019:3172