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.
DescriptionVaratharaja 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).
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.
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.