Description of problem: Pod termination time is longer than 5 minutes. This bug is a followup of bz https://bugzilla.redhat.com/show_bug.cgi?id=2030029 While pods are no longer stuck in termination state - termination time maybe longer than 5 minutes (5 - 10) Hence opening this bz, as noted in https://bugzilla.redhat.com/show_bug.cgi?id=2030029#c39, to pursue / fine tune termination time Version-Release number of selected component (if applicable): ocp 4.9, 4.8 How reproducible: Reproducible at the customer environment as described in https://bugzilla.redhat.com/show_bug.cgi?id=2030029#c0 Steps to Reproduce: 1. 2. 3. Actual results: pods termination is longer than 5 minutes Expected results: Have pods terminate faster, less than 5 minutes the faster the better Additional info: Please let us know required data collection which will help pin pointing the issue
Sascha, can you take a look at this? we have to find why dbus connections are going into the void (If i were to guess, I would guess the dbus library is exec'ing something, and that exec'd process is falling into the wrong cpuset)