-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
Qubes Updater silent failure while updating debian-10 TemplateVM #5705
Qubes Updater silent failure while updating debian-10 TemplateVM #5705
Comments
possibly related: saltstack/salt#56131 |
I think the ticket linked by @redshiftzero is very likely related: Based on my local testing, on a freshly installed Qubes 4.0.3 machine: On a fully patched Fedora-30 template, the |
Worth noting that using F29 (warning: Fedora29 is EOL) for the mgmt vm also resolves, due to the implicit version downgrade. So setting |
Looks like this wants backporting. Note version difference - apparently failing without python-pip package is a common pattern in salt... |
Should we install the |
This is exactly what the commit I pointed in #5705 (comment) does. |
If I read this correctly, we'd need python3-pip in every VM that is managed by salt, not only where salt-ssh is running. This means a simple dependency on a salt-related package isn't enough. On the other hand, the failing code applies only to states using "onlyif" keyword - if I remove them, the update works. Since the salt bug will probably take some more time to fix (PR with the fix is there already, but then it would need to be merged, released and packaged into Fedora), I'd go with avoiding "onlyif" in the update formula. Fortunately, it is used only to apply updates that are incorporated into new templates already, so I can simply remove those entries. |
salt-ssh may exit with code 0 even if applying state failed. One of such cases is saltstack/salt#56131. Add a heuristic that checks output data - if it's empty, report it as a failure for state.* command, as those always produce some output (changes summary). This converts silent failure into not-so-silent one (although there is still no details why it failed). Fixes QubesOS/qubes-issues#5705
Thanks for the quick response & PRs, Marek. This is a critical issue for the SecureDrop Workstation pilot from our perspective as it prevents important system updates from succeeding, and we'd obviously prefer not to manually downgrade packages for security reasons. Is there any way we can help to get this over the finish line? |
Main blocker is testing capacity (openqa busy on other set of PRs already). If you could test those two PRs in your environment too, that would help a lot. |
When I update Qubes VMs, after updates it still shows that all did not update, with green arrow icon. To get Debian 10 template updated, I need to do manually:
For Fedora 30 templates, I need to do manually:
Would it be possible to change update scripts so that all this cleanup would also be run automatically? |
This is broken in salt 3000 (saltstack/salt#56131) currently shipped in Fedora 30. Since those states apply changes already incorporated in all released templates (and latest stable installation image), simply drop them to unbreak updates. Fixes QubesOS/qubes-issues#5705 (cherry picked from commit e32dc3f)
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
Or update dom0 via Qubes Manager. |
Automated announcement from builder-github The package
Or update dom0 via Qubes Manager. |
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Qubes OS version
Qubes release 4.0 (R4.0)
Affected component(s) or functionality
Qubes Updater / update/qubes-vm.sls
Brief summary
Qubes Updater fails to update Debian-based Template
To Reproduce
or
sudo qubesctl --show-output --skip-dom0 --targets debian-10 state.sls update.qubes-vm
in dom0.Expected behavior
Actual behavior
OK
What appears to be relevant output in
debian-10
template:Screenshots
![updater](https://user-images.githubusercontent.com/15223328/75914985-b0b8f880-5e23-11ea-8d41-4b4c22ba1b21.png)
Additional context
For reference, the version of qubes-template-debian-10.noarch I am using is 4..1-201905201854
Solutions you've tried
apt upgrade
directly on the VM itself does work, it seems like the issue is limited to saltRelevant documentation you've consulted
none
Related, non-duplicate issues
none
The text was updated successfully, but these errors were encountered: