Red Hat Bugzilla – Bug 985515
productid yum plugin fails in anaconda env because of missing dbus in anaconda runtime image
Last modified: 2013-09-30 19:13:31 EDT
Created attachment 774850 [details]
screenshot of F2 console from anaconda after running the plugin manually
Description of problem:
0a95a841719210e2b6b244377d926a6eab9cf535 in master moved
the code for getting a dbus interface from gui/utils.py to
the rhsm yum plugin "productid.py" is invoked via the anaconda
process (via yum). The environment in which anaconda is running
does not have the dbus-python package (/usr/lib64/python2.4/site-packages/dbus)
so the productid plugin fails to load.
Note that in rhel5, the file system image is using as it's / filesystem
is basically constructed by hand, often ignoring rpm deps. In this case,
despite productid.py requiring dbus-python, it isnt part of the installer.
We may be able to get it included, but I doubt it (doesn't look like there
is any dbus at all).
So we probably need to either remove or split that dep, or let it handle
it being missing.
screenshot of F2 console from anaconda after running the plugin manually,
Version-Release number of selected component (if applicable):
Anaconda image from RHEL5.10-Client-20130717.0.n
*** Bug 986757 has been marked as a duplicate of this bug. ***
Author: ckozak <email@example.com>
Date: Mon Jul 22 14:44:23 2013 -0400
985515: moved DbusIface to fix anaconda productId
Created attachment 786212 [details]
/etc/pki/product/69.pem was installed by anaconda
My approach to verifying this bug will be to launch a minimal install (no groups checked and all default packages unchecked by choosing Customize now during anaconda install screens) and verify after it completes that the RHEL product id is installed.
Verifying with RHEL-5.10-Server-Snapshot-4.0/ RHEL5.10-Server-20130807.1
After provisioning a minimal install, only 154 packages were installed. /root/anaconda-ks.cfg contains only:
subscription-manager was not installed, however the product id was indeed installed as /etc/pki/product/69.pem See screenshot.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.