Description of problem: Any host installed with latest ISO available on portal is showing same initiator iqn name as iqn.1994-05.com.redhat:94d965987640 Version-Release number of selected component (if applicable): RHV 4 Host : RHVH-4.0-20161018.0-RHVH-x86_64-dvd1.iso How reproducible: 100% Steps to Reproduce: 1. Install the RHV host with ISO RHVH-4.0-20161018.0-RHVH-x86_64-dvd1.iso 2. Check the Initiator iqn name at /etc/iscsi/initiatorname.iscsi 3. It is always same for all the hosts. Actual results: same Initiator name as iqn.1994-05.com.redhat:94d965987640 for all the hosts Expected results: The iqn name should be generated randomly Additional info:
This should really be fixed in platform. But this script can be used to generate a new name: sed "s/:.*$/:$(cut -d- -f 5 < /proc/sys/kernel/random/uuid)/" < /etc/iscsi/initiatorname.iscsi
Test this issue on redhat-virtualization-host-4.0-20161115.1. Test steps are split into two parts, one is initial install test, the other is upgrade test. The test steps and results are as followed: Initial install test: 1. Install RHVH on several servers(for example, 3 servers) 2. Check the initiator iqn on each server after login to RHVH cat /etc/iscsi/initiatorname.iscsi 3. Reboot the server, and check the initiator iqn again Initial install results: 1. Each server has an unique initiator iqn. 2. After reboot, the iqn can be persisted. Upgrade test: 1. Install an old version RHVH(redhat-virtualization-host-4.0-20160919.0) 2. Check the initiator iqn after login to the old version RHVH 3. Upgrade to the latest version(redhat-virtualization-host-4.0-20161115.1) 4. Reboot and login to the latest version RHVH 5. Check the initiator iqn again Upgrade results: After upgrade, the initiator iqn of the latest RHVH is the same as the old RHVH. Fabian, there are two questions need your confirmation: 1. If the test steps are sufficient to test this issue? 2. All hosts installed with one old version, such as redhat-virtualization-host-4.0-20160919.0, have the same initiator iqn. Upgrade them to the latest version, the iqn will be persisted. So, after upgrade, all hosts with the latest version will have the same iqn as well. To resolve this problem, should we generate the unique iqn manually before upgrade?
This bug had requires_doc_text flag, yet no documentation text was provided. Please add the documentation text and only then set this flag.
Test Versions: redhat-virtualization-host-4.1-20170116.0 imgbased-0.9.4-0.1.el7ev.noarch Test Steps: 1. Install RHVH on 3 servers 2. Check the initiator iqn on each server after login to RHVH #cat /etc/iscsi/initiatorname.iscsi 3. Reboot the server, and check the initiator iqn again Test Results: 1. Each server has an unique initiator iqn. 2. After reboot, the iqn can be persisted. The bug is fixed, set the status to VERIFIED
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:1114