chihsuan opened a new pull request, #10685:
URL: https://github.com/apache/ozone/pull/10685
## What changes were proposed in this pull request?
HDDS-12113 moved the S3 HAProxy tests into the HA environments, but
`ozonesecure-ha/test-haproxy-s3g.sh` never set `COMPOSE_FILE`, so it ran
against a
single `s3g` and never started `s3-haproxy.yaml`. The `HA-secure` suite
exercised
the test without actually routing S3 traffic through HAProxy.
1. `ozonesecure-ha/test-haproxy-s3g.sh`: set
`COMPOSE_FILE=docker-compose.yaml:s3-haproxy.yaml` to start the HAProxy
proxy and
three backend `s3g` workers.
2. `testlib.sh` (`reorder_om_nodes`): use POSIX `sh` instead of `bash`. The
`haproxy:lts-alpine` proxy has no `bash`, so the per-container `docker
exec` failed
with exit 127 and aborted the run under `set -e`. `sh` lets the existing
`ozone-site.xml` guard skip non-Ozone containers; behavior is unchanged
elsewhere.
## What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-14956
## How was this patch tested?
- Ran `ozonesecure-ha/test-haproxy-s3g.sh`: 131/131 S3 robot tests passed,
now with
the HAProxy proxy and three backends.
- Verified routing: 12 requests to `s3g:9878` round-robined 4/4/4 across the
backends,
logged with the HAProxy container IP as source.
- `bats.sh` passed.
Generated-by: Claude Code (Opus 4.8)
--
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]
