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 1693154 - Varlink subcommand is missing for podman in rhel-8.0
Summary: Varlink subcommand is missing for podman in rhel-8.0
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: podman
Version: 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.1
Assignee: Brent Baude
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-27 09:07 UTC by Joy Pu
Modified: 2020-11-14 11:48 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-05 21:01:58 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-2019:3403 0 None None None 2019-11-05 21:02:34 UTC

Description Joy Pu 2019-03-27 09:07:54 UTC 
Description of problem:
As the podman varlink will available until rhel 8.1, and the varlink subcommand in podman is already removed in the rpm, we should also remove related systemd files from it.


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

podman-1.0.0-2.git921f98f.module+el8+2784+9a0c1dfe

How reproducible:
100%

Steps to Reproduce:
1. Use ls to check if io.podman.* files exist under /usr/lib/systemd/system
# ls  /usr/lib/systemd/system/io.podman.*
2.
3.

Actual results:
# ls  /usr/lib/systemd/system/io.podman.*
/usr/lib/systemd/system/io.podman.service  /usr/lib/systemd/system/io.podman.socket

Expected results:
Nothing find under /usr/lib/systemd/system


Additional info:
Comment 1 Daniel Walsh 2019-03-27 09:26:23 UTC 
We did not remove podman varlink from RHEL.  We only removed the Client side.  You can still communicate using varlink to the server.

Other packages like cockpit-podman and manually calling via varlink still exist.   I don't see a reason to remove the service files.
Comment 7 Marcus Furlong 2019-06-10 22:40:23 UTC 
On RHEL 8.0, the io.podman service fails to start, due to missing varlink:

# systemctl start io.podman
# systemctl status io.podman
● io.podman.service - Podman Remote API Service
   Loaded: loaded (/usr/lib/systemd/system/io.podman.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Mon 2019-06-10 18:38:41 EDT; 4s ago
     Docs: man:podman-varlink(1)
  Process: 10552 ExecStart=/usr/bin/podman varlink unix:/run/podman/io.podman (code=exited, status=125)
 Main PID: 10552 (code=exited, status=125)

Jun 10 18:38:40 dev-10-34-0-40 systemd[1]: Started Podman Remote API Service.
Jun 10 18:38:41 dev-10-34-0-40 podman[10552]: Command "varlink" not found.
Jun 10 18:38:41 dev-10-34-0-40 podman[10552]: See `podman --help`.
Jun 10 18:38:41 dev-10-34-0-40 systemd[1]: io.podman.service: Main process exited, code=exited, status=125/n/a
Jun 10 18:38:41 dev-10-34-0-40 systemd[1]: io.podman.service: Failed with result 'exit-code'.
Comment 9 Brent Baude 2019-06-17 13:47:58 UTC 
see comment #6
Comment 10 Joy Pu 2019-09-27 15:22:20 UTC 
Test with podman-1.4.2-5.module+el8.1.0+4240+893c1ab8.x86_64 and the varlink subcommand is already shows up. So set this to verified. Details
# podman varlink -h
Run varlink interface

Description:
  Run varlink interface.  Podman varlink listens on the specified unix domain socket for incoming connects.

  Tools speaking varlink protocol can remotely manage pods, containers and images.


Usage:
  podman varlink [flags] [URI]

Examples:
  podman varlink unix:/run/podman/io.podman
  podman varlink --timeout 5000 unix:/run/podman/io.podman

Flags:
  -t, --timeout int   Time until the varlink session expires in milliseconds.  Use 0 to disable the timeout (default 1000)
Comment 12 errata-xmlrpc 2019-11-05 21:01:58 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-2019:3403
Note You need to log in before you can comment on or make changes to this bug.