Bug 2132360
| Summary: | [RFE] python-podman: Podman support to perform custom actions on unhealthy containers [rhel-8.7.0.z] | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | RHEL Program Management Team <pgm-rhel-tools> | |
| Component: | python-podman | Assignee: | Jindrich Novy <jnovy> | |
| Status: | CLOSED ERRATA | QA Contact: | Alex Jia <ajia> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | urgent | |||
| Version: | 8.6 | CC: | ajia, asreddy, bbaude, cdoern, ddarrah, dornelas, dwalsh, dwojewod, jligon, jnovy, jwboyer, lsm5, mheon, pthomas, snanda, toneata, tsweeney, umohnani, vrothber, wwurzbac, ypu | |
| Target Milestone: | rc | Keywords: | FutureFeature, Triaged, ZStream | |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
|
| Hardware: | Unspecified | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | python-podman-4.2.0-2.el8_7 | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | 2131741 | |||
| : | 2136283 (view as bug list) | Environment: | ||
| Last Closed: | 2022-11-08 11:30:48 UTC | Type: | --- | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | 2131741 | |||
| Bug Blocks: | 2136283 | |||
|
Comment 2
Oneata Mircea Teodor
2022-10-18 07:40:23 UTC
Charlie, assuming the fix for this already landed in podman-py 4.2.0 or we need forwardport? v4.2.1 contains the new fix: https://github.com/containers/podman-py/releases/tag/v4.2.1 This bug has been verified on python3-podman-4.2.0-2.module+el8.7.0+16994+ed730e67.
[test@koza-4 ~]$ cat /etc/redhat-release
Red Hat Enterprise Linux release 8.7 (Ootpa)
[test@koza-4 ~]$ rpm -q python3-podman podman runc systemd kernel
python3-podman-4.2.0-2.module+el8.7.0+16994+ed730e67.noarch
podman-4.2.0-3.module+el8.7.0+16994+ed730e67.x86_64
runc-1.1.4-1.module+el8.7.0+16994+ed730e67.x86_64
systemd-239-68.el8.x86_64
kernel-4.18.0-425.3.1.el8.x86_64
[test@koza-4 ~]$ podman system service -t 0 &
[1] 20273
[test@koza-4 ~]$ netstat -lanp|grep podman.sock
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
unix 2 [ ACC ] STREAM LISTENING 73904 20287/podman /run/user/1000/podman/podman.sock
[test@koza-4 ~]$ cat test.py
"""Demonstrate PodmanClient."""
import json
from podman import PodmanClient
alpine_image = "quay.io/libpod/alpine:latest"
uri = "unix:///run/user/1000/podman/podman.sock"
def test_container_healtchecks():
"""Test passing various healthcheck options"""
with PodmanClient(base_url=uri) as client:
containers = []
parameters = {}
version = client.version()
print("Release: ", version["Version"])
print("Compatible API: ", version["ApiVersion"])
print("Podman API: ", version["Components"][0]["Details"]["APIVersion"], "\n")
parameters['healthcheck'] = {'Test': ['CMD-SHELL curl http://localhost || exit']}
parameters['health_check_on_failure_action'] = 1
container = client.containers.create(alpine_image, **parameters)
print("current container:%s" % container)
containers.append(container)
if __name__ == "__main__":
test_container_healtchecks()
[test@koza-4 ~]$ podman ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
[test@koza-4 ~]$ podman pull quay.io/libpod/alpine:latest
Trying to pull quay.io/libpod/alpine:latest...
Getting image source signatures
Copying blob 9d16cba9fb96 done
Copying config 9617696764 done
Writing manifest to image destination
Storing signatures
961769676411f082461f9ef46626dd7a2d1e2b2a38e6a44364bcbecf51e66dd4
[test@koza-4 ~]$ python3 test.py
Release: 4.2.0
Compatible API: 1.41
Podman API: 4.2.0
current container:<Container: e08469330b>
[test@koza-4 ~]$ podman ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
e08469330b86 quay.io/libpod/alpine:latest /bin/sh 4 seconds ago Created gallant_mahavira
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 (Low: 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-2022:7822 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |