Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add dependency between nova-compute and vaultlocker #10

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

rodrigogansobarbieri
Copy link
Contributor

If vaultlocker fails to decrypt and mount
/var/lib/nova/instances, nova will start anyway
and may create instances with their disks on the
root filesystem's disk, which may not be encrypted.

This patch creates a dependency between the nova-compute
and vaultlocker services, so if vaultlocker fails
nova-compute will not be started.

Closes-bug: #1863358

If vaultlocker fails to decrypt and mount
/var/lib/nova/instances, nova will start anyway
and may create instances with their disks on the
root filesystem's disk, which may not be encrypted.

This patch creates a dependency between the nova-compute
and vaultlocker services, so if vaultlocker fails
nova-compute will not be started.

Closes-bug: #1863358
@javacruft
Copy link
Contributor

I think this specialises vaultlocker towards nova-compute to much.

Would an alternative approach be to use overrides on the nova-compute systemd configuration to ensure that it runs after the required vaultlocker units have been started successfully?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants