I configured a group in which the nodes are set to not be VMs. If I were to run orchestrate on these nodes in generates some incorrect certificates instead of indicating that the node is not a VM. It would be useful to clarify that it's a non-VM node instead of behaving like the certificates haven't been configured on the host yet.
[root@controller [testcluster] ~]# metal orchestrate create compute1
warning: The following returned nil: answer.libvirt_host
The following certificates have been generated, copy them
to the specified remote directory on :
from (local): /var/lib/metalware/certs/-cert.pem
to (remote): /etc/pki/libvirt/servercert.pem
from (local): /var/lib/metalware/certs/-key.pem
to (remote): /etc/pki/libvirt/private/serverkey.pem
Provisioning new storage volume for compute1
error: Call to virConnectOpen failed: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory. Use --trace to view backtrace
I configured a group in which the nodes are set to not be VMs. If I were to run orchestrate on these nodes in generates some incorrect certificates instead of indicating that the node is not a VM. It would be useful to clarify that it's a non-VM node instead of behaving like the certificates haven't been configured on the host yet.