Bug 1754515
Summary: | [downstream clone - 4.3.7] get_otopi_python always prefers Python3 even when site-packages are Python2 on RHEL 7.7 | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | RHV bug bot <rhv-bugzilla-bot> |
Component: | otopi | Assignee: | Yedidyah Bar David <didi> |
Status: | CLOSED ERRATA | QA Contact: | Petr Matyáš <pmatyas> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | unspecified | CC: | bugs, didi, dougsland, lleistne, lsurette, lsvaty, pelauter, rdlugyhe, Rhev-m-bugs, sbonazzo, srevivo, tburke, thomas |
Target Milestone: | ovirt-4.3.7 | Keywords: | ZStream |
Target Release: | 4.3.7 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | otopi-1.8.4-1.el7ev | Doc Type: | Bug Fix |
Doc Text: |
Previously, with Red Hat Virtualization 4.3 on RHEL 7, if the system had Python 3 installed, otopi used Python 3. This caused relevant tools such as engine-setup and ovirt-host-deploy to fail. The current release fixes this issue: Now, even with Python 3 installed, otopi uses Python 2, enabling otopi-based tools such as engine-setup and ovirt-host-deploy to succeed. In the next minor version, 1.9, otopi should support Python 3 on RHEL 8 and Fedora.
|
Story Points: | --- |
Clone Of: | 1751324 | Environment: | |
Last Closed: | 2019-12-12 10:37:23 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Integration | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1751324 | ||
Bug Blocks: | 1762733, 1762742 |
Description
RHV bug bot
2019-09-23 13:07:04 UTC
Sandro - do we want this in 4.3? I think so. (Originally by didi) Verified on otopi-common-1.8.4-1.el7ev.noarch 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. https://access.redhat.com/errata/RHBA-2019:4233 |