smengcl opened a new pull request, #11474:
URL: https://github.com/apache/ozone/pull/11474

   Generated-by: Claude Code (Opus 5.5)
   
   ## What changes were proposed in this pull request?
   
   When a test fails in `ozone-ha/test-haproxy-s3g.sh`, the 
`acceptance-HA-unsecure` artifact is not uploaded at all:
   
   ```
   The path for one of the files in artifact is not valid: 
/ozone-ha/haproxy-s3g/ozone-ha-s3g-1_runtime exec failed: exec failed: unable 
to start container process: exec: "bash": executable file not found in 
$PATH.stack. Contains the following character:  Double quote "
   ```
   
   `create_stack_dumps` lists Java processes with `docker exec "${c}" bash -c 
"jps | grep -v Jps"`. The `s3g` service in the HAProxy setup is 
`haproxy:lts-alpine`, which has no bash. Docker prints the `OCI runtime exec 
failed` error to stdout, so it is read as `pid procname` and becomes part of 
the stack dump filename.
   
   HDDS-9027 fixed this by using `sh -c`, which HDDS-11454 changed back to 
`bash -c`. This patch uses `sh -c` again: `jps` is not found in the HAProxy 
container, nothing reaches stdout, and no stack dump file is created for it.
   
   ## What is the link to the Apache JIRA
   
   https://issues.apache.org/jira/browse/HDDS-16883
   
   ## How was this patch tested?
   
   - Ran both variants against a `haproxy:lts-alpine` container with stderr 
discarded: `bash -c "jps | grep -v Jps"` prints the `OCI runtime exec failed` 
error on stdout, `sh -c "jps | grep -v Jps"` prints nothing.
   - `hadoop-ozone/dev-support/checks/bats.sh` passes.
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to