Nomad 0.12.0 enterprise does temporary license expiration bug on upgrade

[schmichael]

Nomad version

v0.12.0+ent

Issue

Enterprise Nomad users are intended to have 6 hours from first using Nomad v0.12.0 to apply their license. Unfortunately there is a bug in time calculation: the time is calculated from cluster creation, so existing Enterprise users will be treated as if their 6 hour temporary license has already expired.

Luckily there is a short grace period during which a license can be applied. This grace period is just on the order of minutes, so it's a far more stressful operation than was originally intended.

Reproduction steps

1. Run Nomad for > 6 hours
2. Upgrade to Nomad v0.12.0+ent
3. Observe the warning about your license being expired
4. Rush to obtain and apply a license before expiration

[github-actions]

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.