-
Notifications
You must be signed in to change notification settings - Fork 696
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
make-vagrant package fails to build upgrade boxes #4854
Comments
Further issues when building with v3 onion services:
I suspect this is because the role path is overriden [1] for in the vagrant-builder scenario, and this path is used to lookup the keys in the playbook when setting up v3 services[2]: [1]
[2] Line 69 in 9f32d46
whereas the tor hidden services files are generated in the securedrop root directory: Line 56 in 9f32d46
|
Description
Steps to Reproduce
Expected Behavior
The vagrant box should be built successfully
Actual Behavior
Fails at
common : Remove generic kernel packages
:Comments
This is because the
common
role is run before thegrsecurity
role in the upgrade boc building playbook:https://github.com/freedomofpress/securedrop/blob/develop/molecule/vagrant-packager/playbook.yml#L17
The production and staging playbooks run grsecurity before common.
https://github.com/freedomofpress/securedrop/blob/develop/install_files/ansible-base/securedrop-prod.yml#L54
inverting the order in vagrant-packager resolves locally
The text was updated successfully, but these errors were encountered: