jordigilh commented on PR #337:
URL:
https://github.com/apache/incubator-kie-kogito-serverless-operator/pull/337#issuecomment-1900204014
> So looks like there is a consistent fail on PR check - 3 out of 3 reruns:
>
> ```
> SonataFlow Operator Validate that Platform services and flows are running
successfully when creating a simple workflow [It] with both Job Service and
Data Index and ephemeral persistence and the workflow in a dev profile:
> [FAILED] No container was found that could respond to the health
endpoint failed to execute curl command against health endpoint in container
data-index-service:invalid character 'I' looking for beginning of value;
%!!(MISSING)w(<nil>)
> Unexpected error:
> <*errors.errorString | 0xc00051a2d0>:
> failed to execute curl command against health endpoint in container
data-index-service:invalid character 'I' looking for beginning of value;
%!w(<nil>)
> {
> s: "failed to execute curl command against health endpoint in
container data-index-service:invalid character 'I' looking for beginning of
value; %!w(<nil>)",
> }
> occurred
> ```
>
> I am currently not sure why this is happening, locally it passes. Should
be investigated to keep the CI stable.
It's because the e2e job has set `DEBUG=true` as environment value and the
kubectl starts adding log entries in the `kubectl exec -it` command, which
causes parsing issues. This is an example of what is returned from the command
in a test run:
```
running: kubectl --v=0 exec -t callbackstatetimeouts-7bf6f9f7f6-hg48m -n
test-511 -c workflow -- curl -s localhost:8080/q/health
I0118 18:50:33.207120 46502 log.go:194] (0x140000e6420) (0x140004a4e60)
Create stream
I0118 18:50:33.207262 46502 log.go:194] (0x140000e6420) (0x140004a4e60)
Stream added, broadcasting: 1
I0118 18:50:33.208525 46502 log.go:194] (0x140000e6420) Reply frame
received for 1
I0118 18:50:33.208535 46502 log.go:194] (0x140000e6420) (0x1400072e000)
Create stream
I0118 18:50:33.208538 46502 log.go:194] (0x140000e6420) (0x1400072e000)
Stream added, broadcasting: 3
I0118 18:50:33.209173 46502 log.go:194] (0x140000e6420) Reply frame
received for 3
I0118 18:50:33.209181 46502 log.go:194] (0x140000e6420) (0x140004f6460)
Create stream
I0118 18:50:33.209183 46502 log.go:194] (0x140000e6420) (0x140004f6460)
Stream added, broadcasting: 5
I0118 18:50:33.209632 46502 log.go:194] (0x140000e6420) Reply frame
received for 5
I0118 18:50:33.245994 46502 log.go:194] (0x140000e6420) Data frame
received for 3
I0118 18:50:33.246002 46502 log.go:194] (0x1400072e000) (3) Data frame
handling
I0118 18:50:33.246006 46502 log.go:194] (0x1400072e000) (3) Data frame
sent
{
"status": "UP",
"checks": [
{
"name": "SmallRye Reactive Messaging - liveness check",
"status": "UP"
},
{
"name": "alive",
"status": "UP"
},
{
"name": "Database connections health check",
"status": "UP",
"data": {
"<default>": "UP"
}
},
{
"name": "SmallRye Reactive Messaging - readiness check",
"status": "UP"
},
{
"name": "SmallRye Reactive Messaging - startup check",
"status": "UP"
}
]
}I0118 18:50:33.246382 46502 log.go:194] (0x140000e6420) Data frame
received for 3
I0118 18:50:33.246389 46502 log.go:194] (0x1400072e000) (3) Data frame
handling
I0118 18:50:33.246398 46502 log.go:194] (0x140000e6420) Data frame
received for 5
I0118 18:50:33.246400 46502 log.go:194] (0x140004f6460) (5) Data frame
handling
I0118 18:50:33.247459 46502 log.go:194] (0x140000e6420) Data frame
received for 1
I0118 18:50:33.247468 46502 log.go:194] (0x140004a4e60) (1) Data frame
handling
I0118 18:50:33.247471 46502 log.go:194] (0x140004a4e60) (1) Data frame
sent
I0118 18:50:33.247475 46502 log.go:194] (0x140000e6420) (0x140004a4e60)
Stream removed, broadcasting: 1
I0118 18:50:33.247478 46502 log.go:194] (0x140000e6420) Go away received
I0118 18:50:33.247571 46502 log.go:194] (0x140000e6420) (0x140004a4e60)
Stream removed, broadcasting: 1
I0118 18:50:33.247579 46502 log.go:194] (0x140000e6420) (0x1400072e000)
Stream removed, broadcasting: 3
I0118 18:50:33.247583 46502 log.go:194] (0x140000e6420) (0x140004f6460)
Stream removed, broadcasting: 5
```
I noticed this while troubleshooting
https://github.com/apache/incubator-kie-kogito-serverless-operator/pull/322 . I
removed the env variable in the job and the problem disappeared. If that
variable is required for other reasons I can resort in setting it to `false`
before calling the `make test-e2e` target. Let me know what you think.
--
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]
