-
Notifications
You must be signed in to change notification settings - Fork 46
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
Audit and suppress CRITICAL messages in install #559
Comments
In spite of the error on the terminal (which a user ordinarily wouldn't see, if they launch the updater through the desktop icon), the update seems to be continuing. |
Thanks for clarifying that the update process did not fail. I suspect the CRITICAL message is being displayed during the salt purge, see #530 (comment) for a different "CRITICAL" message noted during review. |
It looks like it ultimately completed successfully. Here's the remainder of the output: Click to expand
|
Ran a graphical updater on "staging" environment. Completed without error. Inspecting Currently experiencing a sync problem on the client, version |
Retitled and rescoped -- we should IMO still understand the cause of any CRITICAL messages during the installation, and suppress if possible and appropriate, as part of getting the workstation ready for wider production use. |
During
sdw-admin --apply
runs, we sometimes observe "CRITICAL" messages by Qubes. As part of making the system production-ready, we should audit the current installation process, identify the root cause of each message, and suppress them if they are indeed safe to ignore.Example 1
Observed during attempt to update SecureDrop Workstation running 0.3.0-rc1 to 0.3.0-rc2, using the graphical updater. Update completes successfully, no user-facing errors, but see output on terminal below, which occurred while the updater reported 95% progress.
Click to expand
Example 2
See #530 (comment)
The text was updated successfully, but these errors were encountered: