LicenseUpdateConfirmationDto
Body of the 409 answer that asks for confirmation. Nothing was changed; the same import with confirmDowngrade=true installs the file. The resulting fields describe the pool as it would be afterwards.
{
"errorCode": "string",
"message": "string",
"serialNumber": "string",
"installed": {
"cores": 0,
"validFrom": "string",
"validTo": "string"
},
"incoming": {
"cores": 0,
"validFrom": "string",
"validTo": "string"
},
"reasons": [
"string"
],
"resultingState": "string",
"resultingRestricted": false,
"resultingOverCapacity": false,
"resultingEntitledCores": 0,
"consumedCores": 0
}
Always LICENSE_UPDATE_REQUIRED_CONFIRMATION
Human-readable explanation that confirmation is required
Serial number of the installed license the file would replace
Why confirmation is required; one or both of LOWER_CORES and EARLIER_EXPIRY
Overall console licensing lifecycle state
NO_LICENSE: No license is ACTIVE and none has ever been validNOT_YET_VALID: No longer produced: validFrom is informational, so a license counts from the day it is installed. Kept so clients and the telemetry report still recognise the valueACTIVE: At least one license is ACTIVE and the farthest-expiring one has more than 30 days leftEXPIRING: At least one license is ACTIVE but the farthest-expiring one has 30 days or fewer leftGRACE: No license is ACTIVE although one has been valid before, and the grace period of 7 days after its last valid day has not endedRESTRICTED: No license is ACTIVE although one has been valid before, and the grace period has ended; restricted is true
True when the console would be restricted after the replacement
True when consumed cores would exceed the pool after the replacement
Cores in the pool after the replacement
Cores the registered hosts consume now