ben-grande
commented
3 months ago browser is installed but doesn't talk to cacher through 8082 and updates cannot be downloaded.
If browser.install-common failed, this won't work because the file browser/install-common.sls pulls qubes-core-agent-networking which has socat which is a dependency of qvm-connect-tcp which is called by browser/files/browser/rc.local.d/50-sys-cacher.rc to be able to connect on boot to sys-cacher port 8082.
updates cannot be downloaded
If the installation failed, there is a possibility that other things have failed midway. I can't diagnose the problem based on this. Can you please share more information of the commands that you ran an failed? Rerun the installation steps after I push the commit to fix the browser.install-common, which I already detected.
Also default uodatevm not changed in global config.
The cacher doesn't changes qubes-prefs updatevm. That setting is only used by dom0 updates via qubes-dom0-update, qvm-template etc. Because the cacher doesn't cache dom0, doesn't make sense to make it the global updatevm.
The updatevm setting can be changed by sys-mirage-firewall, sys-firewall and sys-pihole, in other words, the firewall qubes, that are always on when network connections are needed.
Commitment
I confirm that I have read the following resources:
Software version
Latest
Brief summary
sys-cacher depends on browser which depends on browser-installed-chromium which depdends on browser.install-common which is not found
Steps to reproduce
Deploy sys-cacher after dom0, debian-minimal and fedors-minimal
Expected behavior
sys-cacher deployed successfully
Actual behavior
Half baked deployment requiring deinit to revert. browser is installed but doesn't talk to cacher through 8082 and updates cannot be downloaded. Also default uodatevm not changed in global config.