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

[0.8.0] Add kernel troubleshooting docs #3498

Closed
eloquence opened this issue Jun 5, 2018 · 0 comments
Closed

[0.8.0] Add kernel troubleshooting docs #3498

eloquence opened this issue Jun 5, 2018 · 0 comments
Labels
Milestone

Comments

@eloquence
Copy link
Member

As part of the 0.8.0 release, we are anticipating that we will ship an upgrade from grsecurity-kernel patched kernel version 4.4.115 to 4.4.135 (this will not impact instances with downgraded kernels). This is being done via #3494.

While we don't anticipate new issues with this kernel and will do hardware testing both on officially recommended hardware and on some additional server models, we must provide downgrade instructions to users in case of unanticipated issues that aren't immediately resolvable.

Implementation

For the 0.5 to 0.6 upgrade, we provided extensive kernel troubleshooting docs here:
https://docs.securedrop.org/en/release-0.7/upgrade/0.5.x_to_0.6.html

I suggest adding a generalized version of these instructions to the admin guide, and referencing them in the upgrade instructions for 0.7 to 0.8, instead of duplicating the whole page.

@eloquence eloquence added the docs label Jun 5, 2018
@eloquence eloquence added this to the 0.8 milestone Jun 5, 2018
@eloquence eloquence added this to In Development in SecureDrop Team Board Jun 7, 2018
eloquence added a commit that referenced this issue Jun 8, 2018
These instructions are largely identical to the troubleshooting section
in the 0.5->0.6 upgrade docs, but they do not reference specific
kernel versions.

Resolves #3498
@eloquence eloquence moved this from In Development to Under Review in SecureDrop Team Board Jun 8, 2018
SecureDrop Team Board automation moved this from Under Review to Done Jun 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant