14. April 2021 at 16:03 #104998
Happy Friday All
Trying to upgrade my DHC 5070 from DHC 1.1 to 1.5. I’m following the steps in the conversion/upgrade guide https://dl.dell.com/topicspdf/dhc_cg_en-us.pdf
I’m using Version: WMS 3.2 780 Public Cloud with an on-prem WMS Repo 3.2 server that is sync’ing without issue
Page 7 Step 3
Copy the image upgrade add-on DHCImageUpgradeAddon.tar.gz and image upgrade iso file DellHybridClient_1.5_750_5070.iso or DellHybridClient_1.5_750_7070.iso corresponding to the platform model to the Wyse Management Suite local repository—\repository\hybridClientApps>.
I’ve done that here in WMS Repo
And the files are showing in WMS Public Cloud so I can setup the Job
Page 9 Step 7
Go to Apps & Data and create the advanced app policy, DHC1.5 Upgrade for the subgroup, DhcUpgradeStageUpgrade
to install Image upgrade add-on and the ISO conversion image respectively.
Check the Enable app dependency option to ensure that the image add-on is installed first followed by the ISO image.
NOTE: You must create the app policy for operating system subtype Ubuntu 18.04.
This picture in Dell’s documentation had me confused because I’m expecting the first drop down to list DHCImageUpgradeAddon.tar.gz but it starts with DHC1.5ImageU… in the picture below.
Remembering from the steps of the 1.0 to 1.1 Upgrade we had to unpack the tar.gz file to get the .bundle file, but it never lists that step in the Dell Documentation
In the screenshot below of my Upgrade job I expanded the screen to better show the application names:
So making my policy look exactly like Dells documentation, I get the following failure when I use the .bundle and the ISO
Failed – (Name: DHC1.5ImgUpgradeAddon.bundle Description: Failed to install DHC1.5ImgUpgradeAddon.bundle ( Could not find signature file in : /etc/WMSApps/DHC1.5ImgUpgradeAddon.bundle ) Status: Failed), ( Name: DellHybridClient_1.5_750_5070.iso Description: Install or Uninstall was not tried due to app dependency. Status: Pending)
Based on that message not finding the signature file I tried changing the above App policy to use the tar.gz which contains both the bundle and signature files, thinking maybe Dell’s verbiage was correct but the image was incorrect.
If I use the tar.gz in the policy, I get the following failure message
Failed – ( Name: DHCImageUpgradeAddon.tar.gz Description: successfully installed or Uninstalled. Status: Success), (Name: DellHybridClient_1.5_750_5070.iso Description: Failed to Download DellHybridClient_1.5_750_5070.iso ( FetchError: request to https://xxxxxxxx.corp.xxxxxxxxxx.net:443/wms-repo/image/app/hybridClient?fileName=DellHybridClient_1.5_750_5070.iso failed, reason: getaddrinfo ENOTFOUND xxxxxxxx.corp.xxxxxxxx.net ) Status: Failed)
I’m stuck now and not sure how to properly upgrade and what getaddrinfo ENOTFOUND means or how to correct it.
Always appreciate the help here @ConfGen14. April 2021 at 16:36 #105070ConfGenKeymaster
- Total Post: 11285
- Jedi Master
I haven’t taken a look at the DHC guide, but that looks wrong to me.
In my environment, I have unzipped the tar.gz file and extracted the .bundle file. After that, I have uploaded the .bundle file to my WMS server and pushed it to my DHC client.
The ISO is only for converting a Non-DHC device to DHC. This is not needed in your case.
CG14. April 2021 at 18:00 #105089
I did a new policy as in the past when going from DHC 1.0 to 1.1 and just used the .bundle file, but it seems to not like that.
Failed – (Name: DHC1.5ImgUpgradeAddon.bundle Description: Failed to Download DHC1.5ImgUpgradeAddon.bundle ( FetchError: request to https://xxxxxxxxx.corp.xxxxxxxx.net:443/wms-repo/image/app/hybridClient?fileName=DHC1.5ImgUpgradeAddon.bundle failed, reason: getaddrinfo ENOTFOUND xxxxxxx.corp.xxxxxxxx.net ) Status: Failed)
The upgrade worked in the past I’ll have to login as an admin and see what is going on, i can’t bring up any tools while auto-signon as guest22. April 2021 at 13:22 #105170ConfGenKeymaster
- Total Post: 11285
- Jedi Master
Where did you get this error message?
CG22. April 2021 at 14:51 #105186
That was the message in the Job section of WMS Public Cloud after the job went to failed.
I did pull a log file but not sure where to look
The log exported as DHC8c47be19df04-2021-04-14-14.47.39.tar
Unpacking the log file with 7zip i get a lot of other files i just haven’t had time to dig through, any help would be appreciated
- You must be logged in to reply to this topic.