-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
False
-
-
False
-
-
The Sonobuoy Aggregator API is reporting errors[1] to process the body when the plugins sends a payload with a large amount of errors.
[1] errors reporting on the aggregator (sonobuoy pod):
time="2023-01-11T18:57:04Z" level=info msg="received request" client_cert="[20-openshift-conformance-validated]" method=POST plugin_name=20-openshift-conformance-validated url=/api/v1/progress/global/20-openshift-conformance-validated time="2023-01-11T18:57:04Z" level=error msg="Failed to get progress update from request: unable to decode body: invalid character '[' after array element"
When looking to the 'report-progress' container, on plugin, the payload looks like:
<truncated payload>
It was caused when in the 'upgrade' feature implementation, when the conformance plugin was running with an old version of openshift-tests.
Steps to reproduce:
- Run OPCT
- make sure the openshift-tests and oc utilities are outdated before running (it must change the plugin removing this patch and this.
- Check the logs of pod plugin, container 'report-progress'. The number of messages on the payload sent by aggregator should be large.
Suggestion to fix on OPCT:
- prevent the bug (fixes on
OPCT-7) - prevent to send large payloads: patch to truncate failures items to an ID, instead of e2e name (it will not affect the final results)
Long-term solution: this is a bug on the Sonobuoy Aggregator. It should be handled on the API refusing large payloads, returning some HTTP code.
- is documented by
-
OPCT-7 [bug][backend] Sonobuoy's aggregator stop working after cluster upgrades
- Closed