Bug 1729234

Summary: blivet3 requires a nonexistent 'enum' module
Product: Red Hat Enterprise Linux 7 Reporter: Pavel Cahyna <pcahyna>
Component: python-blivet3Assignee: Pavel Cahyna <pcahyna>
Status: CLOSED WONTFIX QA Contact: Release Test Team <release-test-team-automation>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.7CC: rhandlin
Target Milestone: pre-dev-freezeKeywords: Triaged
Target Release: 7.8   
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: 2021-03-15 07:37:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1410996, 1691966    

Description Pavel Cahyna 2019-07-11 16:09:10 UTC 
Description of problem:
from blivet3 import Blivet
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python2.7/site-packages/blivet3/__init__.py", line 30, in <module>
    from . import util, arch
  File "/usr/lib/python2.7/site-packages/blivet3/util.py", line 19, in <module>
    from enum import Enum

Version-Release number of selected component (if applicable):
3.1.3-3.el7


Additional info:

While 3.1.3-3 added code to handle absence of enum in lib.py, there are other uses in util.py and lvm.py.
Comment 2 Pavel Cahyna 2019-07-30 18:18:13 UTC 
It turns out that there is python-enum34 package providing this module (so adding the code to handle its absence was probably unnecessary and the only thing needed is to add a dependency on python-enum34).
Comment 3 David Lehman 2019-08-05 17:09:47 UTC 
I think you're on the right track: add the Requires for python-enum34 and drop the code workaround(s).
Comment 6 RHEL Program Management 2021-03-15 07:37:28 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.