Bug 1316950 - [RFE] OTOPI should use python3 interpreter on Fedora
[RFE] OTOPI should use python3 interpreter on Fedora
Status: POST
Product: otopi
Classification: oVirt
Component: Core (Show other bugs)
Unspecified Unspecified
medium Severity medium (vote)
: ovirt-4.3.0
: ---
Assigned To: Yuval Turgeman
Lukas Svaty
: CodeChange, FutureFeature
: 1426484 (view as bug list)
Depends On: 1365751
Blocks: oVirt_on_Fedora
  Show dependency treegraph
Reported: 2016-03-11 09:03 EST by Sandro Bonazzola
Modified: 2018-03-07 04:56 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Feature: OTOPI should use python3 interpreter on Fedora Reason: Result:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: Integration
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
rule-engine: ovirt‑4.3+
ylavi: planning_ack+
rule-engine: devel_ack+
pstehlik: testing_ack+

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 62032 master ABANDONED packaging: spec: Package for python3 2016-08-10 05:07 EDT
oVirt gerrit 86472 master MERGED build: packaging for both python2 and python3 2018-02-06 09:22 EST
oVirt gerrit 87222 master MERGED build: modified binfiles to point to python2 2018-02-08 01:13 EST
oVirt gerrit 87246 master MERGED build: set otopi-devtools as obsolete 2018-02-07 05:15 EST
oVirt gerrit 87276 master MERGED core: Use python3 when possible 2018-03-13 04:40 EDT

  None (edit)
Description Sandro Bonazzola 2016-03-11 09:03:17 EST
The python interpreter is decided by otopi before ovirt-host-deploy can do anything.
So ovirt-host-deploy can't use the package manager to request otopi to install the missing python2-dnf package to support python2 execution since the missing package is needed to perform the install.
Since python2-dnf is not there but python3-dnf is, the only way to solve this (other than asking user to manually install it) is to run otopi with python3.
Comment 1 Yedidyah Bar David 2016-03-22 10:45:18 EDT
Wouldn't this break all our other code that's not yet python3? engine-setup, hosted-engine-setup?
Comment 2 Sandro Bonazzola 2016-03-22 12:21:53 EDT
engine-setup and hosted-engine-setup should be already python3 compatible. If not, we should fix. I don't consider this a blocker for oVirt 4 but it's the only way to solve cleanly bug #1297835 and keep Fedora compatibility in the future.
Comment 3 Red Hat Bugzilla Rules Engine 2016-07-03 06:25:29 EDT
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Comment 4 Yedidyah Bar David 2016-07-31 10:25:52 EDT
Now tried to reproduce bug 1297835 on fedora 24 and failed. Instead of failing, it succeeded, but used yum, not dnf. The result is that I have some transactions done using dnf and soem using yum.

Will try tomorrow to check more stuff, including reproduction on fedora 23, and the pending patch for current bug. Even if/when we merge it, we should be aware of the above current behavior - not sure that's intended on fedora 24, didn't check yet if it's documented anywhere.
Comment 5 Yedidyah Bar David 2017-03-06 05:31:47 EST
Several patches were merged for this bug, and later reverted because they broke too much stuff. Moving back to NEW for now.

When we eventually solve this bug, we should probably:

1. Follow fedora python packaging guidelines, including package naming.
2. In particular build for both python2 and python3.
3. Allow using both the python2 and the python3 as applicable, with whatever Known Issues relevant at the time (e.g. bug 1297835 if using python2).

is not installed on the host, but bundled, copied and ran from a temporary directory.
If it turns out that a single such bundle can run under both python2 and python3, we might default to python3 on fedora >= 23.
Comment 6 Sandro Bonazzola 2017-03-07 04:20:21 EST
*** Bug 1426484 has been marked as a duplicate of this bug. ***

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