Rudder

I was just trying to fire off a client policy rtun from the Node details -> Compliance Reports -> Trigger agent run button.
Click the button, it grays out and shows Loading (Spinning Circle).
That makes sense.
But It seems to not work (idk)
And it stays like that... forever?
The normal run time of that agent is like 1-2 seconds, it's displaying the same thing since a few minutes now.

After like 5 minutes it aborted.

@502 - Proxy Error
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request

Reason: Error reading from remote server

Apache/2.4.25 (Debian) Server at 172.16.52.143 Port 443@

It would be good to see a "still trying, retrying etc." status. I was thinking it's in a dead code path.
Also the proxy error isn't so helpful, i don't know if there was one attempt with 300s timeout or 5 attempts, i don't know if an initial handshake worked etc.

If I imagine myself as a user with only GUI permissions (lets say they can set properties and launch a run) this gives them very little info.

If possible, document the phases of this process and build the message based on it.
"Failed at step 1 - connecting to agent for trigger. See <doc url>"
and <doc url> says:
"if you receive reports from the agent, it's a firewall issue
if you receive no reports from the agent, the agent might be down"

Footnote 1: at that point we see that, if we document this, rudder can diagnose the problem by it's own

Footnote 2: I checked the webapp logfile, nothing there, most likely it would be in some apache log. But my general understanding is "something didn't work", and for an UI-exposed feature I would like the UI to tell me what happened, not present me with an HTTP timeout.

Basically Rudder says "i tried something and here's proof it didn't work".

Footnote 3: I did a find / name parallel and didn't find it. If you should still rely on GNU parallel, you still miss a dependency to it. You need to have dependencies for the things you use ;)

Footnote 4: IMO this is a blocker, you can't release with GUI features that just bring up an HTTP error.