RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1957487 - python3-productmd: _modules attribute missing from Compose class
Summary: python3-productmd: _modules attribute missing from Compose class
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: python-productmd
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: beta
: ---
Assignee: Lubomír Sedlář
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-05 20:45 UTC by Carl George 🤠
Modified: 2022-11-05 07:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-05 07:27:39 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Add missing _modules attribute to Compose (758 bytes, application/mbox)
2021-05-05 20:45 UTC, Carl George 🤠
no flags Details

Description Carl George 🤠 2021-05-05 20:45:38 UTC
Created attachment 1779977 [details]
Add missing _modules attribute to Compose

Description of problem:
RHEL8 has productmd 1.11 which includes a Modules class [0] for processing modules.  However, that version also had a bug where the modules are inaccessible from the Compose class.  This was fixed upstream in version 1.15 [1].  It's a simple one line fix.  Please backport it to the RHEL8 package.  I'm including a backport patch adapted directly from the upstream commit.


Version-Release number of selected component (if applicable):
python3-productmd-1.11-3.el8


How reproducible:
always


Steps to Reproduce:
1. dnf install python3 python3-productmd
2. python3 -c 'import productmd; print(productmd.compose.Compose("path/to/compose").modules)'


Actual results:
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib/python3.6/site-packages/productmd/compose.py", line 131, in modules
    if self._modules is not None:
AttributeError: 'Compose' object has no attribute '_modules'


Expected results:
<productmd.modules.Modules object at 0x7f603c609700>


Additional info:
I also noticed that there is a request to rebase productmd to 1.25 [2].  If that is actioned this backport will not be necessary.  But one of the two will be needed to unblock building compose-utils in epel8 [3].


[0] https://github.com/release-engineering/productmd/commit/9be98ed1bceff5418f8e395cd0263b53544e6fa7
[1] https://github.com/release-engineering/productmd/commit/13ba89db6619e3b20a690be19ef1340faa0c633a
[2] bug 1819185
[3] bug 1956420

Comment 2 RHEL Program Management 2022-11-05 07:27:39 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.


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