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 1847544 - Socket-activated Varlink (io.podman.socket) fails after first call
Summary: Socket-activated Varlink (io.podman.socket) fails after first call
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: podman
Version: 8.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: 8.3
Assignee: Jindrich Novy
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
: 1847559 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-16 15:23 UTC by Matthew Heon
Modified: 2020-11-04 03:06 UTC (History)
8 users (show)

Fixed In Version: podman-2.0.0-0.7.rc6.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-04 03:05:17 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Matthew Heon 2020-06-16 15:23:50 UTC
Description of problem:

After the first call to the `io.podman` Varlink socket, subsequent calls will fail as the socket has been removed.

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

podman-2.0.0-0.6.rc6.module+el8.3.0+7024+2421c176

How reproducible:

100%

Steps to Reproduce:
1. systemctl start io.podman.socket
2. varlink call unix:/run/podman/io.podman/org.varlink.service.GetInfo
3. varlink call unix:/run/podman/io.podman/org.varlink.service.GetInfo

Actual results:

Second (and all subsequent) `varlink call` statement fails as `/run/podman/io.podman` is missing/removed after first `varlink call`

Expected results:

All calls to `varlink call` are successful

Additional info:

Fix is already in flight upstream as https://github.com/containers/libpod/pull/6619

Comment 2 Jindrich Novy 2020-06-17 04:55:49 UTC
*** Bug 1847559 has been marked as a duplicate of this bug. ***

Comment 5 Joy Pu 2020-07-20 06:39:12 UTC
Test with podman-2.0.0-0.9.rc7.module+el8.3.0+7084+c16098dd.x86_64. And now the socket will not be removed. So set this to verified. Details:
# varlink call unix:/run/podman/io.podman/org.varlink.service.GetInfo
{
  "interfaces": [
    "org.varlink.service",
    "io.podman"
  ],
  "product": "podman",
  "url": "https://github.com/containers/libpod",
  "vendor": "Atomic",
  "version": "2.0.0-rc7"
}
# varlink call unix:/run/podman/io.podman/org.varlink.service.GetInfo
{
  "interfaces": [
    "org.varlink.service",
    "io.podman"
  ],
  "product": "podman",
  "url": "https://github.com/containers/libpod",
  "vendor": "Atomic",
  "version": "2.0.0-rc7"
}

Comment 8 errata-xmlrpc 2020-11-04 03:05:17 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 (Moderate: container-tools:rhel8 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-2020:4694


Note You need to log in before you can comment on or make changes to this bug.