Support for Ubuntu 20.04 (Focal) #4768
Comments
|
Moving to Bionic for internal tooling also unlocks goodness like an up-to-date version of dh_virtualenv, with support for explicitly-set build package versions. |
|
Perhaps we should consider enforcing v3 as part of the Bionic switch. We'll have to do a lot of outreach related to this upgrade, and having admins change the .onion address as part of an upgrade or reinstall seems like a good way to get everyone over the hump. This would also give us a clear date we can communicate to the Tor team by which we know that v2 is no longer supported for SecureDrop, which they could use for end-of-life planning (i.e. April 30, 2021, the EOL date for Ubuntu Xenial). |
|
Recap of discussions today:
We're not planning to transition to a different server OS this time around, but if we can get all the way to 20.04, this will buy us some headroom to have that conversation if/when we focus on making major server-side/admin improvements. I will update this issue's description and start organizing into an epic before the next sprint. [*] My view: We should remove v2 support by April 30, 2021, and issue prominent deprecation warnings well before then. This will IMO simplify messaging to admins of v2 instances. That said, we all agreed that the final timetable should be informed by the rate of v3 adoption in the real world. |
|
We have a longstanding PR to reduce the retention of Apache logs to 30 days (#3714). This is a candidate for rolling into the OS upgrade release, since running the upgrade will require a playbook run anyway, so we can avoid using postinst to update existing configurations. |
eloquence
changed the title
@zenmonkeykstop will take a stab at this one during the 6/24-7/8 sprint, time-boxed to 8 hours.
@kushaldas will take this one, also time-boxed to 8 hours. |
|
NOTE: On going work. The goalWe should be able to build SecureDrop packages using Update Makefile/devops scriptThe This means, we should have a Major point to remember, I need Building the container
In the same focal container image I installed all the other dependencies, and Next, I modified the Updating the SecureDrop package related filesdiff --git a/install_files/securedrop-app-code/debian/securedrop-app-code.triggers b/install_files/securedrop-app-code/debian/securedrop-app-code.triggers
index d12cc4e54..8962f21aa 100644
--- a/install_files/securedrop-app-code/debian/securedrop-app-code.triggers
+++ b/install_files/securedrop-app-code/debian/securedrop-app-code.triggers
@@ -1,7 +1,7 @@
# Register interest in Python interpreter changes; and
# don't make the Python package dependent on the virtualenv package
# processing (noawait)
-interest-noawait /usr/bin/python3.5
+interest-noawait /usr/bin/python3.8
# Also provide a symbolic trigger for all dh-virtualenv packages
interest dh-virtualenv-interpreter-updateNow, CFFI python source fails to compile with errors like following. Updates cffi to 1.14.0 and argon2-cffi to 20.1.0 Next error: dh_virtualenv: not found\nmake[1]:. So, let me try to repackage once again. root@2f7a74b349e9:~/packaging/dh-virtualenv-1.1# sudo apt install python2-minimal dpkg-source -x dh-virtualenv_1.1-1.dsc Not sure why it still says --python=/usr/bin/python3.5 as I updated it to python3.8 |
naive do-release-upgrade from xenial to bionic, prod NUC5ssummary
notesfresh prod install ,ssh over tor, v3 only, also nucs, following the procedure for 14.04->16.04 as closely
On app (
|
|
@kushaldas Regarding the
|
|
It looks to me like version 1.2 which just came out four days ago may be Python3-ready: So perhaps just a matter of using that version? In any event, for the 7/8-7/22 sprint, @kushaldas will continue the packaging journey to see if we can unblock that part of the process, one way or another. |
|
As a quick note: I finally have |
|
@kushaldas Great news! I'd love to take a look at your WIP—mind pushing a branch and documenting here? |
|
Steps: Go inside of First download dh-virtualenv from Sid
Then, from the main directory,
https://github.com/freedomofpress/securedrop/tree/on_focal this is the branch. |
|
@kushaldas Following the steps you provide, I'm able to build packages. I've tacked on a commit that performs the dh-virtualenv-from-sid step inside the dockerfile. The purpose of the |
|
I pushed a few more updates related to Python3.5 to Python3.8. The package installation fails with the following details In our post-installation of the debian package, we execute this following command. And this is creating wrong configuration as shown below. But, the real path for the Maybe updating I also noticed the following error: |
|
We won't be directly working on this during the 7/23-8/5 sprint, but we'll aim to:
Keeping this ticket on the sprint to track those commitments. |
|
I updated my
|
|
FYI: I've made Edit: Added Xenial and Bionic to the list |
eloquence
changed the title
|
Hello guys, Anything I can help you with to speedup official support of 20.04 LTS for securedrop? Looking forward to help |
|
@dkorzhevin Sorry, I missed your note on this issue. We would absolutely appreciate your contributions; given the scope and complexity of this issue, it might be easiest to chat in real-time about how to best get involved, e.g. on https://gitter.im/freedomofpress/securedrop or in our virtual standups Mo-Thu at 9AM PST / 5 PM UTC (announced on Gitter). |
|
It is a good thing that we are not doing in place upgrade of the servers, https://bugs.launchpad.net/ubuntu/+source/libxcrypt/+bug/1903838 |
|
Closing this epic:
|
Description
Ubuntu 16.04 (Xenial) is the Ubuntu LTS release that is currently supported for SecureDrop and it will be supported until April 2021.
This issue tracks support for Ubuntu 20.04 (supported until April 2025).
Subtickets
Completed
do-release-upgradeto Ubuntu 18.04, try to unbreak, see where you get stuck, documentfocalbuilder image to quay (@conorsch) - Adds initial builder-focal molecule scenario #5444 (comment)build-debs-focalMakefile target Addmake build-debs-focaltarget #5454 Adds initial builder-focal molecule scenario #5444make fetch-tor-debsto pull both xenial and Focal tor debs Add Focal support tofetch-tor-packagestarget #5481mod_wsgishared library path error Creates a symlink to the .so file in postint for mod_wsgi #5443make staging-focaltarget make staging-focal for a Focal based staging environment #5468paxctlerror on Focal Focal staging paxctl command to convert grub binaries are failing #5495make-build-debs-focaltest Run Focal debs tests in CI #5494platform.linux_distributionfuntion call in Python 3.8 #5433test_submit_messageandtest_submit_filefailure on Focal test_submit_message and test_submit_file failure on Focal container #5592testinfratests against Focal staging. Enable testinfra tests against Focal staging #5509 Add staging-with-rebase-focal to CI and fix testinfra tests #5638cron-aptto unattended upgrades Use unattended-upgrades instead of cron-apt #5295security-only vs. all updates frommain)CI work
Post migration
Deferring for next OS upgrade or other major release
Pending discussion
The text was updated successfully, but these errors were encountered: