nebb2k8
Enthusiast
Enthusiast

7.0.2 - iSCSI name change after upgrade

Updated an ESXi host from v7.0 U1d (17551050) to v7 U2a (17867351) using Image Mode in Lifecycle Manager. After reboot the iSCSI initiator's name changed breaking iSCSI connectivity.

Whilst I didnt record its previous name (I overwrote the SAN ACL), Altthough I can show the differences from other identical hosts in the cluster. The auto generated number after the hostname completely changed and appended with a ":64" . This is very concerning. 

v7U1d = iqn.1998-01.com.vmware:labesx06-4ff17c83

v7U2a = iqn.1998-01.com.vmware:labesx07:38717532:64

It also now shows an iSCSI Alias of "iscsi_vmk".

I couldnt find any references to this change in the release notes. Am I going crazy here?

nebb2k8_0-1622102345677.png

nebb2k8_1-1622102354837.png

0 Kudos
12 Replies
nebb2k8
Enthusiast
Enthusiast

I decided to try another host, same problem. Undocumented iSCSI name changes. Anyone else getting this?

pre.PNGpost.PNG

 

0 Kudos
TheBlueLion
Contributor
Contributor

No, you are not crazy as I am also getting the same issue too, I first noticed it with I ran the non-critical security updates.  I assumed it was because I had not used the Dell branded ESXi image so I reverted the patch.

I imported the Dell EMC VMware-VMvisor-Installer-7.0.0.update02-17867351.x86_64-DellEMC_Customized-A03.iso image, ran the upgrade again still no storage.  At that point I noticed the iSCSI initiator name had changed from ....-418bdc22 to ...:21404486:64, WTH!

I changed it back to the original name, rescanned storage and adapter, no luck.  I then rebooted and now it has all come back up as it was before.

Nice move VMWare, thanks a lot!  

Anyway, relatively easy fix for me.

 

 

 

0 Kudos
nebb2k8
Enthusiast
Enthusiast

I have a response from VMware support...

 

This is a known issue with 7.0U2 and here configuration restore is failing because of invalid iqn of the software adapter.

 

 Ofcourse its another "Internal Bug" with no KB private or public.

 

Unfortunately even we do not have any internal kb's yet for reference. We are right now getting all these information on a different channel from our Engineering team. Sorry again.

 

Joke

0 Kudos
depping
Leadership
Leadership

What is the SR number for this?

0 Kudos
depping
Leadership
Leadership

I found the case internally... will push engineering/support to release a KB.

nebb2k8
Enthusiast
Enthusiast

Thank you depping

0 Kudos
depping
Leadership
Leadership

Just an update, KB is being worked on, and situation is being investigated by engineering.

0 Kudos
lukaslang
Enthusiast
Enthusiast

Just another indicator that 7.0 U2(a) is a complete mess. Never had so many issues with previous upgrades.

0 Kudos
depping
Leadership
Leadership

Issue is identified, KB should be published shortly, This should only happen when upgrading from U1 to U2, when you use randomly generated IQNs.

0 Kudos
BSteinmetz
Contributor
Contributor

Well this just happened to me on a clean install of U2a. So there goes that theory.
0 Kudos
depping
Leadership
Leadership

please create a log dump and create a support request!

0 Kudos
depping
Leadership
Leadership