Certain playbook output has unexpected delays

[ryanpetrello]

Run this playbook on an awx install that is doing little or nothing else:

---

- hosts: all
  gather_facts: false
  tasks:
    - shell: 'echo "Hello, World" && sleep .1'
      with_sequence: start=0 end=100

...observe that none of the events are recorded, nor does any of the stdout show up in the UI until the playbook command finishes executing (then everything shows up at the end in a giant burst).

[kdelee]

fwiw I started to look at this in my local dev environment

I noticed that running something like https://github.com/ansible/test-playbooks/blob/master/chatty_tasks.yml with 1 host and 5000 messages, I did not get any output until the end of the playbook run.

Tried blowing away all my containers and starting fresh, but now I'm having trouble getting ti to run at all (stuck at Attatching to tools_awx_1).

will continue tomorrow

[kdelee]

@ryanpetrello I'm still seeing some weird behavior when I try also on an ec2 instance

here's a gif trying to capture what I'm seeing.

Essentially a little bit of stdout will show when launching the job, but then it just does not update until I do a hard refresh

not saying your change was not good -- but does not seem sufficient to say that there is not any other "unexpected delays"

[ryanpetrello]

@kdelee for what it's worth, the new UI may make this hard to troubleshoot/verify - @jakemcdermott suggested to me that there may still be some streaming stdout warts?

@kdelee if you open the websocket tab in a browser console, are you able to see messages come in?

[kdelee]

not that I can tell, but maybe I'm not reading this right.

Also worth mentioning that the "elapsed" timer does not update until the end of the job either

Here is a video. Wait for it -- it looks static but thats because nothing updates until after the job is done (is about 1 min and change)

[kdelee]

We're still seeing this

[ryanpetrello]

@kdelee I wonder if this is similar to #9747

[kdelee]

It is hard to fully determine if this is fixed until the websocket problems are fixed.