Document: https://github.com/kubevirt/vm-import-operator/blob/master/docs/design.md#vmware-secret-example Description of problem: 1. Please add details on how to fetch the VMware "thumbprint". 2. Emphasize that ":" should separate the numbers and not spaces. This value should be provided as part of VMware Secret: cat <<EOF | oc create -f - --- apiVersion: v1 kind: Secret metadata: name: vmw-secret type: Opaque stringData: vmware: |- # API URL of the vCenter or ESXi host apiUrl: "https://<Vcenter IP address>/sdk" # Username provided in the format of username@domain. username: <username> password: <password> # The certificate thumbprint of the vCenter or ESXi host, in colon-separated hexidecimal octets. thumbprint: 31:14:.. <===== thumbprint EOF Version-Release number of selected component (if applicable): CNV-2.5 Additional info: thumbprint it's the SHA-1 fingerprint of the vCenter's SSL certificate. You could get it from your web browser by clicking the lock in the URL bar and clicking through to the certificate details It needs to be formatted as 31:14:EB:9E etc it will not work with the spaces it would complain of being unable to initialize the provider if the fingerprint was bad
Finding the UUID is pretty much out of scope. A VMware administrator should be able to help. However, I agree that it would be better to explain how to retrieve it, maybe as a note under the example. And I prefer solutions based on command line. Creating a CR is for advanced users, so they should be fine with command line. Here is the openssl command to get it, already in colon-separated hexadecimal octets format: $ openssl s_client -connect esx13.v2v.bos.redhat.com:443 < /dev/null 2>/dev/null | openssl x509 -fingerprint -sha1 -noout -in /dev/stdin | cut -d '=' -f 2
I meant, "finding the thumbprint".
Moving to 2.5.1 as it is an upstream doc RFE.
https://github.com/kubevirt/vm-import-operator/pull/435
Verified on latest master doc: https://github.com/kubevirt/vm-import-operator/blob/master/docs/design.md
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Virtualization 2.5.2 Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2020:5560