podman api play kube the replace parameter #20705

jontte75 · 2023-11-17T14:19:16Z

jontte75
Nov 17, 2023

Hello,
I'm trying to give the replace parameter with value true, using the api (curl via socket), so that existing pod with container would be replaced. It works fine as long as the pod to be created does not exist. But if it does exist already, I always get the error "pod already exists" (despite the replace=true").

What I tried was:
/d/v4.0.0/libpod/play/kube?annotations=%7B%22some.value%22%3A%221%22%2C%22some.hash%22%3A%22911e0f%22%7D&network=pasta&replace=true

If I run the podman kube play --replace by hand,it works just fine, and existing pod with containers is replaced.

I assume I'm giving the replace parameter somehow wrong in the url, so how should one give it?

Answered by rhatdan

Nov 22, 2023

Ok, opened a PR to fix. You were correct podman was doing the removal on the client side not the server side.

View full answer

rhatdan · 2023-11-18T21:02:17Z

rhatdan
Nov 18, 2023
Maintainer

I think your Curl line is correct, but try with

podman --remote kube play --replace

6 replies

rhatdan Nov 20, 2023
Maintainer

Too bad the Debug does not show the actual API command.

@jwhonce Any ideas?

jontte75 Nov 21, 2023
Author

One more thing...I managed to capture data from the socket, and noticed that podman --remote worked a bit differently from our soultion (curl).
podman --remote

No.	Time	Source	Destination	Protocol	Length	Info
4	0.000427983	127.0.0.1	127.0.0.1	HTTP	144	GET /v4.7.2/libpod/_ping HTTP/1.1 
6	0.004207340	127.0.0.1	127.0.0.1	HTTP	446	HTTP/1.1 200 OK  (text/plain)
14	0.008807666	127.0.0.1	127.0.0.1	HTTP	144	GET /v4.7.2/libpod/_ping HTTP/1.1 
16	0.014288708	127.0.0.1	127.0.0.1	HTTP	446	HTTP/1.1 200 OK  (text/plain)
22	0.019283644	127.0.0.1	127.0.0.1	HTTP	2519	DELETE /v4.7.2/libpod/play/kube?force=false HTTP/1.1 
29	0.270132515	127.0.0.1	127.0.0.1	HTTP	253	GET /v4.0.0/libpod/containers/json?all=true HTTP/1.1  (application/yaml)
33	0.554009510	127.0.0.1	127.0.0.1	HTTP/JSON	83	HTTP/1.1 200 OK , JavaScript Object Notation (application/json)
<....>

curl api:

No.	Time	Source	Destination	Protocol	Length	Info
72	20.792752921	127.0.0.1	127.0.0.1	HTTP	2781	POST /v4.0.0/libpod/play/kube?annotations=%7B%22com.company.platform-managed%22%3A%221%22%2C%22com.company.yamlHash.kube%22%3A%22a66b1e0f%22%7D&network=pasta&replace=true HTTP/1.1  (application/yaml)
73	20.817550709	127.0.0.1	127.0.0.1	HTTP/JSON	460	HTTP/1.1 500 Internal Server Error , JavaScript Object Notation (application/json)
74	20.817675204	127.0.0.1	127.0.0.1	TCP	66	57604 → 9876 [ACK] Seq=6620 Ack=94440 Win=65152 Len=0 TSval=1893865280 TSecr=1893865280

So to me it looks like in podman --remote case, the podman-remote already handles the --replace and it first deletes the pod and other resources (--replace is not sent to the remote as in the curl-case).

rhatdan Nov 21, 2023
Maintainer

Looks like I fixed this recently.

commit 91df369ae6807d5d3c0adf37ea5caeb883c0284e (rhatdan/pod, pod)
Author: Daniel J Walsh <[email protected]>
Date:   Fri Oct 27 07:23:53 2023 -0400

    podman kube play --replace should force removal of pods and containers
    
    Fixes: https://github.com/containers/podman/issues/20025
    
    Signed-off-by: Daniel J Walsh <[email protected]>

rhatdan Nov 21, 2023
Maintainer

This should be fixed in podman 4.8 which went RC1 yesterday.

jontte75 Nov 21, 2023
Author

Thanks for Your support!
Tried with the latest one, seems that there is still some issues with the api (curl) and the replace=true

$ podman --version
podman version 4.8.0-dev
$

CURL: POST /v4.0.0/libpod/play/kube?annotations=%7B%22com.company.platform-managed%22%3A%221%22%2C%22com.company.yamlHash.kube%22%3A%22a66b2ef93cdeb9e44bd9ef962604f7daee47b8d8d167e419043bab742d911e0f%22%7D&network=pasta&replace=true HTTP/1.1
<...>
CURL: HTTP/1.1 500 Internal Server Error
CURL: Api-Version: 1.41
CURL: Content-Type: application/json
CURL: Libpod-Api-Version: 4.8.0-dev
CURL: Server: Libpod/4.8.0-dev (linux)
CURL: X-Reference-Id: 0x4000010008
CURL: Date: Tue, 21 Nov 2023 18:43:03 GMT
CURL: Content-Length: 160
CURL:
CURL: {"cause":"pod already exists","message":"playing YAML file: adding pod to state: name \"TestApplication-pod\" is in use: pod already exists","response":500}
<....>

I tried with the podman remote, and it worked though

$ podman --log-level=trace --remote --url=unix://run/podman/podman.sock kube play --replace --network=pasta test.yaml 
INFO[0000] podman filtering at log level trace          
DEBU[0000] Called play.PersistentPreRunE(podman --log-level=trace --remote --url=unix://run/podman/podman.sock kube play --replace --network=pasta test.yaml) 
DEBU[0000] DoRequest Method: GET URI: http://d/v4.8.0/libpod/_ping 
DEBU[0000] DoRequest Method: GET URI: http://d/v4.8.0/libpod/_ping 
DEBU[0000] DoRequest Method: DELETE URI: http://d/v4.8.0/libpod/play/kube 
Pods stopped:
96b15d0f6b3d294458d514f8b1949e101bfbb3202104820bc70a10ff384a6721
Pods removed:
96b15d0f6b3d294458d514f8b1949e101bfbb3202104820bc70a10ff384a6721
Secrets removed:
Volumes removed:
DEBU[0002] Loading registries configuration "/etc/containers/registries.conf"

rhatdan · 2023-11-21T19:50:04Z

rhatdan
Nov 21, 2023
Maintainer

Can you give my the actual curl command you are running?

4 replies

jontte75 Nov 22, 2023
Author

Actually I wrote a bit wrong; libcurl is used here. But I will try to reproduce this with plain curl commands

jontte75 Nov 22, 2023
Author

Here is one example:

$ cat alpine-pod.yaml | curl  -H "Content-Type: application/yaml" -vvv --unix-socket /run/podman/podman.sock --data-binary "@-" 'http://d/v4.8.0/libpod/play/kube?annotations=%7B%22some.value%22%3A%221%22%2C%22some.hash%22%3A%22911e0f%22%7D&network=pasta&replace=true'
* processing: http://d/v4.8.0/libpod/play/kube?annotations=%7B%22some.value%22%3A%221%22%2C%22some.hash%22%3A%22911e0f%22%7D&network=pasta&replace=true
*   Trying /run/podman/podman.sock:0...
* Connected to d (/run/podman/podman.sock) port 80
> POST /v4.8.0/libpod/play/kube?annotations=%7B%22some.value%22%3A%221%22%2C%22some.hash%22%3A%22911e0f%22%7D&network=pasta&replace=true HTTP/1.1
> Host: d
> User-Agent: curl/8.2.1
> Accept: */*
> Content-Type: application/yaml
> Content-Length: 423
> 
< HTTP/1.1 200 OK
< Api-Version: 1.41
< Content-Type: application/json
< Libpod-Api-Version: 4.8.0-dev
< Server: Libpod/4.8.0-dev (linux)
< X-Reference-Id: 0x4000122040
< Date: Wed, 22 Nov 2023 09:14:45 GMT
< Content-Length: 372
< 
{"Pods":[{"ID":"eb7b859e732827dc1e05ffce6023776701e21b6f929e78240627d168ea552923","Containers":["4ceaf66c5ee74a79ffb1221c5b630e5423fba83ba6debdd8c8772c9dafe53c3a"],"InitContainers":null,"Logs":null,"ContainerErrors":null}],"Volumes":null,"StopReport":null,"RmReport":null,"VolumeRmReport":null,"SecretRmReport":null,"Secrets":null,"ServiceContainerID":"","ExitCode":null}
* Connection #0 to host d left intact
$ cat alpine-pod.yaml | curl  -H "Content-Type: application/yaml" -vvv --unix-socket /run/podman/podman.sock --data-binary "@-" 'http://d/v4.8.0/libpod/play/kube?annotations=%7B%22some.value%22%3A%221%22%2C%22some.hash%22%3A%22911e0f%22%7D&network=pasta&replace=true'
* processing: http://d/v4.8.0/libpod/play/kube?annotations=%7B%22some.value%22%3A%221%22%2C%22some.hash%22%3A%22911e0f%22%7D&network=pasta&replace=true
*   Trying /run/podman/podman.sock:0...
* Connected to d (/run/podman/podman.sock) port 80
> POST /v4.8.0/libpod/play/kube?annotations=%7B%22some.value%22%3A%221%22%2C%22some.hash%22%3A%22911e0f%22%7D&network=pasta&replace=true HTTP/1.1
> Host: d
> User-Agent: curl/8.2.1
> Accept: */*
> Content-Type: application/yaml
> Content-Length: 423
> 
< HTTP/1.1 500 Internal Server Error
< Api-Version: 1.41
< Content-Type: application/json
< Libpod-Api-Version: 4.8.0-dev
< Server: Libpod/4.8.0-dev (linux)
< X-Reference-Id: 0x4000123a10
< Date: Wed, 22 Nov 2023 09:15:05 GMT
< Content-Length: 142
< 
{"cause":"pod already exists","message":"playing YAML file: adding pod to state: name \"test\" is in use: pod already exists","response":500}
* Connection #0 to host d left intact
[container@kedge ~]$

The given annotations can be seen when inspecting the created container, so the curl command cannot be completely wrong :-)

The used example yaml is attached here
alpine-pod.yaml.tar.gz

rhatdan Nov 22, 2023
Maintainer

Ok, opened a PR to fix. You were correct podman was doing the removal on the client side not the server side.

Answer selected by jontte75

jontte75 Nov 22, 2023
Author

Thanks for the information and support! I'll close this, since it will now be handles as a PR

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

podman api play kube the replace parameter #20705

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 2 comments 10 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

podman api play kube the replace parameter #20705

jontte75 Nov 17, 2023

Replies: 2 comments · 10 replies

rhatdan Nov 18, 2023 Maintainer

rhatdan Nov 20, 2023 Maintainer

jontte75 Nov 21, 2023 Author

rhatdan Nov 21, 2023 Maintainer

rhatdan Nov 21, 2023 Maintainer

jontte75 Nov 21, 2023 Author

rhatdan Nov 21, 2023 Maintainer

jontte75 Nov 22, 2023 Author

jontte75 Nov 22, 2023 Author

rhatdan Nov 22, 2023 Maintainer

jontte75 Nov 22, 2023 Author

jontte75
Nov 17, 2023

Replies: 2 comments 10 replies

rhatdan
Nov 18, 2023
Maintainer

rhatdan Nov 20, 2023
Maintainer

jontte75 Nov 21, 2023
Author

rhatdan Nov 21, 2023
Maintainer

rhatdan Nov 21, 2023
Maintainer

jontte75 Nov 21, 2023
Author

rhatdan
Nov 21, 2023
Maintainer

jontte75 Nov 22, 2023
Author

jontte75 Nov 22, 2023
Author

rhatdan Nov 22, 2023
Maintainer

jontte75 Nov 22, 2023
Author