New Federation Deployment 4.2 - Fails Step 10 Resignaturing

[alg204]

Hello!

We have an HPE engagement to create a new stretched cluster with 4 nodes, simplivity 4.2.

3 nodes deployed fine but the 4th keeps failing at step 10 - specifically the resignaturing portion. 

Error Message
ERROR: Step 10 of 43: ERR_DPLY_CAUGHT_EXCEPTION_RESIGNATURING_ESXI_STORAGE: An exception occured while resignaturing the ESXi Storage. 

Our HPE Deployment tech found a time issue with the node and fixed that. cleared the raid and reconfiged the raid. Then did the tiny image of 4.2. From there, tried deploying again and it failed again at the same spot. 

Anyone seen this? 

Only step 10 issue I've seen on the forum is waiting for reboot but we get passed that part of step 10 just fine.

[Steven Clementi]

4.2 is too new for me to comment on, but if you have time to play around... try deploying a single node cluster using the 4.1.3 bits... see if the node stops at the same spot.  It might be an invisible hardware issue.

It won't help get you to your desired configuration since you would need to re-deploy the node again, but it could help in troubleshooting.

If you weren't so far along I would suggest deploying the entirecluster on 4.1.3, then upgrading to 4.2.0..

[Aditya_A · Accepted solution]

Hi,

Is there any IP on the DCUI showing up as 16.1.15.2 or anything apart from the permanent ESXi management IP?
If so, iLO virtual NIC would need to be disabled.

Could you check the failed node once and let me know?
Moreover, you can ask the team you're working with to attempt a factory reset using full image.

[alg204]

Hi!

We finally got the 4th node deployed. Using a USB with full image did the trick.

[Sunitha_Mod]

Hello @alg204,

That's great! 

We are glad to know your concern has been addressed. 

[DavS]

@alg204 

alg204,

What fiile did you use for the full image?

Thanks.