Solve Aleph VMs automatic restarts #750
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Confidential VMs are restarted automatically
Related ClickUp, GitHub or Jira tickets : ALEPH-383
Self proofreading checklist
packaging/Makefile
Changes
Problem: On Ubuntu 24.04 OS version, a new service called
needrestart
restart some services automatically and this also resets some confidential VMs that cannot init again as we don't store the password key.Solution: Add a rule on
needrestart
service to skip the restart on aleph services.How to test
Install the version on a CRN with some instances inside and do a manual package update.