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 1729053 - podman play kube faces error on exporting the yaml
Summary: podman play kube faces error on exporting the yaml
Keywords:
Status: CLOSED DUPLICATE of bug 1727873
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: podman
Version: 7.6
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Brent Baude
QA Contact: Martin Jenner
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-11 09:56 UTC by Sayali Kulkarni
Modified: 2019-07-12 13:00 UTC (History)
7 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-12 13:00:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Sayali Kulkarni 2019-07-11 09:56:04 UTC
Description of problem:

podman play kube with yaml file doesn't start. The error is: 
``` Error: pod was given but no pod is specified: invalid argument ``` This bug is fixed in podman version 1.4.1 and up but that isn't available on RHEL 7.6.


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

podman-1.3.2-1.git14fdcd0.el7.x86_64


How reproducible:

100%


Steps to Reproduce:

# podman run -dt -p 8000:80 --name demo rhel7
Trying to pull registry.access.redhat.com/rhel7...Getting image source signatures
Copying blob dc4e07da33bc done
Copying blob 5c2598df4560 done
Copying config b6bcd4d771 done
Writing manifest to image destination
Storing signatures
f7e4e7f6e9bf2f499a4d0851d10514eac71ceac7ace10489c92b58b078324a79

# podman generate kube demo  > demo.yml

# podman play kube demo.yml
Error: pod was given but no pod is specified: invalid argument


Actual results:

Error: pod was given but no pod is specified: invalid argument


Expected results:

No errors

Additional info:

https://github.com/containers/libpod/issues/3157

Comment 2 Daniel Walsh 2019-07-11 12:20:26 UTC
Fixed in podman 1.4.2

Comment 3 Derrick Ornelas 2019-07-12 13:00:24 UTC

*** This bug has been marked as a duplicate of bug 1727873 ***


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