Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
Regression in the /CoreOS/initscripts/Sanity/bz843386-killproc-function-should-check-if-program-has-exited-several-times-during-delay
Version-Release number of selected component (if applicable):
initscripts-9.03.51-1.el6
How reproducible:
Always
Steps to Reproduce:
1. execute tc#268929
Actual results:
fail
Expected results:
pass
Additional info:
original bug bz843386, works with initscripts-9.03.49-1.el6
Lukas, I've found terrible bug in this patch.
__kill_pids_term_kill() {
local try=0
local delay=3;
local pid=
local kill_list=$* <==== in the kill_list can be also something like -d 60
local stat=($(< /proc/self/stat))
local base_stime=${stat[21]}
if [ "$1" = "-d" ]; then
delay=$2
shift 2
fi
after this __kill_pids_term_kill_checkpids filter out from kill_list "-d", but if a process with pid 60 exists, it stays in the kill_list.
Example:
# ps -p60
PID TTY TIME CMD
60 ? 00:00:00 md/2
# sleep 100 &
[1] 24658
# echo $! > /tmp/pid
# killproc -p /tmp/pid -d 60 sleep
kill_list 60 24658 <==== i've put echo "kill_list $kill_list" just before signaling TERM
[1]+ Terminated sleep 100
It terms the sleep, but cannot terminate md/2 (thankfully) and waits for 60s because of delay.
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, 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://rhn.redhat.com/errata/RHBA-2016-0951.html