Comment 52 for bug 1443798
Revision history for this message
| Salvatore Orlando (salvatore-orlando) wrote | #52 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
cd293fb
demo site
(Get the code!)
An empty allocation pool [] is a valid value. However it's not compatible with DHCP.
I am not sure if this should return an error to the API caller, on result in a failure which is handled by the agent (thus avoiding the resync).
the fact that the DHCP needs an IP address from a pool is indeed an implementation feature of agent-based DHCP. I know neutron does not have any other kind of support for DHCP at the moment, but I'm not sure we should surface this implementation details at the API layer. (I'm not sure means that I'm thinking about it, not that I think it's wrong).
The fix should be backported, yes. I am ok with backporting it even if it changes API constraints, assuming the stable team is fine with that.
Also, I think, as Tristan said that the OSSA criteria for this bug should be those we established for its first occurrence, and for bug 1362651.
Finally, if the people looking after the DHCP agent would try and find a solution to avoid the perennial resync loop for good, that would be great.