Red Hat Bugzilla – Bug 1435378
split-stack: deployment error for initiatorname.iscsi config
Last modified: 2017-05-17 16:13:23 EDT
I was deploying a split stack overcloud. During step 4, I hit a puppet error for iscsi initiator config on the Compute node. Here's the puppet error: Error: /bin/echo InitiatorName=$(/usr/sbin/iscsi-iname) > /etc/iscsi/initiatorname.iscsi returned 1 instead of one of [0] Error: /Stage[main]/Tripleo::Profile::Base::Nova::Compute/Exec[reset-iscsi-initiator-name]/returns: change from notrun to 0 failed: /bin/echo InitiatorName=$(/usr/sbin/iscsi-iname) > /etc/iscsi/initiatorname.iscsi returned 1 instead of one of [0] And journalctl grepping for iscsi-related entries: Mar 23 15:16:22 compute.dansosp.net os-collect-config[1210]: Notice: /Stage[main]/Tripleo::Profile::Base::Nova::Compute/Exec[reset-iscsi-initiator-name]/returns: sh: /usr/sbin/iscsi-iname: No such file or directory Mar 23 15:16:22 compute.dansosp.net os-collect-config[1210]: Notice: /Stage[main]/Tripleo::Profile::Base::Nova::Compute/Exec[reset-iscsi-initiator-name]/returns: sh: /etc/iscsi/initiatorname.iscsi: No such file or directory Mar 23 15:16:22 compute.dansosp.net os-collect-config[1210]: Notice: /Stage[main]/Tripleo::Profile::Base::Nova::Compute/File[/etc/iscsi/.initiator_reset]: Dependency Exec[reset-iscsi-initiator-name] has failures: true Mar 23 15:16:22 compute.dansosp.net os-collect-config[1210]: Error: /bin/echo InitiatorName=$(/usr/sbin/iscsi-iname) > /etc/iscsi/initiatorname.iscsi returned 1 instead of one of [0] Mar 23 15:16:22 compute.dansosp.net os-collect-config[1210]: Error: /Stage[main]/Tripleo::Profile::Base::Nova::Compute/Exec[reset-iscsi-initiator-name]/returns: change from notrun to 0 failed: /bin/echo InitiatorName=$(/usr/sbin/iscsi-iname) > /etc/iscsi/initiatorname.iscsi returned 1 instead of one of [0] Mar 23 15:16:22 compute.dansosp.net os-collect-config[1210]: Warning: /Stage[main]/Tripleo::Profile::Base::Nova::Compute/File[/etc/iscsi/.initiator_reset]: Skipping because of failed dependencies I worked this issue by manually running "sudo /bin/echo InitiatorName=$(/usr/sbin/iscsi-iname) > /etc/iscsi/initiatorname.iscsi" on the compute node (which works) and then rerunning the deployment command. From Alex Schultz: This seems like an ordering thing where iscsi-initiator-utils is not installed before we try and reset the name but eventually gets installed which is why you were able to do it after the fact. Could you log a BZ and we can fix it? Upstream bug is https://bugs.launchpad.net/tripleo/+bug/1675462 with proposed fix https://review.openstack.org/449200
this can be temporarily worked around by manually installing iscsi-initiator-utils on the deployed servers before the overcloud deployment
Given the manual workaround - not a blocker. But let's try to make it in.
If that's the case, should I document the workaround? (I'm assuming yes, but want to check if this patch will make it into OSP11)
Verified on build 2017-04-20.2 [stack@undercloud-0 ~]$ rpm -q puppet-tripleo puppet-tripleo-6.3.0-10.el7ost.noarch
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:1245