Mark Grondona

My guess is you're quoting of the entire `--setattr` option caused argparse to treat `exec.test.run_duration=0.1s hostname` as its entire argument, thus there was no "remainder" to represent the command and...

You can try `srun -N2 -n2 flux start sleep inf` to run `sleep inf` as the initial program of your Flux instance, then attempt to connect with `flux proxy slurm:JOBID`....

> It is only node2 that fails. Ah, that is a good clue. That probably indicates that for some reason on your Slurm cluster, Flux isn't properly bootstrapping via Slurm...

For some added background, when launching Flux under Slurm, Flux is bootstrapping in the same way as an MPI job for its wire-up. Only the "rank 0" flux-broker will start...

After the Flux instance is established, though, you would need `ssh` access to make use of `flux proxy`.