the number of virtual machines that the operation would start.
Cause. Powering on the virtual machine would take the number of running virtual machines over the limit of the effective licence. Powered-on, paused and suspended virtual machines count; powered-off virtual machines and templates do not.
Remedy.
Power off virtual machines that are not needed: kyvernon vm power-off <id>.
Or install a licence with a higher limit: kyvernon licence install <payload> <signature>. In the console, use Install licence.
Check the counters: kyvernon licence show. The console shows them under Running virtual machines.
error.licence.limit_hosts
Text in the console
Enrolling a host would exceed the host licence limit ({current} of {limit}; requested {delta}). Remove a host or install a multi-host licence.
Meaning for API clients
Enrolling a host would exceed the host licence limit.
Cause. The operation needs a licence feature that the effective licence does not include. The features are cluster, ha, live_migration, remote_storage.nfs, remote_storage.iscsi and remote_storage.ceph.
Remedy.
Check which features are enabled: kyvernon licence show. In the console, see Features.
Install a licence that includes the feature: kyvernon licence install <payload> <signature>.
Or choose an operation that the current licence covers, for example a datastore on local storage.
error.licence.signature_invalid
Text in the console
The licence file signature is not valid. Check that you pasted the complete payload and signature.
Cause. The signature of the licence file does not match the payload, or was made with a key that this controller does not trust. The payload was changed after signing, or the signature file is incomplete.
Remedy.
Install the payload and the signature exactly as you received them. Do not edit either file. Copy the complete content when you paste it in the console.
Check that the signature file is the one that belongs to the payload.
When it stays, ask the issuer of the licence for a new file. Pass on the licence identifier and the message id.
error.licence.not_valid
Text in the console
The licence is outside its validity window. Check the start and end dates on the licence file.
Cause. The licence is outside its validity window: its start date is still in the future, or its end date has passed. The clock of the controller decides.
Remedy.
Read the start and end dates in the licence file and compare them with the date of the controller.
When the controller clock is wrong, correct it, then install the licence again.
When the licence has expired, ask the issuer for a new one and install it with kyvernon licence install <payload> <signature>.