Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upqubes-dom0-update cumulative rpm size quota #3408
Comments
andrewdavidwong
added
bug
C: core
labels
Dec 18, 2017
andrewdavidwong
added this to the Release 4.0 milestone
Dec 18, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
najamelan
Dec 27, 2017
Note that the documentation already mentions this:
Disk Quota Exceeded (When Installing Templates)
If you install multiple templates you may encounter this error. The solution is to shut down the updateVM between each install:
install template and shutdown updateVM:
cmd.run:
- name: sudo qubes-dom0-update -y fedora-24; qvm-shutdown {{ salt.cmd.run(qubes-prefs updateVM) }}
I can confirm this workaround:
Go into the updateVM and delete unneeded rpms in both:
/var/lib/qubes/dom0-updates/packages
/var/lib/qubes/dom0-updates/var/cache/yum/x86_64/4.0/qubes-templates-itl-fd404fe04a5ff777/packages
najamelan
commented
Dec 27, 2017
|
Note that the documentation already mentions this:
I can confirm this workaround: |
xaki23 commentedDec 18, 2017
Qubes OS version:
R4-RC3
Affected TemplateVMs:
Steps to reproduce the behavior:
install RC3
install fedora-26 template (works)
install fedora-26-minimal template
fails horribly with some quota-exceeded message after downloading
the problem here is the total sum of downloaded-since-last-reboot rpms in the updatevm cache exceeds 2GB (arbitrary limit enforced somewhere in the chain)
the step of pulling the rpms from updatevm to dom0 allway pulls all RPMs in the cache (instead of just the one(s) it cares about), a hardcoded something/*.rpm
and it seems the cache is not expired after a successful install
Expected behavior:
being able to install multiple huge rpms (like templates) in dom0
Actual behavior:
installation failing when reaching a cumulative rpm size limit
General notes:
workarounds:
restart updatevm to clean cache
manual cleanup of rpms in updatevm (dont miss the second copy in the tree)
passing --clean to qubes-dom0-update (and downloading all the repo metadata again)
Related issues: