Bug 1598562
Summary: | [OSP-10]iSCSI initiatornames should be different and random on all hosts deployed, not just computes | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Alan Bishop <abishop> |
Component: | puppet-tripleo | Assignee: | Alan Bishop <abishop> |
Status: | CLOSED ERRATA | QA Contact: | Avi Avraham <aavraham> |
Severity: | low | Docs Contact: | Kim Nylander <knylande> |
Priority: | low | ||
Version: | 10.0 (Newton) | CC: | abishop, amcleod, aschultz, athomas, bfournie, cschwede, dbecker, dsneddon, jcoufal, jjoyce, jschluet, mburns, morazi, owalsh, pablo.iranzo, pgrist, rhel-osp-director-maint, slinaber, srevivo, tshefi, tvignaud |
Target Milestone: | z9 | Keywords: | Triaged, ZStream |
Target Release: | 10.0 (Newton) | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
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
|
Story Points: | --- |
Clone Of: | 1306727 | Environment: | |
Last Closed: | 2018-09-17 16:56:14 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Alan Bishop
2018-07-05 19:31:56 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. 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 |