Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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:
BugZilla 2210139 corrected the issue of inaccurate stats being displayed when the "podman stats" command was run with the --no-stream option.

However, "podman version" returns no difference in the version number returned between the inaccurate podman 3.0.1 vs the corrected podman 3.0.1-11.  In both cases, the version returned is 3.0.1.

Customer would like the entire version number displayed to make it easier to identify which podman is in use.

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

How reproducible:
Very.   

Steps to Reproduce:
1. Install podman 3.0.1-11 (or later)
2. Execute "podman version"


Actual results:
# podman version
Version:      3.0.1

Expected results:
We expect podman to not cut off the end of the version number 

Additional info:

The output of `podman version` is correct, as this is Podman 3.0.1 - plus some extra, RHEL-specific patches. 3.0.1-11 is the RPM version, which is not correlated to the version of Podman (and I don't really know how we'd correlate them - Podman 4.4.1, for example, is shipped in both RHEL8 and RHEL9, so we could easily end up with podman-4.4.1-3 on RHEL8 referring to the same code as Podman 4.4.1-5 on RHEL9, or similar. As such we have no plans to make changes to `podman version` to include information on the RPM Podman was shipped in.

That said, it should be possible to include full information on the RPM package in `podman info` to indicate the RPM that the installed Podman came from. Would this be acceptable?