Bug 1598562 - [OSP-10]iSCSI initiatornames should be different and random on all hosts deployed, not just computes
Summary: [OSP-10]iSCSI initiatornames should be different and random on all hosts depl...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: puppet-tripleo
Version: 10.0 (Newton)
Hardware: x86_64
OS: Linux
low
low
Target Milestone: z9
: 10.0 (Newton)
Assignee: Alan Bishop
QA Contact: Avi Avraham
Kim Nylander
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-05 19:31 UTC by Alan Bishop
Modified: 2021-12-10 16:43 UTC (History)
21 users (show)

Fixed In Version: puppet-tripleo-5.6.8-9.el7ost
Doc Type: Bug Fix
Doc Text:
Previously, all overcloud nodes were deployed with the same iSCSI initiator name (IQN). This is a consequence of using a common overcloud image. Later in the deployment, the IQN is reset on Compute nodes. However, the IQN is not reset on Controllers, which also need to support iSCSI connections. As a result, all overcloud Controller nodes have the same IQN, which causes iSCSI connections to fail. With this update, the IQN is now reset on both Controller and Compute nodes and Controllers can create reliable iSCSI connections because all of the Controllers have a unique IQN. Note: The IQN on an overcloud node should be reset once, and only once. If a user has already manually reset the IQN on an overcloud node, then care must be taken to ensure that TripleO does not reset the IQN a second time. TripleO uses a sentinel file (/etc/iscsi/.initiator_reset) to determine whether it should reset the node IQN. To prevent TripleO from resetting the IQN on a node, run the following command on that node: sudo touch /etc/iscsi/.initiator_reset
Clone Of: 1306727
Environment:
Last Closed: 2018-09-17 16:56:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 482166 0 None MERGED Refactor iscsi initiator-name reset into separate profile 2020-09-02 00:46:23 UTC
Red Hat Issue Tracker OSP-11461 0 None None None 2021-12-10 16:43:33 UTC
Red Hat Product Errata RHBA-2018:2670 0 None None None 2018-09-17 16:57:14 UTC

Description Alan Bishop 2018-07-05 19:31:56 UTC 
+++ This bug was initially created as a clone of Bug #1306727 +++

Description of problem:
https://bugzilla.redhat.com/show_bug.cgi?id=1244328 was about all overcloud nodes having the same initiatorname post-deployment.

This is resolved for compute nodes, but all other nodes (controller, ceph, swift, cinder) still have the same initiatornames. This is not a problem in a vanilla setup the way we use it, but will pose a problem if additional drives are added to these hosts via iscsi later on. 

Version-Release number of selected component (if applicable):
[stack@instack ~]$ rpm -qa |grep tripleo
openstack-tripleo-image-elements-0.9.6-10.el7ost.noarch
openstack-tripleo-common-0.0.1.dev6-6.git49b57eb.el7ost.noarch
openstack-tripleo-heat-templates-0.8.6-119.el7ost.noarch
openstack-tripleo-puppet-elements-0.0.1-5.el7ost.noarch
openstack-tripleo-0.0.7-0.1.1664e566.el7ost.noarch


How reproducible:
Always


[stack@instack ~]$ nova list
+--------------------------------------+-------------------------+--------+------------+-------------+---------------------+
| ID                                   | Name                    | Status | Task State | Power State | Networks            |
+--------------------------------------+-------------------------+--------+------------+-------------+---------------------+
| fe8c1d14-d63b-442e-91b8-a6c68f1214ce | overcloud-cephstorage-0 | ACTIVE | -          | Running     | ctlplane=192.0.2.7  |
| 44344478-0866-40f4-9a27-a9fa84343119 | overcloud-compute-0     | ACTIVE | -          | Running     | ctlplane=192.0.2.11 |
| 69335882-c373-4956-9823-47d95cd1ed4b | overcloud-compute-1     | ACTIVE | -          | Running     | ctlplane=192.0.2.9  |
| 3c691e1a-6a7e-48f1-bb28-fc2b7e953d15 | overcloud-controller-0  | ACTIVE | -          | Running     | ctlplane=192.0.2.12 |
| abd350f8-54e2-420f-9e3e-d7f4081ed51c | overcloud-controller-1  | ACTIVE | -          | Running     | ctlplane=192.0.2.10 |
| 58483250-538b-4bdb-861b-f7cc98f7d08d | overcloud-controller-2  | ACTIVE | -          | Running     | ctlplane=192.0.2.8  |
+--------------------------------------+-------------------------+--------+------------+-------------+---------------------+


[stack@instack ~]$ for i in `nova list|grep ctlplane|cut -d"=" -f2 |cut -d' ' -f1`; do echo $i; ssh heat-admin@$i cat /etc/iscsi/initiatorname.iscsi; done
192.0.2.7
InitiatorName=iqn.1994-05.com.redhat:9d4e9e8d8fe
192.0.2.11
InitiatorName=iqn.1994-05.com.redhat:8950acdea36
192.0.2.9
InitiatorName=iqn.1994-05.com.redhat:7c3107a5d62
192.0.2.12
InitiatorName=iqn.1994-05.com.redhat:9d4e9e8d8fe
192.0.2.10
InitiatorName=iqn.1994-05.com.redhat:9d4e9e8d8fe
192.0.2.8
InitiatorName=iqn.1994-05.com.redhat:9d4e9e8d8fe
Comment 12 Tzach Shefi 2018-08-22 09:05:14 UTC 
Verified on:
puppet-tripleo-5.6.8-15.el7ost.noarch

Using a preinstalled none HA system, as can be seen each node has a unique initiatorname
 

[stack@undercloud-0 ~]$ nova list
+--------------------------------------+--------------+--------+------------+-------------+------------------------+
| ID                                   | Name         | Status | Task State | Power State | Networks               |
+--------------------------------------+--------------+--------+------------+-------------+------------------------+
| ab9196a9-e749-439a-b1c4-2ec3e80f9987 | ceph-0       | ACTIVE | -          | Running     | ctlplane=192.168.24.8  |
| 68ecfaf8-1914-4402-bdf1-a87e89207e98 | compute-0    | ACTIVE | -          | Running     | ctlplane=192.168.24.13 |
| 67800ed3-d27b-4510-9262-83d1bd1750ce | controller-0 | ACTIVE | -          | Running     | ctlplane=192.168.24.10 |
+--------------------------------------+--------------+--------+------------+-------------+------------------------+

[stack@undercloud-0 ~]$ for i in `nova list|grep ctlplane|cut -d"=" -f2 |cut -d' ' -f1`; do echo $i; ssh heat-admin@$i cat /etc/iscsi/initiatorname.iscsi; done
192.168.24.8
InitiatorName=iqn.1994-05.com.redhat:62f05d2d527f
192.168.24.13
InitiatorName=iqn.1994-05.com.redhat:60a939123
192.168.24.10
InitiatorName=iqn.1994-05.com.redhat:4b6a62dbbffe


Checked again on another deployment, same puppet version, this time HA but without ceph, again all nodes have unique initiator names. 

for i in `nova list|grep ctlplane|cut -d"=" -f2 |cut -d' ' -f1`; do echo $i; ssh heat-admin@$i cat /etc/iscsi/initiatorname.iscsi; done
192.168.24.13
InitiatorName=iqn.1994-05.com.redhat:b561b3b97b47
192.168.24.11
InitiatorName=iqn.1994-05.com.redhat:78f83527fe0
192.168.24.15
InitiatorName=iqn.1994-05.com.redhat:4e9d77958d2b
192.168.24.8
InitiatorName=iqn.1994-05.com.redhat:3d69e4e6dd
192.168.24.7
InitiatorName=iqn.1994-05.com.redhat:5b36aea878d6

Based on these two systems OK to verify.
Comment 14 errata-xmlrpc 2018-09-17 16:56:14 UTC 
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/RHBA-2018:2670
Note You need to log in before you can comment on or make changes to this bug.