I'm updating from 7.0.521 -> 7.0.531. Running advisory report fist stuck for a while to 80% then fails. "Failed to generate the advisory report. Please retry the operation after some time." This is happening in two separate systems.
So far so good - It appeared to hang, then completed. Much better than before. Will report back after the upgrade installs (as I was having issues here as well).
VxRail Update ran into a problem... Error extracting upgrade bundle 7.0.531-28777448. The upgrade engine is deployed. However it failed to start. Try again later.
This led me to:
<ADMIN NOTE: Broken link has been removed from this post by Dell>
I verified the logs ( tail -f /var/log/mystic/lcm-web.log ), and was seeing that the verify_bundle_signature.py file was not found, so I followed the steps to place the file where it needed to be.
After doing so, and retrying the update, I receive the same error:
VxRail Update ran into a problem...
Error extracting upgrade bundle 7.0.531-28777448. The upgrade engine is deployed. However it failed to start. Try again later.
Checking the logs again, this time a new error:
2024-10-16T18:30:28.950Z <4dfa9a554f1a43e1f26e5efb705999fc> lcm [ERROR] <286> ScriptServiceImpl.java runLocalScript() (424): Running local script got exception: scriptName=/etc/vmware-marvin/scripts/lcm/scripts/verify_bundle_signature.py, shebangCommand=/etc/vmware-marvin/scripts/lcm/lcm_python, timeout=600000, envp= parameters=--bootstrap-check 2024-10-16T18:30:28.950Z <4dfa9a554f1a43e1f26e5efb705999fc> lcm [ERROR] <286> ScriptServiceImpl.java runLocalScript() (426): Running local script got exception. java.io.IOException: Cannot run program "/etc/vmware-marvin/scripts/lcm/lcm_python": error=2, No such file or directory
Looks like a support case is needed. Sometimes I wonder if they test these updates!
Sorry for my delay, I didn't get notified of the reply. - I only found your reply because I am preparing to deploy 7.0.532, and I am seeing the same behavior - They don't test these, I am now convinced!
Regarding my prior specific issue/error, my Dell/EMC Engineer was able to find a customer facing KB:
As I review my emails, After he sent me this KB, I replied informing him that I had restarted 'hostd' on all nodes using SuperPutty, and my upgrade was able to continue and succeed.
DELL-Josh Cr
Community Manager
•
9801 Posts
•
45350 Points
0
1
Posted October 16th, 2024 18:43
Thanks for the info, yes calling phone support is the best option.