Paunch improperly names PID files for services running containers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Bogdan Dobrelya |
Bug Description
Sometimes (when redeploying overcloud on top, so containers/services get the prefixed names) the PID files does not match what's being used by the systemd service file.
$ systemctl status tripleo_
● tripleo_
Loaded: loaded (/etc/systemd/
Active: failed (Result: protocol) since Mon 2019-08-12 15:09:49 UTC; 16h ago
Process: *667419* ExecStart=
$ grep PIDFile /etc/systemd/
PIDFile=
$ ls -1 /var/run/
ls: cannot access '/var/run/
$ ls -1 /var/run/
/var/run/
$ cat /var/run/
666389
$ ps -fp 666389
UID PID PPID C STIME TTY TIME CMD
root 666389 1 0 Aug12 ? 00:00:00 /usr/libexec/
$ sudo podman inspect 78b965370645faa
"memcached-
This is caused by mismatching container name specified for PIDFile in systemd unit and the name passed as --conmon-pidfile argument
Changed in tripleo: | |
importance: | Undecided → Critical |
tags: | added: idempotency |
Changed in tripleo: | |
importance: | Critical → High |
milestone: | none → train-3 |
assignee: | nobody → Bogdan Dobrelya (bogdando) |
tags: | added: containers |
description: | updated |
description: | updated |
tags: | added: queens-backport-potential |
tags: | removed: queens-backport-potential |
Fix proposed to branch: master /review. opendev. org/676156
Review: https:/