The script based tests are passing but with parse errors in the pipelines.

Bug

Description

Current Fluentbit script based tests are passing but with parse errors in the pipelines. Below is the test logs, and bease of parse errors we dont know for sure if tests are checking everything correctly.

Running api-check.sh...
---
Hitting Fluentbit endpoint...

real	0m0.027s
user	0m0.000s
sys	0m0.006s
Test 1 Success: Fluentbit is up, see above for curl's elapsed wait time.
Checking Fluentbit version...
parse error: Invalid numeric literal at line 1, column 5
./api-check.sh: line 18: [: 4.0.0: unary operator expected
Test 2 Success: Fluentbit version matches.
Waiting 15 seconds to allow Fluentbit to collect some records...
Checking Fluentbit records input...
parse error: Invalid numeric literal at line 1, column 5
./api-check.sh: line 32: [: !: integer expression expected
Test 3 Success: Fluentbit has received  records.
Checking Fluentbit records processed...
parse error: Invalid numeric literal at line 1, column 5
./api-check.sh: line 43: [: !: integer expression expected
Test 4 Success: Fluentbit has processed  records.
Checking Fluentbit processing errors...
parse error: Invalid numeric literal at line 1, column 5
./api-check.sh: line 54: [: -gt: unary operator expected
Test 5 Success: Fluentbit has had 0 processing errors.

Every Fluentbit package pipeline has the same issue.

BigBang Version

2.50

This can be retrieved multiple ways:

# via helm
helm ls -n bigbang

# via the deployed umbrella git tag
kubectl get gitrepository -n bigbang