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.

Description of problem:

- Submitting the changes after modifying the Interfaces page of the host results in No host found error.

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

- Satellite 6.12 

How reproducible:

- Everytime

Steps to Reproduce:

1. Access the Edit form for a host.

2. Access the Interfaces tab

3. Click Edit on any interface.

4. Press Ok and then Submit.

Actual results:

- This results in No host found page.

  Redirection happens to `https://satellite.example.com/new/hosts/client#/Overview` instead of `https://satellite.example.com/new/hosts/client.example.com#/Overview`

Expected results:

- Should redirect to the correct page. 

Additional info:

- Only happens if Ok is selected on the interface edit page and then Submit is selected. Simply selecting Submit does not present the issue.

This feels like a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=2184018 . Could you check on 6.13 on newer?

Hello Adam, 

Thanks for the reply. The issue seems to be resolved in 6.13.

Since this is fixed in 6.13 and this BZ doesn't have any customer case linked to it, I'd suggest we close it as a duplicate, unless you feel strongly about having this fixed in 6.12.z. Would that be ok?

Hello Adam,

Thanks for the reply. I don't have any objection to closing it.

Closing per #2, #3 and #4. Feel free to reopen

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