To remediate the CVE's below, we've upgraded to the latest VMware 7.0 U3s, but now our vcenter client plugins give us the following error.. Please advise.
Error deploying plug-in. java.lang.IllegalStateException: Cannot convert value of type 'java.lang.String' to required type 'com.fasterxml.jackson.databind.PropertyNamingStrategy' for property 'propertyNamingStrategy': no matching editors or conversion strategy found org.springframework.beans.TypeConverterDelegate.convertIfNecessary(TypeConverterDelegate.java:262)
Solved! Go to Solution.
Maybe the same (or similar to) the issue encountered in previous upgrades with a workaround that involves Nimble support restarting jetty service on your array(s) as described in this post. and addressed in Customer Advisory a00142228en_us What version of NimbleOS is on the array(s) linked to your vCenter, and what version is your VCSA? The latest VCSA is vCenter Server 7.0 Update 3t version 7.0.3.02200 released 2024-10-21.. I assume you updated the host ESXi version to ESXi 7.0 Update 3s build 24585291 released today...
Thanks for that info. The customer advisory link didn't appear to work for me. I'll try searching the number, though.
Below are the versions we're running:
Nimble: 6.1.2.500-1053701-opt
ESXi Hosts: VMware ESXi, 7.0.3, 24585291
VCSA: 7.0.3.02200 build 24322018
The advisory https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00142228en_us
states that affected versions are:
So I'm sure this can be fixed in your case by upgrading NimbleOS to 6.1.2.502 or latest version 6.1.2.600. If your environment requires a maintenance window to do that, then a short-term solution would be to call Nimble Supoort and ask them to apply the workaround (which is to restart the jetty service on your arrays(s) which makes the array GUI unavailable for a minute or two while restarting, but does not interrupt the array serving I/O) and then have you retry reinstalling the plugin.
That link works great. I apprecaite the VERY quick responses. We'll work on getting our Nimble version updated, but I'm showing a DECLINED_SUPPORT_GM for that version. I'll reach out to support and see which direction they'd like to take, the workaround or approve that update for us.
DECLINED_SUPPORT_GM is due to array being out of active support. Can you please confirm if the customer has renewed support contract recently ?
We did reach out to support and they let us know that one of the two arrays in the group were out of support. We've since sent in the renewal approval and awaiting it to be appled. We'll then get the arrays updated. Thanks for the help, everyone!