Query: OneView for VMware vCenter problem registering HPE OneView Service Packs

[umoperating]

Hello,

VMware: 8.0.3 (latest)
OneView:  9.30.00-0502470 (latest)
OneView for VMware vCenter (OV4VC): 11.6.0.4 (latest)

We are using Standard OneView (without license).

All connections are setup and working:
- vCenter and all ESXis (all Gen10) added to OneView -> check
- OneView added to OV4VC -> check
- vCenter added to OV4VC -> check

As I currently have no Root CA available all involved certs are self-signed certs (vCenter, OneView, OV4VC). The cert of OV4VC was created under Certificate Management (in OV4VC in vCenter). It is using the correct FQDN. The OV4VC cert was successfully added to the vCenter trust store.

I can see all available SPPs which are present in OneView in OV4VC. However, when I try to register an official SPP or a custom SPP (tried both) I always get:

Online software depot registration failed. Please check HPE OneView for VMware vCenter certificate is added into vCenter trust store. If the problem persists, please contact technical support.

Can someone give me a hint, what the actual problem is?

Thanks a lot in advance.

[support_s]

System recommended content:

1. HPE OneView for VMware vCenter 10.4 User Guide | Adding the HPE OneView for VMware vCenter certificate to vCenter trust store

2. HPE OneView for VMware vCenter 10.3 User Guide | Revoking the HPE OneView for VMware vCenter certificate from vCenter trust store

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[umoperating]

Hello,

of course I read the official documentation but it does not help (as said the OV4VC cert is correctly imported in vCenter trust store). 

I still have this problem. Is there some kind of log where this is addressed?

Maybe someone from HPE can jump in here and bring some clarity.

Regards

[Rama2]

Please verify if a proxy server is in use in your environment. If so, it is essential to configure the NO_PROXY settings correctly to exclude the following components:

HPE OneView, OneView for VMware vCenter (OV4VC) and  vCenter Server

For detailed guidance on configuring proxy settings for vCenter, please refer to the following Knowledge Base article:

How to Configure Proxy Settings for vCenter Server :- https://knowledge.broadcom.com/external/article/370265/how-to-configure-proxy-settings-for-vcen.html

This article includes step-by-step instructions to help you apply the necessary exclusions.

if you still face any issues raise a support ticket with HPE for further assistance 

[umoperating]

Hi,

thanks for your reply @Rama2.

There is no proxy configured on this vCenter setup. So, this does not apply. 

Oneview is connected to OV4C correctly but it cannot register the SPPs. That alone is quite strange as it obviously can reach OneView. Only the registering does not work. And there is no way to get a more detailled log or something. It is just saying that "Online software depot registration failed." I am very disappointed by this OV4VC <-> OneView experience.

I will try to open a Support ticket. But as we use the free version (so, no license) I don't know if someone is willing to help me.

When I have a meaningful answer I will post it here. 

[RenjuCR]

Can you provide more information regarding your OV4VC version and which version of SPP is failing to get registered?

[umoperating]

Hello @RenjuCR,

we use the following versions:

VMware vCenter: 8.0.3.00500
VMware ESXi (on HPE Gen10 ProLiant DL380): 8.0 U3e - 24674464
VMware Vendor Addon: HPE Customization for HPE Servers 803.0.0.11.9.0-7
OneView:  9.30.00-0502470 
OneView for VMware vCenter (OV4VC): 11.6.0.4

So, afaik these are the latest versions currently.

The SPPs I try to register are:

- Official SPPs:
  - Gen10 Service Pack for ProLiant-2025.01.00.00 (Version 2025.01.00.00)
  - Gen10 Service Pack for ProLiant-2024.11.00.00 (Version 2024.11.00.00)

Custom SPP: test_gen10_spp_202411-2024.11 (based on Version 2024.11.00.00)

For none of them the registration works.

Regards

[RenjuCR]

To verify that the online depot registration was successful, navigate to Menu > Lifecycle Manager > Settings > Administration > Patch Setup. 

Our QA team has not observed any issue with the mentioned configuration.

Please raise a support ticket and provide the logs to our team for further debugging on this issue.

[umoperating]

Hello @RenjuCR ,

thanks for your message.

I checked it and it still does not work. I always get this OV4VC certificate error although it is added to vCenter trust store.
I checked also if it was registered although there is this error and the SPPs are not shown there (as expected).

What logs do you mean? I asked several times for a more meaningful error message in logs somewhere. I got no answer.

I will create a support ticket.

Regards

[RenjuCR]

Support ticket would help as this might be an issue with configuration, so that our team can guide you in the right direction. 

[umoperating · Accepted solution]

Hi,

I created a support ticket but of course I was directly asked for valid license/support contract. So, no help from the official support.

However in the meantime I solved the issue by myself. The problem was the self-generated certificate in OV4VC itself. When this is used only the certificate for port 3512 is changed not the 443 certificate and this leads to this problem.

I fixed it by re-deploying the whole OV4VC VM. With the delivered certs it is working. Then 3512 and 443 are using the same certificate and the registering works immediately.

So, in case you want to use self-signed certs just don't touch them after installation of OV4VC. Leave the default ones installed.

This thread is solved and will be closed.

[RenjuCR]

We are happy to hear that your issue got resolved.