-
Bug
-
Resolution: Unresolved
-
Major
-
4.18
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
Proposed
-
Bug Fix
-
Fixed oc adm must-gather volume checker not killing gather when a custom command is specified
-
None
-
None
-
None
-
None
Description of problem:
when the volume max percentage exceeded we expect must gather to stop run, but the pkill fails and must gather continues to run
This happens when we run not the default 1 word cmd /usr/bin/gather
This is the run cmd:
oc adm must-gather -- "sed -i 's#--rotated-pod-logs# #g' /usr/bin/*gather* && /usr/bin/gather"
Version-Release number of selected component (if applicable):
How reproducible:
every time when not enough disk space and with this cmd
Steps to Reproduce:
1.run oc adm must-gather -- "sed -i 's#--rotated-pod-logs# #g' /usr/bin/*gather* && /usr/bin/gather"
Actual results:
[must-gather-dksw2] POD 2025-07-30T08:56:09.318218227Z volume usage percentage 65 [must-gather-dksw2] POD 2025-07-30T08:56:09.318248495Z Disk usage exceeds the volume percentage of 5 for mounted directory. Exiting... [must-gather-dksw2] POD 2025-07-30T08:56:09.321511812Z pkill: only one pattern can be provided [must-gather-zj2cr] POD 2025-07-30T08:56:09.307828344Z pkill: only one pattern can be provided
Expected results:
pkill succeeds and must gather running stops
Additional info: