Closed emkll closed 3 years ago
We need someone else than me to reproduce this, on a normal VM based approach can not test secureboot
related checks. Just now finished a normal installation on Focal via release/1.8.1
branch and works perfectly.
I just ran install again and did not observe this error. It's unclear if this is was a transient error or user error :confused:
Just ran through a fresh install (and multiple install playbook runs afterward) on nuc10/nuc8, did not observe this error.
Hardware: 2014 Mac Minis
Server OS: Ubuntu 20.04
Scenario: Fresh install
Commit: 372952c71aa7fd75de297185e9eb0bb135cd89f8 (tip of release/1.8.1
)
The [prepare-servers: Install python and packages required by installer]
step completed without issues on app
and mon
. Will post any other findings from quick testing on main issue.
Closing for now due to failure to reproduce, will re-open if we observe again during next QA cycle or before then.
Description
When performing a new install on the latest
release/1.8.1
branch, the installer fails at the following step:What is strange is that ssh to the app server is still working after that failure.
Steps to Reproduce
./securedrop-admin --force install
on a newly provisioned 20.04 installExpected Behavior
prepare-servers role should complete successfully
Actual Behavior
prepare-servers fails at the "Check SecureDrop status" step
Comments
I tried several things:
~/.ansible/cp/