Bug 1751324

Summary:	get_otopi_python always prefers Python3 even when site-packages are Python2 on CentOS 7
Product:	[oVirt] otopi	Reporter:	thomas
Component:	Core	Assignee:	Yedidyah Bar David <didi>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Petr Matyáš <pmatyas>
Severity:	high	Docs Contact:
Priority:	high
Version:	master	CC:	bugs, lleistne, pelauter, sbonazzo, thomas
Target Milestone:	ovirt-4.4.0	Keywords:	ZStream
Target Release:	1.9.0	Flags:	sbonazzo: ovirt-4.4? pelauter: planning_ack+ sbonazzo: devel_ack+ lleistne: testing_ack+
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	otopi-1.9.0	Doc Type:	Bug Fix
Doc Text:	Cause: otopi defaulted to using python3, if found, although it's still not fully working in 4.3. Consequence: Relevant tools, including engine-setup and ovirt-host-deploy, could fail, if python3 was installed on the system before they ran. Fix: otopi was changed to default to python (2) when it is running on EL7. Result: Now otopi-based tools, such as engine-setup and host-deploy, should succeed, even if python3 is installed. In the next minor version, 1.9, otopi should fully support python3, on EL8+ and Fedora.	Story Points:	---
Clone Of:
Clones:	1754515 (view as bug list)		Environment:
Last Closed:	2020-05-20 19:59:50 UTC	Type:	Bug
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:	1788090
Bug Blocks:	1700864, 1754515

Description thomas 2019-09-11 17:51:17 UTC

Description of problem:
As previously described with Bug 1688811, an python3 will cause Otopi to pick it first, but for all the system libraries only exist as Python2 code on CentOS 7

With Python3 being included in the standard, the argument cited for "wontfix" in the bug 1688811 may need to be revised.

Version-Release number of selected component (if applicable):
oVirt 4.3.5.2 otopi 1.8.3-1.el7

How reproducible:
, try to add it as a new host to oVirt,

Steps to Reproduce:
1. Install python3 on target host-to-add
2. try to add host to oVirt engine
3. /var/log/ovirt-engine/host-deploy/ovort-host-deploy<unique-id>.log will contain error messages that rpmUtils could not be imported.

Actual results:
Host installation fails quickly, needs to be removed immediately or there will be followup problems, because it cannot go into maintenance for proper removal

Expected results:
Host installed and usable

Additional info:
took more than three weeks to track down, very hard to find

Comment 1 Yedidyah Bar David 2019-09-16 09:39:34 UTC

Sandro - do we want this in 4.3? I think so.

Comment 3 Petr Matyáš 2020-03-20 11:28:06 UTC

Verified on otopi-common-1.9.0-1.el8ev.noarch

Comment 4 Sandro Bonazzola 2020-05-20 19:59:50 UTC

This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020.

Since the problem described in this bug report should be
resolved in oVirt 4.4.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.