Status checking of streaming "daemon"-s is buggy and misleading

When a daemon is started Solr randomly picks a replica to process that request and then it executes in the context of that particular replica. The response from the request mentions this specifically:

{
  "result-set":{
    "docs":[{
        "DaemonOp":"Deamon:testD1 started on gettingstarted_shard2_replica_n6"}
      ,{
        "EOF":true}]}}

Subsequent requests to /solr/gettingstarted/stream?action=list only sometimes return the status of this daemon, specifically only when the request is randomly routed to the actual replica that the daemon is running on - in other cases the response doesn't show the running daemon.

This is very easy to reproduce using the cloud example with 2 (local) nodes and a source collection with multiple shards and multiple replicas.

Currently the only workaround is to request the status using a non-cloud core URL - in this case a request to /solr/gettingstarted_shard2_replica_n6/stream?action=list always returns correct status.