You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're currently seeing a problem where a failed workflow's job internally gives an appropriate error message in its job events, but broker can't tells the user it can't find a failure reason.
This specific issue is because broker caps the job events to 200 results. However, there are jobs with close to 600 job events.
We need to find a way to better handle this. Filtering to only include failures would be the best if it is possible. Otherwise, bumping the page limits to 1000 (or paginating) may be our only options.
The text was updated successfully, but these errors were encountered:
We're currently seeing a problem where a failed workflow's job internally gives an appropriate error message in its job events, but broker can't tells the user it can't find a failure reason.
This specific issue is because broker caps the job events to 200 results. However, there are jobs with close to 600 job events.
https://github.com/SatelliteQE/broker/blob/master/broker/providers/ansible_tower.py#L373
We need to find a way to better handle this. Filtering to only include failures would be the best if it is possible. Otherwise, bumping the page limits to 1000 (or paginating) may be our only options.
The text was updated successfully, but these errors were encountered: