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 1771990 - Varlink subcommand is missing for podman in rhel-8.2
Summary: Varlink subcommand is missing for podman in rhel-8.2
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: podman
Version: 8.2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: 8.2
Assignee: Jindrich Novy
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-13 10:59 UTC by Matej Marušák
Modified: 2020-04-28 15:51 UTC (History)
10 users (show)

Fixed In Version: podman-1.6.3-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-28 15:48:34 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:1650 0 None None None 2020-04-28 15:51:03 UTC

Description Matej Marušák 2019-11-13 10:59:09 UTC 
Description of problem:
In current rhel-8.2 build there is no `varlink` subcommand. This breaks cockpit-podman.


Version-Release number of selected component (if applicable):
podman-1.6.2-5.module+el8.2.0+4584+0d586e68.x86_64


How reproducible:
```
$ podman varlink
Error: unrecognized command `podman varlink`
Try 'podman --help' for more information.
```
or how I found out:
```
$ sudo systemctl start io.podman
```

Additional info:
We (as cockpit-podman) have tests in rhel dist-git[1] and also integrate them into container-tools module[2] but it seems it is not working otherwise this would not slip in?


[1] https://src.osci.redhat.com/rpms/cockpit-podman
[2] http://pkgs.devel.redhat.com/cgit/modules/container-tools
Comment 1 Martin Pitt 2019-11-13 11:02:46 UTC 
Do you have any guidance how to add cockpit-podman's gating tests (http://pkgs.devel.redhat.com/cgit/rpms/cockpit-podman/tree/tests?h=stream-container-tools-rhel8-rhel-8.2.0) into http://pkgs.devel.redhat.com/cgit/modules/container-tools/tree/tests/tests.yml?h=rhel8-rhel-8.2.0 ? With all the complex roles structure it's not obvious how to do that. Can changes to that file be tested locally somehow, or do OSCI pull requests run them?
Comment 2 Ed Santiago 2019-11-13 14:06:12 UTC 
A few rhel8 module builds were accidentally done without build tags; the 4602 build[1] should be back to normal.

 [1] podman-1.6.2-6.module+el8.2.0+4602+797a8543
Comment 4 Ed Santiago 2019-11-13 18:48:30 UTC 
> Do you have any guidance how to add cockpit-podman's gating tests

As of 2019-09-30 (when I asked this on #osci), there is no way to have one package run/chain/combine with another's gating tests. It is on their radar but I don't know where or what priority. The only current way to do it is by duplicating one in the other.
Comment 5 Martin Pitt 2019-11-13 21:32:40 UTC 
@Ed: But this isn't "tie one package to another"; container-tools is the module, and cockpit-podman is one package in it, similar to podman itself, buildah, etc. These other components of that module already have their tests enabled, just not cockpit-podman.
Comment 6 Ed Santiago 2019-11-15 02:09:56 UTC 
Sorry, I totally spaced about cockpit-podman being part of the module. It should be straightforward to include that test. I'm traveling this week but will get to this early next week. Thank you for clarifying.
Comment 7 Jindrich Novy 2019-11-20 14:52:54 UTC 
Fixed in podman-1.6.3-1.el8 in container-tools-rhel8-8.2.0.
Comment 8 Martin Pitt 2019-11-22 08:16:44 UTC 
This isn't in the nightlies yet [1], did the build fail or so?

[1] http://download.devel.redhat.com/rhel-8/nightly/RHEL-8/latest-RHEL-8.2/compose/AppStream/x86_64/os/Packages/
Comment 9 Jindrich Novy 2019-11-22 09:56:11 UTC 
Martin, maybe it's not yet there because gating tests are failing. We are working on it.
Comment 15 errata-xmlrpc 2020-04-28 15:48:34 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, 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-2020:1650
Note You need to log in before you can comment on or make changes to this bug.