Bug 1717991 - ovirt-hosted-engine-setup requires pyliblzma which is available only for python2
Summary: ovirt-hosted-engine-setup requires pyliblzma which is available only for python2
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-hosted-engine-setup
Classification: oVirt
Component: Packaging.rpm
Version: 2.3.9
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ovirt-4.4.0
: 2.4.0
Assignee: Simone Tiraboschi
QA Contact: Polina
URL:
Whiteboard:
Depends On:
Blocks: RHV-H_4.4_RHEL_8
TreeView+ depends on / blocked
 
Reported: 2019-06-06 15:26 UTC by Sandro Bonazzola
Modified: 2020-05-20 20:02 UTC (History)
1 user (show)

Fixed In Version: ovirt-hosted-engine-setup-2.4.0
Clone Of:
Environment:
Last Closed: 2020-05-20 20:02:02 UTC
oVirt Team: Integration
Embargoed:
sbonazzo: ovirt-4.4?


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 100613 0 'None' MERGED Remove unneeded dependencies 2020-04-16 08:43:06 UTC

Description Sandro Bonazzola 2019-06-06 15:26:47 UTC
ovirt-hosted-engine-setup requires pyliblzma which is available only for python2.
We either need to drop the dependency or find a suitable alternative.

Comment 1 Simone Tiraboschi 2019-06-06 15:43:50 UTC
It was used just in 3.6/el6 -> 4.0/el7 upgrade flow: https://github.com/oVirt/ovirt-hosted-engine-setup/blob/ovirt-hosted-engine-setup-2.2/src/plugins/gr-he-upgradeappliance/vm/configurevm.py#L29
which it's not there anymore in 4.3.
We can simply drop it.

Comment 2 Polina 2020-04-19 12:59:01 UTC
verified on http://bob-dr.lab.eng.brq.redhat.com/builds/4.4/rhv-4.4.0-29
no pyliblzma dependency on both engine and host

Comment 3 Sandro Bonazzola 2020-05-20 20:02:02 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.


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