Hide Forgot
Description of problem: When the systems have the same hostname, only the last one can be kept registered in satellite6.2. Version-Release number of selected component (if applicable): Satellite-6.2.0-RHEL-7-20160907.6 How reproducible: always Steps to Reproduce: 1. Install 2 systems: RHEL-7.3-Snapshot-4.0-server-x86_64. 2. Make sure the 2 systems have the same hostname 'test'. 3. Register system 1 to Satellite-6.2.0-RHEL-7-20160907.6, and the system is recorded in satellite UI. (Please see attachment 'register_client1_successfully.png') 4. Register system 2 to Satellite-6.2.0-RHEL-7-20160907.6, and check the 2 records in satellite UI: the system 2 is recorded while the record of system 1 is missing. (Please see attachment 'register_client2_successfully_with_client1_missing_in_satellite_UI.png') 5. Check the identity of system 1 in CLI: [root@test ~]# subscription-manager identity Unit c1666704-99a2-4fc1-b9e7-70b87810aeb3 has been deleted Actual results: As step 4 and step 5.. Expected results: All the systems can be registered with the same hostname. And all the systems should be recorded in satellite UI. Additional info: foreman-debug log is the attachment 'task-export-1474263771.tar.gz'
Created attachment 1202309 [details] task-export-1474263771.tar.gz
Created attachment 1202310 [details] register_client1_successfully.png
Created attachment 1202311 [details] register_client2_successfully_with_client1_missing_in_satellite_UI.png
Justin, this is expected behavior, correct? I.e. hostnames of registered systems should be unique.
Yes, starting in 6.2 this is expected behavior. If you'd like to see this behavior return please write up some good use cases. Generally having multiple hosts with the same fqdn is not a corrects situation.
Hi, Justin I have not some scenarios need registering systems with the same hostname. Due to curiosity，I tried against stage candlepin. The stage can identify two systems with the same hostname by different consumer IDs. (Please see attachment 'stage_can_identify_systems_with_same_hostname.png') Does the satellite need to keep in line with stage candlepin?
Hi, Satellite is based upon foreman which adds this restriction (and has always had this restriction, we've just now properly unified with it). I don't think there is a need to allow duplicate hostnames with the same name just because stage does. If there is some user requirement that requires it, it could be considered to be added back as part of foreman.
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 Rich Jerrido or Bryan Kearney 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.