Moving a Simplivity cluster to a new vCenter fails with: Error 0, Failed to validate and..

[AleksandarPeev]

Hi all,

I have new conundrum for you.

I have to move a Simplivity cluster to a new vCenter.
Of course i have looked up the discusssion groups and I have found the following well descriptive discussion that says it is oh so easy:

https://community.hpe.com/t5/HPE-SimpliVity/How-to-move-simplivity-cluster-to-new-vCenter/td-p/7099161

Well not with me.

As suggested I have disconnected the Simplivity hosts running 4.1.0U1 from the old vCenter (ver 6.5) and connected them to the new vCenter (ver 7.0.3a) ... no issues there!

Now for the dsv-update-vcenter....

It connects ... It gets the certificates ... Yes I do acceept them ...

I enter the password to the administrator@vsphere.local ... the correct one

Aaand it fails with the descriptive error of:
Verifying credentials ...
Successfully verified credentials with the vCenter
Updating authentication information for xxxxx.xxx.xx ...
Failed to update authentication information for rxxxxx.xxx.xx:
Error 0, Failed to validate and save vCenter credential, please check the input.

I have seen the following advisory from HPE:
https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=emr_na-sv7322en_us

but it does not seem to apply.

the $SVTLOG shows nothing, zipo zilch and nada

Does anybody have an idea how to proceed?

I have also opened a case with HPE ...

[support_s]

System recommended content:

1. SimpliVity - Upgrade fails due to Incorrect Omnistack Certificate

If the above information is helpful, then please click on "Thumbs Up/Kudo" icon.

Thank you for being a HPE community member.

[AleksandarPeev]

Hi,

I am not running an upgrade ...
It is just a "simple" vcenter repoint ...

[gustenar]

@AleksandarPeev 

If your password contains special characters, try using the --password parameter in the command and add the password in quotes.

[AleksandarPeev]

Hi @gustenar 

I was on a call with support ....

adding it in quotes did not help.

Apparently creating a user in vCenter with a simpler password that has a . as the required special character adds the connects the OVCs to a vCenter 6.5 but not to a vCenter 7.0.3a

It could be due to unsupported SSL/TLS protocol suites ...

I am ad this point a bit miffed.

Miffed that I chose to use vCenter 7.0.3a ...

Because HPE say ... Tough luck ! It is unsupported.

If anybody has new ideas I would be open to some.

And they say Omnistack 4.1.1 is just around the corner ... I hope that one can actually handle complex passwords from the input line.