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.
+++ This bug was initially created as a clone of Bug #1941727 +++
Description of problem:'
The meta data in the module is wronge
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
1. yum module list | grep container-tools
Actual results:
Stable versions of podman 1.0, buildah 1.5, skopeo 0.1, runc, conmon, CRIU, Udica, etc as well as dependencies such as container-selinux built and tested together, and supported for 24 months.
Expected results:
The 1.0 should be: Stable versions of podman 1.0, buildah 1.5, skopeo 0.1, runc, conmon, CRIU, Udica, etc as well as dependencies such as container-selinux built and tested together, and supported as documented on the Application Stream lifecycle page.
Additional info:
--- Additional comment from Scott McCarty on 2022-01-19 15:30:22 UTC ---
Jindirch,
Notice that the 2.0 and 3.0 modules are missing CRIU and Udica.
[root@keith-dc2-crunchtools-com entitlement]# yum module list | grep container-tools
container-tools rhel8 [d][e] common [d] [i] Most recent (rolling) versions of podman, buildah, skopeo, runc, conmon, runc, conmon, CRIU, Udica, etc as well as dependencies such as container-selinux built and tested together, and updated as frequently as every 12 weeks.
container-tools 1.0 common [d] Stable versions of podman 1.0, buildah 1.5, skopeo 0.1, runc, conmon, CRIU, Udica, etc as well as dependencies such as container-selinux built and tested together, and supported for 24 months.
container-tools 2.0 common [d] Stable versions of podman 1.6, buildah 1.11, skopeo 0.1, runc, conmon, etc as well as dependencies such as container-selinux built and tested together, and supported as documented on the Application Stream lifecycle page.
container-tools 3.0 common [d] Stable versions of podman 3.0, buildah 1.19, skopeo 1.2, runc, conmon, etc as well as dependencies such as container-selinux built and tested together, and supported as documented on the Application Stream lifecycle page.
--- Additional comment from Scott McCarty on 2022-07-16 18:13:51 UTC ---
This meta data still needs fixed. They should be as follows:
container-tools rhel8 [d][e] common [d] Most recent (rolling) versions of podman, buildah, skopeo, runc, conmon, runc, conmon, CRIU, Udica, etc as well as dependencies such as container-selinux built and tested together, and updated as frequently as every 12 weeks.
container-tools 1.0 common [d] Stable versions of podman 1.0, buildah 1.5, skopeo 0.1, runc, conmon, CRIU, Udica, etc as well as dependencies such as container-selinux built and tested together, and supported on the Application Stream lifecycle page.
container-tools 2.0 common [d] Stable versions of podman 1.6, buildah 1.11, skopeo 0.1, runc, conmon, CRIU, Udica, etc as well as dependencies such as container-selinux built and tested together, and supported as documented on the Application Stream lifecycle page.
container-tools 3.0 common [d] Stable versions of podman 3.0, buildah 1.19, skopeo 1.2, runc, conmon, CRIU, Udica, etc as well as dependencies such as container-selinux built and tested together, and supported as documented on the Application Stream lifecycle page.
container-tools 4.0 common [d] Stable versions of podman 4.0, buildah 1.24, skopeo 1.6, runc, conmon, CRIU, Udica, etc as well as dependencies such as container-selinux built and tested together, and supported as documented on the Application Stream lifecycle page.
--- Additional comment from Tom Sweeney on 2022-07-18 19:55:30 UTC ---
Jindrich, please see Scott's latest comment.
--- Additional comment from Jindrich Novy on 2022-07-27 07:27:43 UTC ---
The description/summary is now updated for 3.0-8.7.0 and 4.0-8.7.0.
Scott, if a 2.0 stream change is required for RHOSP then we need to go through zstream approval and cloning process.
--- Additional comment from Joy Pu on 2022-08-15 08:58:54 UTC ---
Checked with the latest build log http://download.eng.bos.redhat.com/brewroot/packages/container-tools/4.0/8070020220802150542.39077419/files/module/modulemd.x86_64.txt. The summary is already updated.:
Stable versions of podman 4.0, buildah 1.24, skopeo 1.6, runc, conmon,
CRIU, Udica, etc as well as dependencies such as container-selinux built and tested
together, and supported as documented on the Application Stream lifecycle page
So add the Tested flag.
--- Additional comment from Jindrich Novy on 2022-08-22 13:48:32 UTC ---
Setting "zstream?" so that this bug can be used for cloning to commit to 8.6.0 branches.