oscerd commented on PR #3033:
URL: https://github.com/apache/camel-kamelets/pull/3033#issuecomment-5773264580
@JiriOndrusek the two failing tests are not caused by this PR. **They fail
the same way on an unmodified `main`.**
I ran `OpenApiIT` on `main` at c23ad6dfd, with nothing from this branch:
```
✘ TEST FAILED: rest-openapi-sink-delete-pet-test
✘ TEST FAILED: rest-openapi-sink-add-pet-test
ValidationException: Values not equal for header element
'citrus_http_request_uri',
expected '/petstore/pet' but was '/petstore/openapi.json'
```
Identical to what CI reported here, and the rest of your run is clean: 69 of
71 passing, with the two failures in `rest-openapi`, which this PR does not
touch.
## What is actually happening
The test expects two requests in order: a `GET /petstore/openapi.json` to
fetch the specification, then the operation call. What arrives at the second
expectation is **another spec fetch**, so the specification is being requested
more than once and the operation request never shows up where the test waits
for it.
Nothing in the Kamelet or the test changed. These integrations are executed
by Camel JBang rather than by the project's `camel.version`, so they run
against a moving Camel snapshot. The same tests passed on 2026-09-16 in CI and
again locally on 2026-09-17; they fail today with no commit here in between,
which points at a `camel-rest-openapi` behaviour change upstream rather than
anything in this catalog.
That also puts the fix on the other side of the runtime boundary:
`rest-openapi` is a Camel component, so if the repeated fetch is unintended it
belongs in `apache/camel`.
## What this means for this PR
Nothing here needs changing on account of those two failures. They should
not hold up review. I have flagged the breakage to @oscerd separately so it can
be chased on its own rather than through your pull request.
---
_Claude Code on behalf of Andrea Cosentino_
--
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]
