Closed zenmonkeykstop closed 2 years ago
2.3.2-rc1
2.3.1
../securedrop-admin verify
are passing:
cd ~/Persistent/securedrop && ./securedrop-admin setup -t
./securedrop-admin verify
(this will take a while)rm -rf admin/.venv3/ && ./securedrop-admin setup
Exceptions:
FAILED common/test_automatic_updates.py::test_automatic_updates_dependencies[paramiko:/mon]
FAILED common/test_automatic_updates.py::test_cron_apt_config[paramiko:/mon]
FAILED common/test_automatic_updates.py::test_unattended_upgrades_functional[paramiko:/app]
After updating to this release candidate and running securedrop-admin tailsconfig
Except for securedrop-admin verify
failures logged above.
perform a manual upgrade using a Tails 5.0 reference USB
[x] reboot the admin workstation and verify that the upgrade completed successfully and the persistent volume is available
[x] run cd Persistent/securedrop && ./securedrop-admin tailsconfig
and verify that an error message indicating that a Tails 4 virtualenv was detected and deleted is displayed
[x] run ./securedrop-admin setup
and verify that it completes successfully
[x] verify that the clean install cases above complete successfully
[x] ./securedrop-admin setup completed successfully
[x] apt-cache policy ccontrol shows that ccontrol is not installed
[x] the admin sdconfig, install, and tailsconfig commands completed successfully
[x] the servers are accessible over ssh and the SI and JI are available via desktop shortcuts
[x] backup and restore work correctly
[x] the JI and SSH services are still available after restarting the network connection.
For application testing, repeated only those cases involving the Admin Workstation:
./securedrop-admin verify
are passing:
FAILED common/test_automatic_updates.py::test_all_packages_updated[paramiko:/app]
FAILED common/test_automatic_updates.py::test_unattended_upgrades_functional[paramiko:/mon]
FAILED common/test_automatic_updates.py::test_all_packages_updated[paramiko:/mon]
FAILED common/test_automatic_updates.py::test_unattended_upgrades_functional[paramiko:/app]
...
...
[x] Can successfully add journalist account with HOTP authentication
restart the network connection
Yup, and breaks the 2.3.2-rc1
virtualenv! ;-) Required to recover:
amnesia@amnesia:~/Persistent/securedrop$ rm -rf admin/.venv3
amnesia@amnesia:~/Persistent/securedrop$ git checkout 2.3.2-rc1
amnesia@amnesia:~/Persistent/securedrop$ ./securedrop-admin setup
amnesia@amnesia:~/Persistent/securedrop$ ./securedrop-admin tailsconfig
Then a network bounce triggers the SecureDrop Updater prompt as expected.
./securedrop-admin verify
are passing:
cd ~/Persistent/securedrop && ./securedrop-admin setup -t
./securedrop-admin verify
(this will take a while)rm -rf admin/.venv3/ && ./securedrop-admin setup
After updating to this release candidate and running securedrop-admin tailsconfig
On the admin workstation with the 2.3.2 rc code deployed, verify that:
cd Persistent/securedrop && ./securedrop-admin tailsconfig
and verify that an error message indicating that a Tails 4 virtualenv was detected and deleted is displayed./securedrop-admin setup
and verify that it completes successfully./securedrop-admin verify
are passing:
cd ~/Persistent/securedrop && ./securedrop-admin setup -t
./securedrop-admin verify
(this will take a while)rm -rf admin/.venv3/ && ./securedrop-admin setup
After updating to this release candidate and running securedrop-admin tailsconfig
On the admin workstation with the 2.3.2 rc code deployed, verify that:
Tested preflight upgrade scenario against 2.3.2 prod packages:
apt-qa.freedom.press
per preflight procedure)
This is a tracking issue for the release of SecureDrop 2.3.2
Tentatively scheduled as follows:
Pre-release announcement: 2022-05-03 Release date: 2022-05-05
Release manager: KOG Deputy release manager: TBD Communications manager:: TBD (As this is a hotfix release with no translated string changes, no LM is assigned.)
SecureDrop maintainers and testers: As you QA 2.3.2, please report back your testing results as comments on this ticket. File GitHub issues for any problems found, tag them "QA: Release".
Test debian packages will be posted on https://apt-test.freedom.press signed with the test key. An Ansible playbook testing the upgrade path is here.
QA Matrix for 2.3.2
Test Plan for 2.3.2
Prepare release candidate (2.3.2~rc1)
2.3.2~rc1
on test apt serverAfter each test, please update the QA matrix and post details for Basic Server Testing, Application Acceptance Testing and release-specific testing below in comments to this ticket.
Final release
release
branch in the LFS repo)release
branch in the LFS repo for the debs)main
in the LFS repo)main
and verify new docs build in securedrop-docs repoPost release
securedrop-docs
and Wagtaildevelop