k8s Coredump Handler: Timing issue during create-k8s-account.sh execution

Bug #2059264 reported by Thales Elero Cervi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
In Progress
Undecided
Unassigned

Bug Description

Brief Description
-----------------
When creating a sleep process in one k8s pod and killing it (sleep 30 command followed by Ctrl+\ to trigger coredump.), a sleep coredump should be created, but no coredump is being created.

Severity
--------
Minor: System is usable with minor issue (k8s Coredump Handler is not working)

Steps to Reproduce
------------------
On a lab installed with STX:

1)ssh to non-k8s host or to a pod

2) run a sleep process (i.e sleep 10) and ctrl + \ to kill It

3) check coredump file extension created under /coredump/

Expected Behavior
------------------
coredumps are found(e.g sleep.*.zst)

Actual Behavior
----------------
No coredumps are found

Reproducibility
---------------
Intermittent

Branch/Pull Time/Commit
-----------------------
master

Timestamp/Logs
--------------
sysadmin@controller-0:~$ sudo cat /etc/k8s-coredump-conf.json
{
    "k8s_coredump_token": ""
}

k8s-account-creation-script.log:
Initializing k8s-coredump kubernetes ServiceAccount creation
Running kubectl apply
The connection to the server [aefd::1]:6443 was refused - did you specify the right host or port?
Getting token and creating config file
TOKEN=''

puppet:
2024-03-22T01:59:01.944 Notice: 2024-03-22 01:59:01 +0000 /Stage[main]/Platform::Coredump::K8s_token_handler::Controller/Exec[create-k8s-coredump-account]/returns: executed successfully

First log in the kube-apiserver log (7 seconds later):
2024-03-22T01:59:08.978712165Z stderr F Flag --insecure-port has been deprecated, This flag has no effect now and will be removed in v1.24.

Test Activity
-------------
Regression Testing

Workaround
----------
Manually re-execute /etc/k8s-coredump/create-k8s-account.sh

description: updated
Changed in starlingx:
status: New → In Progress
tags: added: stx.utilities
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.