Bug 1985905

Summary: Podman report unsupported pull policy if set imagePullPolicy with capitalized Word
Product: Red Hat Enterprise Linux 8 Reporter: Joy Pu <ypu>
Component: podmanAssignee: Jindrich Novy <jnovy>
Status: CLOSED ERRATA QA Contact: Joy Pu <ypu>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 8.4CC: bbaude, dwalsh, jligon, jnovy, lsm5, mheon, pthomas, tsweeney, umohnani, vrothber
Target Milestone: beta   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: podman-3.3.0-0.21.el8 or newer Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-11-09 17:40:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Joy Pu 2021-07-26 08:12:02 UTC
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

Comment 1 Valentin Rothberg 2021-07-26 08:32:29 UTC
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

Comment 2 Daniel Walsh 2021-07-26 12:43:54 UTC
Fixed in podman 3.3

Comment 3 Tom Sweeney 2021-07-26 20:38:55 UTC
Setting to Post and assigning to Jindrich for any further BZ or packaging needs.

Comment 7 Joy Pu 2021-08-05 16:54:17 UTC
Test with podman-3.3.0-2.module+el8.5.0+12136+c1ac9593.x86_64 and the test passed.

Comment 9 errata-xmlrpc 2021-11-09 17:40:16 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-2021:4154