Description of problem: After do system upgrade with "atomic host upgrade", the atomic command stopped to work. Version-Release number of selected component (if applicable): # cat /etc/redhat-release Fedora release 22 (Twenty Two) # uname -a Linux localhost.localdomain 4.2.3-200.fc22.x86_64 #1 SMP Thu Oct 8 03:23:55 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux How reproducible: # atomic host upgrade # systemctl reboot # atomic --help atomic --help Traceback (most recent call last): File "/usr/bin/atomic", line 31, in <module> import Atomic File "/usr/lib/python2.7/site-packages/Atomic/__init__.py", line 6, in <module> from .atomic import Atomic File "/usr/lib/python2.7/site-packages/Atomic/atomic.py", line 17, in <module> import dbus ImportError: No module named dbus
Likely introduced by https://bodhi.fedoraproject.org/updates/FEDORA-2015-15847
One can work around this with directly invoking `rpm-ostree upgrade`.
This workaround does not works: -bash-4.3# rpm-ostree upgrade Updating from: fedora-atomic:fedora-atomic/f22/x86_64/docker-host 30 metadata, 94 content objects fetched; 91569 KiB transferred in 120 seconds Copying /etc changes: 17 modified, 0 removed, 42 added Transaction complete; bootconfig swap: yes deployment count change: 0 Freed objects: 105.7 MB Changed: dnsmasq-2.75-2.fc22.x86_64 fedora-repos-22-2.noarch gssproxy-0.4.1-2.fc22.x86_64 hwdata-0.283-1.fc22.noarch os-prober-1.68-1.fc22.x86_64 plymouth-0.8.9-10.2013.08.14.fc22.x86_64 plymouth-core-libs-0.8.9-10.2013.08.14.fc22.x86_64 plymouth-scripts-0.8.9-10.2013.08.14.fc22.x86_64 Upgrade prepared for next boot; run "systemctl reboot" to start a reboot -bash-4.3# After reboot, the error persist!
I am also seeing this when trying to use Rawhide Atomic AWS AMI's in order to get Docker 1.9. The following AMI's have this issue: ami-bde639ce ami-719ba506 ami-719ba506 ami-617e4016 Btw: There are also broken symlinks for /tmp and /ostree (the whole of /sysroot is empty).
Please test and add karma to https://bodhi.fedoraproject.org/updates/FEDORA-2015-b6c503d73a
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle. Changing version to '24'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
atomic-1.16.3-1.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-2ad6948192
atomic-1.16.3-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-cf5944a771
atomic-1.16.3-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-cf5944a771
atomic-1.16.3-1.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-2ad6948192
atomic-1.16.4-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-e8cbc792c6
atomic-1.16.4-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-e8cbc792c6
atomic-1.16.4-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.