Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1743680

Summary: after creating a new host, the UI for the newly created host disappear
Product: Red Hat Satellite Reporter: Tomer Brisker <tbrisker>
Component: HostsAssignee: Amir <afeferku>
Status: CLOSED ERRATA QA Contact: tstrych
Severity: medium Docs Contact:
Priority: unspecified    
Version: NightlyCC: afeferku, egolov, inecas
Target Milestone: 6.6.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: foreman-1.22.0.20-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-22 19:51:52 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:57:47 UTC
this seems like a regression from #26122

steps to reproduce:

1. create a new host with an error in the form
2. fix error and submit form
3. notice progress bar
4. main content div is hidden

the host is created successfully.

Comment 1 Tomer Brisker 2019-08-20 12:57:50 UTC
Created from redmine issue https://projects.theforeman.org/issues/26655

Comment 2 Tomer Brisker 2019-08-20 12:57:53 UTC
Upstream bug assigned to afeferku

Comment 5 Bryan Kearney 2019-08-25 18:04:31 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26655 has been resolved.

Comment 7 tstrych 2019-09-09 12:02:31 UTC
Hi, can you please give me more info about steps to reproduce, what should disappear? Screenshot can be really helpful and also snap number when it doesn't work.
Because I tried to create host in snap 16 and also snap 18 and I do not know where should I look.
And do I need to create real machine via libvirt (for example) or is it enough to create (fake) host only in UI.

Comment 8 Tomer Brisker 2019-09-09 12:13:50 UTC
The issue was reproducible when orchestration failed and triggered a toast notification. I have been successful in reproducing by trying to provision libvirt with an ip that was already reserved in dhcp, but that requires working dhcp setup. I think Amir was able to find a simpler reproducer, but that may have involved code changes - passing on the needinfo.

Comment 10 tstrych 2019-09-10 16:03:35 UTC
I used steps to reproduce which Amir wrote to me into private comment, 
I was able to reproduce the this bug on snap 16. 
After I did found the problem I reproduce it on snap 18 with the same steps.
In snap 18 I was able to see main content div. 
Verified.

Comment 11 Bryan Kearney 2019-10-22 19:51:52 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