hello there!
i've noticed the exact same issue! but its not related to workgroup-cluster.. this is also on a domain-joined cluster! (even MS "supports" live-migration in workgroup now (it even worked before with some tricks) i wouldn't recommend a workgroup-cluster... microsoft don't write thit in the same docs, but don't having it domain joined also breaks a lot of other things... foremost the cluster-aware-updating for example... but this is all a different story)
i was able to add the domain-joined nodes individually, but can't add the cluster node!
have a support case open on this:
07831539
you can also find something about the error in the logs, but nothing to helpfull:
Code: Select all
output:
[26.09.2025 13:37:57.362] <08> Error (1) stdout: instance of OMI_Error
[26.09.2025 13:37:57.362] <08> Error (1) {
[26.09.2025 13:37:57.362] <08> Error (1) OwningEntity=OMI:CIMOM
[26.09.2025 13:37:57.362] <08> Error (1) MessageID=OMI:MI_Result:1
[26.09.2025 13:37:57.362] <08> Error (1) Message=Kerberos verify cred with password failed No credentials were supplied, or the credentials were unavailable or inaccessible
[26.09.2025 13:37:57.362] <08> Error (1) MessageArguments={}
[26.09.2025 13:37:57.362] <08> Error (1) PerceivedSeverity=7
[26.09.2025 13:37:57.362] <08> Error (1) ProbableCause=117
[26.09.2025 13:37:57.362] <08> Error (1) ProbableCauseDescription=Kerberos verify cred with password failed No credentials were supplied, or the credentials were unavailable or inaccessible
[26.09.2025 13:37:57.362] <08> Error (1) CIMStatusCode=1
[26.09.2025 13:37:57.362] <08> Error (1) OMI_Code=1
[26.09.2025 13:37:57.362] <08> Error (1) OMI_Category=0
[26.09.2025 13:37:57.362] <08> Error (1) OMI_Type=MI
[26.09.2025 13:37:57.362] <08> Error (1) OMI_ErrorMessage=A general error occurred, not covered by a more specific error code.
[26.09.2025 13:37:57.362] <08> Error (1) }
[26.09.2025 13:37:57.362] <08> Error (1) stderr: /opt/veeam/vbr/omi/omicli: result: MI_RESULT_ACCESS_DENIED
there is also a commandline displayed what veeam is trying todo:
Code: Select all
client options: Options { ToolPath = /opt/veeam/vbr/omi/omicli, AddressOrHostname = 172.22.240.220, UserName = backup-service, UserDomainName = domain, PasswordProvider = System.Func`1[System.String], LogInhibition = False, ConnectionTimeoutSeconds = 3600, Port = 5985, EncryptionType = Http, AuthType = Kerberos }
[26.09.2025 13:37:57.362] <08> Error (1) command line: /opt/veeam/vbr/omi/omicli wql root/cimv2 'SELECT Version FROM Win32_OperatingSystem' --hostname HVCluster --port 5985 --encryption http --auth Kerberos -u backup-service@domain -pi
you'll see the port 5985 there... basically its winRM...
support told me to test with wbemtest tool, if i can connect to the cluster... and yes in my case its working as expected... allthough the cluster WMI space is somewhat secured, because as soon as i trying to connect this wmispace and make querys i get a warning in eventlog that this is only supported with encryped querys... not sure how to test this..
anyway. i've also tested with "invoke-command clustername" with kerberos and the service account, this is also working in my case...
today i also tested to add the v13-vsa to the domain (this can be done in the host mgmt interface) but also doesn't change the behaviour!
it even doesn't matter what user you choose, it fails before it checks the user i think!