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:
podman 4.6.0-3.el9 has been built against podman main branch and commit 144098587706ac3fd4e257ea03c75aaf4ee29064 which is 4.7.0-dev and has been delivered in CentOS stream, causing all issues in systems running podman. For example, it prevents other tools like gitlab runner from starting services using podman.

https://gitlab.com/redhat/centos-stream/rpms/podman/-/commit/d265b78198fdabd6ec7508a5a61b2d7f46405e55

The build was changed to be done against branch "main" (perhaps it should be tag v4.6.0), and specifically commit 144098587706ac3fd4e257ea03c75aaf4ee29064.

```
$ git tag --contains "144098587706ac3fd4e257ea03c75aaf4ee29064"
## nothing

$ git checkout 144098587706ac3fd4e257ea03c75aaf4ee29064

$ cat version/rawversion/version.go 
package rawversion

// RawVersion is the raw version string.
//
// This indirection is needed to prevent semver packages from bloating
// Quadlet's binary size.
//
// NOTE: remember to bump the version at the top of the top-level README.md
// file when this is bumped.
const RawVersion = "4.7.0-dev"
```

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

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

This is now fixed by podman-4.6.1-1.el9:

$ podman --version
podman version 4.6.1

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: podman 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-2023:6474