The 20170215 qcow/vagrant images we released don't properly detect and use static deltas. I've been told this is because we are leaving the fedora-atomic/25/x86_64/updates/docker-host ref on the system as a result of the trickery we perform in the installer.
20170215
fedora-atomic/25/x86_64/updates/docker-host
The non-use of static deltas won't be a big issue once this issue is fixed upstream, but leaving around the ref is supposedly bad because some files that could get cleaned up won't and will take up space that they shouldn't.
We'll just move to a model where we don't leave around the other ref. PR here
Metadata Update from @dustymabe: - Issue assigned to dustymabe
Metadata Update from @dustymabe: - Issue tagged with: host
This has merged upstream - I'll close this after our next release when we prove everything works as desired.
The images we released today have the ref cleaned up.
[fedora@cloudhost ~]$ ostree refs fedora-atomic:fedora-atomic/25/x86_64/docker-host ostree/0/1/0 [fedora@cloudhost ~]$ [fedora@cloudhost ~]$ [fedora@cloudhost ~]$ rpm-ostree status State: idle Deployments: ● fedora-atomic:fedora-atomic/25/x86_64/docker-host Version: 25.80 (2017-03-13 23:35:50) Commit: 24d4499420ffb2cc49681020bbe5aa6780d780d2b811eab1f5ffea6446b5a4c5 OSName: fedora-atomic
still can't close this issue until next release when we can verify that the images we released today can properly detect and use static deltas to do the upgrade. Will wait for that to close this ticket.
The images released today properly pick up and use static deltas. Closing.
Metadata Update from @dustymabe: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.