-
Notifications
You must be signed in to change notification settings - Fork 46
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
Support Whonix 17 #938
Support Whonix 17 #938
Conversation
Tested again (with rpm built from 9fa6c15):
|
(This is another example of where it would be good to have clean CI environments - unless we include salt logic to remove the whonix-17 templates, they're now already present on the runner.) |
Agreed, the test failing is a red herring and is because the old template is still being used. Just downloaded the prod templates and they do have |
Specify whonix template version and use qvm.template_installed to ensure it is present. Update migration flag and vm_tests.
8691907
to
ac9eb2f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving based on previous test results, visual inspection post-rebase.
Status
Ready for review
Description of Changes
Fixes #934
Towards #937
Changes proposed in this pull request:
Testing
Upgrade scenario (Qubes 4.1, no whonix-17 templates installed)
sdw-admin --apply.
apply
completes successfully; anon-whonixdom0
tests pass (relevant ones: sd-whonix template iswhonix-gateway-17
, kernelopts for sd-whonix and whonix templates show apparmor enabled)Other scenarios (eg templates already downloaded)
apply
completes successfullyDeployment
Any special considerations for deployment? Consider both:
Checklist
If you have made changes to the provisioning logic
make test
) pass indom0
If you have added or removed files
MANIFEST.in
andrpm-build/SPECS/securedrop-workstation-dom0-config.spec
: n/aIf documentation is required