vCenter Plugin 400-OK Error after migration to vCenter 7.0 U3c

[ICPMuenchen]

Hey,

today we upgraded to vcenter v7 and after installing the latest Simplivity vCenter Plugin 4.1.1.670 we have some 400 OK errors on the Plugin Pages:

Any hints or recommendations?

Regards

Peter

[CadenLange]

That's interesting - I'm getting exactly the same thing  but this is a new deployment and so I didn't upgrade my vCenter like you...... just deployed a new VCSA straight on 7.0 U3c

And I'm also running plugin 4.11.670..... however, did try a previous plugin version and got the same results.

Am I correct in saying that it's only those three panels that are affected? All the other plugin panels work fine??

No idea's on a fix yet though - what version of VCSA were you on previously and did they all work ok using that previous version - sounds like it might have been a 6.x release, I was keen to know if this is just 7.0.3 related an it might be fine using 7.0.2d. There is mention in the interop guide of potential issues with backup policy creation but that seems to be fine for me.

Keep us posted on any updates\breakthroughs

good luck - Caden

[ICPMuenchen]

Hello Caden,

glad i am not the only one

we had VCSA 6.7 latest Release before and had no issues with 4.1.1.670 Plugin. We updated to Simplivity 4.1.1.U1 some weeks ago without any issues. While upgrading to VCSA 7.0 U3c, vCenter Setup said the Plugin will be removed because it is not possible to migrate.

The 400-OK error also appears when you try to create a support capture file in the 1. step on Host-Level. Didnt find any other menus where it appears so far.

I opened a case, and already sent some logs to Simplivity Team, lets see what say will say or recommend.

Will keep you posted.

Regards

Peter

[CadenLange]

Hi Peter

Yeah - just run a create support capture and get the same - I hadn't tried that before.

Hopefully a simple fix that support can come back with...... I guess your environment was already registered in InfoSight whereas I'm not sure how I can register mine as it's a new install and the infosight page of the plugin isn't working - I'll look to see if there's a command line option for registering with InfoSight but I don't think there's any alternative.

cheers

C

[ICPMuenchen]

yes we already registered in infosight long time ago. this still works even i cant access the Plugin Page.

In infosight it still shows we have vCenter 6.7 but i think this is due to the missing update of our hosts to vsphere 7. Dont want to update them even the vCenter 7 Issues arent fixed so far.

[gustenar]

This issue is currently under investigation. Will provide more updates as soon as available. 

[CadenLange]

Hi

Do you know yet if this issue is only experienced with vCenter 7.0.3x or if it will still be evident with 7.0.2x versions of vCenter?

many thanks 

[gustenar]

It's only happening with vCenter 7.0. U3c. No reports of other versions affected with this issue. 

[David4033]

Hello,

Same issue on deploy new cluster 4.1.1U1

svt-session fail :

HVAL create session failure, HVALInvalidIdentityException:Invalid Login exception occurred while connecting to the vSphere Server to create a session.

[CadenLange]

"It's only happening with vCenter 7.0. U3c. No reports of other versions affected with this issue. "

Ok good - so is 7.0 U3a OK?

Or should be be avoiding 7.0 U3x altogether and just stick with 7.0 U2x?

many thanks

[David4033]

7.0 U3a not in interop

vCenter Server Appliance 7.0 U2d 18455184

or

vCenter Server Appliance 7.0 U3c (2) 19234570

2. HPE OmniStack backup policy creation may not work from vCenter web client. Instead it could be carried via OmniStack command line. The bug is in investigation & will be addressed in the next OmniStack release.

[ICPMuenchen]

Finally we got an answer from HPE L3 Support and we were told, there is currently no workaround available for this Problem. It should be fixed with the next omnistack Update to Version 4.1.2 (no ETA known at the moment)

HPE Tracking: CFI: 27955
Problem description:
"Due to the ongoing concerns over the log4j vulnerabilities engineering approved usage of vCenter 7.0u3c in the following announcement: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00121438en_us

Despite being considered for approval with OmniStack software 4.1.0, 4.1.0u1, and 4.1.1u1, it was noted that some GUI functionality was impacted, specifically the ability to create / modify backup policies broken, and additional reports of https 400 errors with certain actions."

Root Cause Analysis:
"The issue was discovered during testing and certification of the build, however, customers who wish to mitigate the log4j risk may still wish to perform this upgrade despite known problems."

Work Around:
"There is currently no workaround available."

[David4033]

Install New  vCenter Server Appliance 7.0 U2d 18455184

Register host esxi

dsv-digitalvault-init --hmsuser SSO --hostip IP --hostuser root

dsv-update-vcenter --server IP --username SSO

Work fine

[Kipp_Glover · Accepted solution]

FYI.....Today,  May 13th, HPE released two plug-in packages to resolve the 400-OK errors seen in the plug-in.

Download Links:
HPE SimpliVity Plug-in for vSphere Web Client for 4.1.0 and 4.1.0U1; Build # 4.1.0.12781
https://support.hpe.com/hpesc/public/swd/detail?swItemId=MTX_23f37482331345cc8606b682ac 

HPE SimpliVity Plug-in for vSphere Web Client for 4.1.1U1; Build # 4.1.1.12784
https://support.hpe.com/hpesc/public/swd/detail?swItemId=MTX_e844c797fedf43bfb83b014c77

Fixes - Certain SimpliVity Plug-in functionalities with VMware vCenter Server 7.0 Update 3c (vCSA 7.0 U3c) will results in Error "400 - OK" or "400: Bad Request" , including backup policy creation and InfoSight registration. This version of the SimpliVity plug-in fixes this issue.

The updated advisory will be published soon to include these links.  The link will be posted once available. 

Cheers!
/Kipp

[Kipp_Glover]

Here is the link to the advisory with the updated resolution:  https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00122345en_us

/Kipp

[ICPMuenchen]

Installed this morning, and no errors so far.

*thumbsup*