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 1727873 - Error: pod was given but no pod is specified: invalid argument
Summary: Error: pod was given but no pod is specified: invalid argument
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: podman
Version: 7.6
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Brent Baude
QA Contact: Martin Jenner
URL:
Whiteboard:
: 1729053 (view as bug list)
Depends On:
Blocks: 1186913 1697833
TreeView+ depends on / blocked
 
Reported: 2019-07-08 12:10 UTC by Markus Schibli
Modified: 2023-09-14 05:31 UTC (History)
9 users (show)

Fixed In Version: podman-1.4.2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-29 16:17:28 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:1907 0 None None None 2019-07-29 16:17:36 UTC

Comment 6 Joy Pu 2019-07-12 03:06:18 UTC 
Test with podman-1.4.4-1.el7.x86_64 with steps in comments #1 and now the podman and conatiner can be created, and no error message is reported. Here is the details:
# podman play kube test-pod.yml 
Pod:
a65776792cd0433910966f80c988338889b4a05cdb216a2025c84b82ef263208
Container:
81ac82e4d4dc8fc920240bfb5c12d4f538249a3a4b903232fb58c9a7869e0f17
# podman pod ps
POD ID         NAME                STATUS    CREATED         # OF CONTAINERS   INFRA ID
a65776792cd0   pod-initcontainer   Running   7 seconds ago   2                 f91f9171cd71
# podman ps -a --pod
CONTAINER ID  IMAGE                 COMMAND  CREATED         STATUS                     PORTS  NAMES               POD
81ac82e4d4dc  busybox               sh       20 seconds ago  Exited (0) 20 seconds ago         test_container      a65776792cd0
f91f9171cd71  k8s.gcr.io/pause:3.1           20 seconds ago  Up 20 seconds ago                 a65776792cd0-infra  a65776792cd0

So the problem described in this bug is fixed. But I found that the Command in test_container is not match the test-pod.yml. But this should be another problem. Will set this one to verified and report another one for tracking it.
Comment 7 Derrick Ornelas 2019-07-12 13:00:24 UTC 
*** Bug 1729053 has been marked as a duplicate of this bug. ***
Comment 9 errata-xmlrpc 2019-07-29 16:17:28 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:1907
Comment 10 Red Hat Bugzilla 2023-09-14 05:31:32 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days
Note You need to log in before you can comment on or make changes to this bug.