Hi Florian,
I am unsure I am qualified to answer as I have limited experience with multinode jobs, but that is what it seems like youre working with (please correct me if that assumption is wrong).
When looking at a (multinode) job itself, it will have what I call a "display id" and a "functional id". The display id is the 132.0 and 132.1 in your presented case, but the functional ids are 132 and 133, being that when requesting job information via lavacli or the RPC api, you use the functional id. I don't think it's a bug, but either a weird intentional implementation or a limitation (old or current, I am unsure) of something else.
This can be quite bothersome I think if you are going to submit several jobs at one time, and the only way to predict what the ids are going to be in advance is knowing how many jobs are being submitted, and how many devices are involved in each test.
Again, my experience with multinode is limited as I don't use, nor need to use, multinode tests. As such, I may be wrong or only partially correct, so take my words with a grain of salt.
Best regards, Michael