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.

Description of problem:

In kubernetes the imagePullPolicy value are capitalized like: Always, IfNotPresent and Never. But in podman the imagePullPolicy will be: missing, always, ifnotpresent and never. So we can not use the yaml file from kubernetes directly, otherwise it will report "unsupported pull policy".


Version-Release number of selected component (if applicable):
podman-3.2.3-0.9.module+el8.4.0+11870+8b6f7018.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Create a yaml file
cat >mypod.yml <<EOF
 Version: v1
 kind: Pod
 metadata:
   labels:
     app: pod-initcontainer
   name: pod-initcontainer
 spec:
   containers:
   - name: test_container
     image: quay.io/libpod/busybox
     command:
       - sleep
       - "3600"
     imagePullPolicy: Never
   restartPolicy: Always
 EOF

2. Star the the pod and container with podman play kube
# podman play kube mypod.yml


Actual results:
podman report unsupported pull policy


Expected results:
pod and container can be create as expected


Additional info:
The same test also failed in RHEL 8.5 with podman-3.3.0-0.14.module+el8.5.0+11900+dd5e640e.x86_64

Thanks for the report!  I opened the following commits to fix it:

* main branch: https://github.com/containers/podman/pull/11044
* v3.2.3-rhel branch: https://github.com/containers/podman/pull/11045

Fixed in podman 3.3

Setting to Post and assigning to Jindrich for any further BZ or packaging needs.

Test with podman-3.3.0-2.module+el8.5.0+12136+c1ac9593.x86_64 and the test passed.

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-2021:4154