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 2192977 - Correctly add secrets to container on creation - podman-py
Summary: Correctly add secrets to container on creation - podman-py
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: python-podman
Version: 8.7
Hardware: All
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Jindrich Novy
QA Contact: Edward Shen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-03 19:31 UTC by Tom Sweeney
Modified: 2024-03-14 04:25 UTC (History)
13 users (show)

Fixed In Version: python-podman-4.5.0-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-11-14 15:29:11 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-156333 0 None None None 2023-05-03 19:32:58 UTC

Description Tom Sweeney 2023-05-03 19:31:31 UTC
Description of problem:
Further details in:  https://issues.redhat.com/browse/RHELPLAN-151432  
This was fixed with https://github.com/containers/podman-py/pull/234 which is included in podman-jpy v4.5.0

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:

See noted Jira card

Expected results:

Secrets should work.

Additional info:

Comment 1 Tom Sweeney 2023-05-03 19:59:20 UTC
The fix for this is https://github.com/containers/podman-py/pull/234, which made podman-py v4.5.0.  That version of podman-py was just released last week, so I suspect it did not make the RHEL 8.8/9.2 Zero Day release.  @jnovy could you verify the version of podman-py that shipped with RHEL 8.8/9.2 ZeroDay please?

The original request was a backport to RHEL 8.7. However, it is no longer possible to backport to RHEL 8.7 as it's been closed for further changes.  We now need to see if the fix landed with the ZeroDay delivery, or if we'll need to get it into the next Zstream release.

@cpippin FYI

Comment 15 errata-xmlrpc 2023-11-14 15:29:11 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: container-tools:rhel8 security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2023:6939

Comment 16 Red Hat Bugzilla 2024-03-14 04:25:42 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days


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