No resolution yet. I also this issue is a bug in vCloud 5.5.1a. Previously, I used vCloud 5.1.0 without this issue.
I think the current workaround is to control the startup order of VM to get external IP from the pool. Then check "Retain IP/MAC Resources" in vApp network.