Bug 1542971

Summary:	otopi uses yum on fedora
Product:	[oVirt] otopi	Reporter:	Yedidyah Bar David <didi>
Component:	Plugins.packagers	Assignee:	Yedidyah Bar David <didi>
Status:	CLOSED DUPLICATE	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	1.6.2	CC:	bugs, ylavi
Target Milestone:	ovirt-4.3.0	Flags:	rule-engine: ovirt-4.3+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-06-25 07:57:01 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:
Bug Blocks:	1460625

Description Yedidyah Bar David 2018-02-07 13:39:08 UTC

Description of problem:

On Fedora 27 (and somewhat earlier too), if otopi finds 'yum', it uses it.

See also bug 1495629.

Currently, otopi itself starts to support python3 and dnf-2, but the tools that use it (engine-setup, hosted-engine-setup, host-deploy) still do not (fully, at least). Also the interface and desired behavior are not fully clear (e.g. should 'otopi' choose python version, or link to python2-otopi, etc.).

Opening this bug mainly so that once everything works with python3/dnf-2, we remove this option - make otopi refuse to use yum if dnf is found. Exact behavior is still TBD.

The risk of not fixing this bug is e.g. to have separate dnf and yum histories, etc., perhaps other similar things.

Comment 1 Yaniv Lavi 2018-06-25 07:57:01 UTC


*** This bug has been marked as a duplicate of bug 1542529 ***