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

Graphical updater re-appears, fails after initial run without admin password #4387

Closed
eloquence opened this issue Apr 26, 2019 · 2 comments · Fixed by #4877
Assignees
Labels
bug

Comments

@eloquence
Copy link
Contributor

@eloquence eloquence commented Apr 26, 2019

Description

The graphical updater fails to successfully complete an update, if it is re-run after an update that failed due to a Tails admin password not being set.

Steps to Reproduce

  1. Boot up the Admin Workstation with an update pending;
  2. Do not set a Tails admin password;
  3. Proceed with the update when prompted by the graphical updater.
  4. Cancel the update and reboot the workstation at the step that requires a Tails admin password.
  5. Proceed with the update when prompted by the graphical updater.

Expected Behavior

I can successfully complete the update.

Actual Behavior

The update fails ("Update failed").

@eloquence eloquence added the bug label Apr 26, 2019
@eloquence eloquence added this to Near Term Backlog in SecureDrop Team Board Apr 29, 2019
@eloquence eloquence moved this from Near Term Backlog to Nominated for next sprint (5/1-5/15) in SecureDrop Team Board Apr 30, 2019
@eloquence eloquence moved this from Nominated for next sprint (5/1-5/15) to Near Term Backlog in SecureDrop Team Board May 1, 2019
@eloquence eloquence moved this from Near Term Backlog to Nominated for next sprint in SecureDrop Team Board May 28, 2019
@eloquence eloquence moved this from Nominated for next sprint to Near Term Backlog in SecureDrop Team Board May 30, 2019
@rocodes

This comment has been minimized.

Copy link
Contributor

@rocodes rocodes commented Sep 23, 2019

Hey folks - any proposed workaround for this issue? Have a user reporting it in our Support Portal.

@redshiftzero redshiftzero moved this from Near Term Backlog to Current sprint - 9/19 - 10/9 in SecureDrop Team Board Sep 23, 2019
@zenmonkeykstop

This comment has been minimized.

Copy link
Contributor

@zenmonkeykstop zenmonkeykstop commented Sep 23, 2019

Yup, this is caused by a flag file that does not get removed when the updater fails in this scenario.

The most straightforward workaround is to:

  • delete the file ~amnesia/Persistent/.securedrop/securedrop_update.flag on the Admin Workstation
  • reboot Tails and start with the PV unlocked and an admin password set.

If the git checkout portion of the update completed successfully, the GUI updater will no longer appear. If you want to force it to run again (not necessary for releases that don't require a setup or tailsconfig update), open a terminal and run:

cd ~/Persistent/securedrop
git tag -v <previous release here> # verify that tag is signed
git checkout <previous release here>

Then, bounce the network connection. The GUI updater will appear and should work correctly, prompting you for the Tails admin pw about halfway through.

@emkll emkll closed this in #4877 Oct 8, 2019
SecureDrop Team Board automation moved this from Current Sprint - 9/19 - 10/9 to Done Oct 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants
You can’t perform that action at this time.