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.

Description of problem:

Podman's version in RHEL 8.4 includes the "-dev" prefix which suggests that a development version (rather than a stable one) is shipped.


How reproducible:

Always.


Steps to Reproduce:
1. `podman version`

Actual results:

Version:      3.0.2-dev
API Version:  3.0.0
Go Version:   go1.15.7
Built:        Wed Apr  7 04:36:54 2021
OS/Arch:      linux/amd64

Expected results:

Version:      3.0.2
API Version:  3.0.0
Go Version:   go1.15.7
Built:        Wed Apr  7 04:36:54 2021
OS/Arch:      linux/amd64

Quick correction: The reported version should be `v3.0.1` (not `v3.0.2`).

Opened an upstream PR: https://github.com/containers/podman/pull/10515

Test with podman-3.3.0-2.module+el8.5.0+12136+c1ac9593.x86_64, seems we need fix it in 3.3 branch too.
# podman version
Version:      3.3.0-dev
API Version:  3.3.0-dev
Go Version:   go1.16.6
Built:        Thu Aug  5 04:57:16 2021
OS/Arch:      linux/amd64

@mheon did we miss tweaking the version in Podman 3.3.0rc1?

This is a release candidate, so it is still a development version. I don't expect this to flip over to a non-dev version until we do a final release.

Test with podman-3.3.0-8.module+el8.5.0+12332+af0a4708.x86_64 and it works as expected. So set this to verified.
Version:      3.3.0
API Version:  3.3.0
Go Version:   go1.16.7
Built:        Sat Aug 21 15:33:32 2021
OS/Arch:      linux/amd64

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, bug fix, and enhancement 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-2021:4154