Bug 2212808

Summary:	Editing the Interface on Satellite results in No host found error
Product:	Red Hat Satellite	Reporter:	Manu Sunil <msunil>
Component:	Navigation	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.12.4	CC:	aruzicka
Target Milestone:	Unspecified
Target Release:	Unused
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:	2023-06-07 08:16:26 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 Manu Sunil 2023-06-06 12:29:12 UTC

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.

Comment 1 Adam Ruzicka 2023-06-06 12:44:15 UTC

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

Comment 2 Manu Sunil 2023-06-06 12:57:54 UTC

Hello Adam, 

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

Comment 3 Adam Ruzicka 2023-06-06 13:46:33 UTC

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?

Comment 4 Manu Sunil 2023-06-06 17:44:22 UTC

Hello Adam,

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

Comment 5 Adam Ruzicka 2023-06-07 08:16:26 UTC

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

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