Restart required after applying Ultimate license
Summary
Restart required after applying Ultimate license
Steps to reproduce
- Install ultimate license to GitLab instance
- Wait for instance license expire
- Apply new license to instance
- Requires restart of services
Example Project
What is the current bug behavior?
Currently, a restart is required after applying a new license. This introduces downtime.
What is the expected correct behavior?
A restart should not be required after applying a new license. The instance should gracefully apply the license without additional intervention.
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)