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

Release SecureDrop Workstation 0.5.1 #643

Closed
6 tasks done
eloquence opened this issue Nov 12, 2020 · 4 comments
Closed
6 tasks done

Release SecureDrop Workstation 0.5.1 #643

eloquence opened this issue Nov 12, 2020 · 4 comments

Comments

@eloquence
Copy link
Member

eloquence commented Nov 12, 2020

The next version of the SecureDrop Workstation will enforce the use of fedora-32 as the default for sys-* VMs due to its EOL. This issue tracks this and any other release-critical issues, the QA process, and the release itself.

  • Land fedora-32 support (Use fedora-32 for sys-* VMs #627)
  • Update changelog
  • Create test plan
  • Prepare test package for yum-test
  • Complete QA
  • Production release and comms
@conorsch
Copy link
Contributor

Added a test plan here: https://github.com/freedomofpress/securedrop-workstation/wiki/0.5.1-Test-Plan

Given that F32 has received upstream fixes to resolve the salt breakage, upgrades are now possible via the GUI updater.

@eloquence
Copy link
Member Author

Went through a fresh install attempt today; provisioning failed due to #644 (see output in https://gist.github.com/eloquence/d29ba85df5153e9d09c328db3a6d00b4). Will reset to clean slate and retry after fix lands in apt-test.

@zenmonkeykstop
Copy link
Contributor

Ran through upgrade testing, successfully with no issues:

Scenario: in-place upgrade

  • Install prod 0.5.0 on dedicated hardware
  • Clone the securedrop-workstation repo to dom0
    • Edit utils/qa-switch.sh to include "sd-large-buster-template" and "sd-small-buster-template" in the list of targets
    • Rhen run sudo bash utils/qa-switch.sh to set the yum-test repos
  • Confirm that qvm-ls | grep fedora-32 shows no hits
  • Run the GUI updater via time /opt/securedrop/launcher/sdw-launcher.py --skip-delta=0 and confirm no errors
  • In dom0, run qvm-ls | grep fedora-32, and verify that:
    • sys-firewall, sys-net, and sys-usb are all based on fedora-32
    • sd-app, sd-log, sd-proxy, and sd-gpg are based on sd-small-buster-template
    • sd-devices-dvm and sd-viewer are based on sd-large-buster-template
  • Confirm qvm-prefs default-mgmt-dvm template shows fedora-32
  • Run the graphical updater again to completion, confirm no errors

@eloquence
Copy link
Member Author

eloquence commented Nov 24, 2020

This was completed last week. During testing, we discovered a regression in the dom0 update logic that was introduced in 0.5.0 (#646) and fixed via a follow-up release, 0.5.2, issued today.

SecureDrop Team Board automation moved this from SecureDrop Sprint #63 - 11/12-11/25 to Done Nov 24, 2020
@eloquence eloquence unpinned this issue Dec 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
Development

No branches or pull requests

3 participants