Description of problem: Actualizando : docker-2:1.13.1-47.gitf43d177.fc28.armv7hl 1015/2191 Error unpacking rpm package docker-2:1.13.1-47.gitf43d177.fc28.armv7hl Error unpacking rpm package docker-2:1.13.1-47.gitf43d177.fc28.armv7hl error: Plugin selinux: hook fsm_file_prepare failed error: falló el desempaquetado de archivos en archivo/etc/docker: cpio: (error 0x2) Actualizando : oci-register-machine-0-6.1.git66fa845.fc28.armv7hl 1016/2191 error: docker-2:1.13.1-47.gitf43d177.fc28.armv7hl: instalar falló Filing as a Beta blocker as update from Fedora 27 to 28 fails the rpm transaction. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Discussed at 2018-03-19 Fedora 28 blocker review meeting: https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2018-03-19/f28-blocker-review.2018-03-19-16.02.html . We are fairly sure Docker is not in fact in any of the default release-blocking package sets that are subject to a normal upgrade process, so this is not covered by the release criterion, "For each one of the release-blocking package sets, it must be possible to successfully complete a direct upgrade from fully updated installations of the last two stable Fedora releases with that package set installed." However, we accept it as a freeze exception issue, as obviously Docker is an important package and we ought to fix upgrade problems in it. It would be useful to test on other arches, to see if this is somehow ARM-specific or 32-bit specific, perhaps...
Hello, I have tested this bug on x86_64 to confirm or not. The procedure was: 1. Install Fedora Server 27. 2. Run "dnf upgrade". 3. Install docker, because it was not installed by default. 4. Install python3-dnf-plugin-system-upgrade.noarch 5. Run dnf system-upgrade download --releasever=28 6. Run dnf system-upgrade reboot I ended up with updated Fedora Server with 4.16.0-0.rc4.git0.1.fc28 kernel. I cannot confirm this bug for the x86_64 version of Fedora Server.
The same I did for i386. I did not see the reported error happening either.
Thanks Lukas!
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.