Aias00 opened a new pull request, #6379: URL: https://github.com/apache/shenyu/pull/6379
## What changed - Recover the RocketMQ logging e2e compose flow when the initial sync stack start leaves `shenyu-bootstrap` created but not started. - Wait for `shenyu-admin` health first, then explicitly start `shenyu-bootstrap`. - Fail immediately when required healthchecks fail instead of continuing to Maven with an unavailable gateway. ## Why GitHub Actions job `80239448309` for apache/shenyu#6339 failed in the zookeeper sync round. The log showed `dependency failed to start: container shenyu-admin is unhealthy`, then `shenyu-bootstrap` stayed in `Created` state and Maven failed because `http://localhost:31195` was unavailable. This branch is based on apache/shenyu#6339 and adds one CI recovery commit on top. ## Verification - `bash -n shenyu-e2e/shenyu-e2e-case/shenyu-e2e-case-logging-rocketmq/compose/script/e2e-logging-rocketmq-compose.sh` - `./mvnw -B -f ./shenyu-e2e/pom.xml -pl shenyu-e2e-case/shenyu-e2e-case-logging-rocketmq -am -DskipTests test-compile` - `docker compose -f shenyu-e2e/shenyu-e2e-case/compose/sync/shenyu-sync-zookeeper.yml config --quiet` - `docker compose -f shenyu-e2e/shenyu-e2e-case/shenyu-e2e-case-logging-rocketmq/compose/shenyu-rocketmq-compose.yml config --quiet` - `docker compose -f shenyu-e2e/shenyu-e2e-case/shenyu-e2e-case-logging-rocketmq/compose/shenyu-examples-http-compose.yml config --quiet` - `./mvnw -B -pl shenyu-plugin/shenyu-plugin-logging/shenyu-plugin-logging-rocketmq -am -DskipTests test-compile` - `git diff --check` ## Not tested Full Docker Compose e2e was not run locally because the CI-built images `apache/shenyu-admin:latest`, `apache/shenyu-bootstrap:latest`, and `shenyu-examples-http:latest` are not present locally. Related: apache/shenyu#6339 -- 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]
