Comment 11 for bug 1443798

Hello, @Armando Migliaccio (armando-migliaccio)

Thank you for your help.
Please let me correct my words in #4.
YES, VM would be boot fine, and YES, the effect would be lack of dynamic IP allocation.
The problem only affect new created VMs with dynamic IP allocation, that no IPs will be allocated due to the time out of the allocation.

About your comment in #10, that we should find a way to avoid the resync loop from the agent side. I couldn't agree with it any more. Which it is my first thought, too.
But due to the time limit, I would like to give a first add first.
/64 is already been restricted, so I would like to leave it as it is, if there is not any other request.
/32, /31 is reasonable when enable_dhcp is False, but after the creation, if someone updated the subnet enable_dhcp to True, the resync will happen, too.

So the only way I got is to restrict /32, /31 subnet creation, until we found a way to avoid the resync loop from the agent side.