GitLab use the previous license instead of the newest license on the system after upgrading
Summary
After customers upgrade their Self-Managed GitLab instance, the system activates the previous license instead of the newest license on installed.
Steps to reproduce
- Have a license installed that's close to license end term
- Renew the license and install on the system (the old license is still valid)
- Upgrade the system
- When the instance restart, observe that the previous license is loaded instead the latest
- The renewed license get activated at the start date
Example Project
(If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report)
(If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version)
What is the current bug behavior?
Confusing license switch. The new license was able to upload but the system choose the previous one upon upgrade.
What is the expected correct behavior?
One of the below:
- License with future start date should not be uploaded successfully.
- License with future start date can be uploaded successfully, and the system provide banner or information that the license will be automatically activated on the start date; and the old license display banner informing that customer has
Users over license
but it will be reset with the new license
Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise.)
Output of checks
Customer upgraded to GitLab 13.0.1
Possible fixes
(If you can, link to the line of code that might be responsible for the problem)
Workaround
Restart the system