Job output is not displayed fully #11765
Comments
|
I can see the same thing in the job log, some times it will not scroll at all.
In the AWX pod this is from the log (URL changed to a dummy version) |
|
I made the discovery, that this is more likely to happen, when I have some When fixing the deprecation warning, all is shown well in the logs. |
|
I don't think suppressing warnings is a good idea. They are needed to catch changes and update playbooks. |
|
But it seems like some of the warning messages cause output to disappear. |
That's what I meant. |
|
I'm having this same issue with 20.0.0. Applying search terms (for example appending url with ?job_output.not__stdout__startswith=[WARNING]) makes the missing lines appear in stdout (even warnings I thought I was filtering out, maybe I just can't use this search properly) |
|
Hi i confirm with ?job_output.not__stdout__startswith=[WARNING] all output is appear |
|
Hi all, Confirm that ?job_output.not__stdout__startswith=[WARNING] does the job. So it is all duplicate of #11647 |
Does it seem to fix the issue when you apply any search terms? |
|
@keithjgrant yes just apply not__stdout="" fix the stdout for me |
|
@keithjgrant I can also confirm this. I also noticed that the output field seem to have extra grayed lines after job summary when filtering a "broken" job output with ?job_output.not__stdout="". This doesn't seem to occur with ?job_output.not__stdout__startswith filter. |
|
@chris93111 Thanks. This confirms my suspicions. Performing a search disables the event nesting functionality (the expand/collapse arrows), so the page is more performant with a search filter applied. The problem is likely caused by the UI trying to determine how events are nested in parent/child relationships. Most of the network traffic in the screenshot above (#11765 (comment)) is used by the UI to determine how many child nodes each parent event has. This network traffic is much heavier than anticipated and is almost certainly the cause. Instead of these network requests, we need to see if the API can surface more information up front about the number of children for each event. |
|
@keithjgrant After clearing out the warnings in my code, I also experienced this issue when I have duplicate imports. I've tried all the variations of import, include, diff, including vars, dynamic task names, and no task names that I could think of. The allow_duplicates params didn't make any difference either. It presents similarly to the warnings issue, and it goes away with the same stdout query filters so I believe its the same root. I didn't see any other open issues specifically mentioning duplicate tasks, but I can see that you've been inundated with variations on #11765. Is it enough to tack it on to this issue or should I open a fresh issue referencing this? |
|
I also wanted to confirm, that even appending the url just with
|
|
Resolved |
|
sorry, how is this solved? by adding the filter each time? |
|
@stefanpinter |
|
ah, ok thank you :) |
|
The release cadence of AWX varies, however we try to release a new version of AWX every few weeks. If you feel comfortable running the HEAD of awx/devel then these changes will be immediately available. |
Please confirm the following
Summary
Some lines is grayed out in job output results
AWX version
19.5.1
Select the relevant components
Installation method
openshift
Modifications
no
Ansible version
2.9
Operating system
Win10
Web browser
Firefox, Chrome, Edge
Steps to reproduce
Run job with many line output
Expected results
See all output lines
Actual results
Many lines, specially toward end of the job just gray rectangles
or
Additional information
No response
The text was updated successfully, but these errors were encountered: