Skip to main content
Hi Community, I am trying to configure an RHV server, after entering the credentials I get this message:

 

Failed to add cluster: Failed to register cluster - Failed to register cluster - Value cannot be null. (Parameter 'key')

Value cannot be null. (Parameter 'key')

 

Regards

 

Hi @tavoli -

This is more of a Community site for Veeam, not really for varous hypervisors. Maybe someone has some experience with RHV and can assist. But, have you looked at RHV documentation or user forums?


Are you trying to add RHV to Veeam, or something else? Your post isn’t quite clear of what you’re doing. I assumed initially you’re just trying to install/configure RHV. Please share what specifically you’re attempting to do.

Here’s RedHat’s docs on installing a Cluster on RHV:

https://docs.redhat.com/en/documentation/openshift_container_platform/4.4/html/installing_on_rhv/installing-on-rhv#installing-rhv-default


I want to add the RHV hypervisor to Veeam, it's a question about Veeam, I searched and didn't find anything, that's why I'm asking if anyone has already experienced it.

Ah, ok. Thanks for clarifying @tavoli . Let me see if I can find anything to help you out.


@tavoli - have you looked at Veeam’s OLVM/RHV Guide?

https://helpcenter.veeam.com/docs/vbrhv/userguide/add_rhv_manager.html?ver=41

Also, one of our Community members/Veeam Legends, created a walkthrough of OLVM/RHV. Have you looked at it to see what you may have missed? 

Sadly, I also have not been able to find anything on the error you’re getting when adding OLVM/RHV to Veeam. 


@tavoli -

I assume you created a RHV Cluster according to either of the following 2 articles, before trying to add to Veeam?

https://docs.redhat.com/en/documentation/red_hat_virtualization/4.4/html/administration_guide/chap-clusters#Creating_a_New_Cluster

https://docs.oracle.com/en/virtualization/oracle-linux-virtualization-manager/admin/admin-admin-tasks.html#unique_99476967

If so, and you’re still getting the above error, it may be worth reaching out to Veeam Support.


Comment