Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Laszlo, you can probably just rpm -Uvh --force the rpm and it will work. If not you might need to just delete the installed pyc files, then next run of virt-install will just regenerate them. The actual code doesn't have any hard dep on a newer python version.
Unfortunately, it didn't work.
I tried "rpm -Uvh --force" first, but it kept complaining about "python(abi) = 2.7". Then I also added --nodeps (which allowed rpm to install the package), plus I removed all pyc and pyo files under:
- /usr/lib/python2.7/site-packages/virtconv
- /usr/lib/python2.7/site-packages/virtconv/parsers
- /usr/lib/python2.7/site-packages/virtinst
When I start virt-install, it says:
Traceback (most recent call last):
File "/usr/bin/virt-install", line 33, in <module>
import virtinst
ImportError: No module named virtinst
python-2.6 most probably doesn't look for the required files under /usr/lib/python2.7/site-packages. Can we change that with an environment variable? (I really don't want to move around or symlink files at this point.) Thanks.
>
> python-2.6 most probably doesn't look for the required files under
> /usr/lib/python2.7/site-packages. Can we change that with an environment
> variable? (I really don't want to move around or symlink files at this point.)
> Thanks.
For reference, you can see the system python path with
python -c 'import sys; print sys.path'
You can alter the python path like
PYTHONPATH=/usr/lib/python2.7/site-packages python -c 'import virtinst'
Regarding this bug though, it's pretty late in the cycle to backport what is essentially a new feature. Wouldn't be impossible though provided RHEL process isn't prohibitive, dallan what do you think?
Comment 11RHEL Program Management
2012-07-10 08:44:06 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 12RHEL Program Management
2012-07-11 01:59:27 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.