Message: The Fleet lifecycle 'Component import' task with ID <task id> failed. Internal errors: An unexpected error occurred in step discover_vrni_component_task_ref. Reference Code: 6F30FB09. Please contact support with this reference code. Detail: I/O error on POST request for "https://<IP>:443/api/auth/login": Certificate for <IP> doesn't match any of the subject alternative names: []Unable to register components with VCF Operations.To fix this, the VCF Operations for Networks Platform appliance(s) need to be updated with valid certificates containing IPs in SAN fields of certificates, via a script.
Script filename: rotate_vrni_certs.shSize: 47 KBMD5 Checksum: 4c9cb0e1dfff5db58f8179fd39ba0ded
Stop the Upgrade If VCF Operations for Networks upgrade was triggered in VCF Operations Fleet Manager leading to the error, then the upgrade must be stopped and stale legacy data cleared prior prior to rotating the certificates.
If manually importing VCF Operations for Networks prior to starting the upgrade, these steps may be skipped.
Rotate the Certificates
rotate_vrni_certs.sh.rotate_vrni_certs.sh to the platform node under the /home/support directory. Use a tool such as WinSCP to the platform node and login with username support to transfer the file./home/support directory.ls -lrth sudo md5sum rotate_vrni_certs.shverify parameter to verify if the current VCF Operations for Networks certificate needs to be replaced:sudo bash ./rotate_vrni_certs.sh verify
Note: The results will be either OK or ERROR[OK] All platform certificates are valid. No rotation needed. [ERROR] Certification rotation is required on one or more nodes.
Could not resolve IP for nodeThis script verifies based on the aliases "platform1", "platform2", "platform3", not through FQDN. This should be resolvable through localhost as per the /etc/hosts file.
Re-run the script using the apply parameter to rotate the certificate.
If using a CA-signed certificate:
Run the following command to verify the current SAN entries:
openssl s_client -connect localhost:443 | openssl x509 -text -noout | grep -A 1 "Subject Alternative Name"
If the IP address is missing or listed as a DNS: entry, regenerate the certificate.
Ensure the new certificate includes the FQDN as a DNS entry and the IP address as an IP Address entry in the SAN field.
Copy the certificate, private key and CA chain files to the platform node where the script is being run and execute the script per the following syntax:
sudo bash ./rotate_vrni_certs.sh apply --cert <certificate-pem-file-path-here> --key <private-key-pem-file-path-here> --ca-chain <ca-chain-pem-file-path-here>
If using a self-signed certificate, the script can create a new self-signed certificate and update VCF Operations for Networks to use it.
sudo bash ./rotate_vrni_certs.sh apply --self-signed
Note: Output similar to the following should be returned:[OK] Certificate rotation completed successfully on all nodes!
Complete the Import of VCF Operations for Networks If VCF Operations for Networks upgrade was triggered in VCF Operations Fleet Manager leading to the error, then the following step must be taken to complete the import of VCF Operations for Networks as part of the upgrade.
If manually importing VCF Operations for Networks prior to starting the upgrade, simply re-try the import in the GUI and do not follow the steps below.
Subscribe to this knowledge article to get updates on this issue/ KB.