Bug 1625650 - Unable to change a host's primary interface.
Summary: Unable to change a host's primary interface.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Networking
Version: 6.3.2
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Roman Plevka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-05 13:00 UTC by Varatharaja Perumal G
Modified: 2023-09-07 19:22 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-02 12:33:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 24925 0 Normal New Unable to change a host's primary interface. 2021-01-04 09:26:21 UTC

Description Varatharaja Perumal G 2018-09-05 13:00:46 UTC
Description of problem:

When registering a host with two interfaces to the satellite server. 

Lets assume it takes the configuration as below.

eth0:
eth1: primary + provisioning named test.example.com

We attempt to change eth0 to the primary interface because eth1 is actually on a private network we get a validation error of "Some of the interfaces are invalid. Please check the table below." and eth0 is highlighted. When we Edit eth0 it says the DNS name is already taken. If we attempt the operation again by removing the DNS name and domain from eth1 the validation still fails for the same reason. The only way I've been able to modify a host's primary interface has been by giving the new primary interface a completely new name. This results in the host having a new, incorrect, FQDN then we have to go back and change back to the original hostname.


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

Satellite 6.3

How reproducible:

Steps to Reproduce:

1. Register a host with two nic's using bootstrap.
2. Change the primary interface settings from eth1 to eth0.


Actual results:

Failed with DNS name is already taken

Expected results:

We should be able to change the interface without any issue.

Additional info:

Workaround:

Modify a host's primary interface new primary interface with a completely new name (test.example.com to test-temp.example.com). This results in the host having a new, incorrect, FQDN then we have to go back and change back to the original hostname (test-temp.example.com to test.example.com).

Comment 2 Ondřej Pražák 2018-09-13 09:05:06 UTC
Created redmine issue http://projects.theforeman.org/issues/24925 from this bug

Comment 6 Bryan Kearney 2020-03-04 14:08:17 UTC
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.

Comment 7 Bryan Kearney 2020-04-02 12:33:04 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.


Note You need to log in before you can comment on or make changes to this bug.