Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1289903 - 'atomic' command fails to import dbus
Summary: 'atomic' command fails to import dbus
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: atomic
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lokesh Mandvekar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-09 10:28 UTC by Stef Walter
Modified: 2015-12-17 15:57 UTC (History)
4 users (show)

Fixed In Version: atomic-1.7-2.gitd378de0.fc22
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-16 09:53:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Stef Walter 2015-12-09 10:28:29 UTC
Description of problem:

-bash-4.3# atomic host status
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

Version-Release number of selected component (if applicable):

* 2015-12-08 21:17:20     22.185             82212b2ac6     fedora-atomic     fedora-atomic:fedora-atomic/f22/x86_64/docker-host     

How reproducible:

Every time

Comment 1 Stef Walter 2015-12-09 10:28:47 UTC
This bug was discovered by the Cockpit integration tests

Comment 2 Stef Walter 2015-12-10 06:37:22 UTC
-bash-4.3# rpm -q atomic
atomic-1.4-1.git9d724aa.fc22.x86_64
-bash-4.3# rpm -q python-dbus
package python-dbus is not installed

Comment 3 Colin Walters 2015-12-16 02:23:15 UTC
annotate says this came from http://pkgs.fedoraproject.org/cgit/atomic.git/commit/?h=f22&id=a5a7adbb5014e8f7283251e83421505971890d54

Now I'm confused since that links to https://bugzilla.redhat.com/show_bug.cgi?id=1278499
which is the exact same issue for F23, but this commit *introduced* it for F22?

Comment 4 Fedora Update System 2015-12-16 02:25:59 UTC
atomic-1.7-2.gitd378de0.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-b6c503d73a

Comment 5 Colin Walters 2015-12-16 02:26:53 UTC
One can work around this `rpm-ostree upgrade`.

Comment 6 Fedora Update System 2015-12-16 09:53:26 UTC
atomic-1.7-2.gitd378de0.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.

Comment 7 Stef Walter 2015-12-17 08:39:57 UTC
This is closed ... but will a new ostree build be done to unbreak Fedora Atomic 22?

(In reply to Colin Walters from comment #3)
> annotate says this came from
> http://pkgs.fedoraproject.org/cgit/atomic.git/commit/
> ?h=f22&id=a5a7adbb5014e8f7283251e83421505971890d54
> 
> Now I'm confused since that links to
> https://bugzilla.redhat.com/show_bug.cgi?id=1278499
> which is the exact same issue for F23, but this commit *introduced* it for
> F22?

I think there's a python-dbus vs. python3-dbus confusion here?

But anyway, I can confirm that this is fixed on Fedora Atomic 23 with this tree:

* 2015-12-14 10:16:00     23.33     a40cbd4a80     fedora-atomic     fedora-atomic:fedora-atomic/f23/x86_64/docker-host


Note You need to log in before you can comment on or make changes to this bug.