Cool, thanks for your response.
I think that the required change will probably need to be more
sophisticated than the one you showed (and I advised against hot-fixing
your quantum server this way); reason being, the dhcp agent's behavior
might be unexpected, especially if there was a port already associated
with the gateway ip.
I also noticed that by using the quantum client, I am unable to reset
the gateway-ip, as None or null do not parse correctly (they end up
being marshalled into a string). I will follow that up with the client-
side of the project, but for now, I think it would be sensible to gather
more input/opinion from whom is more experienced with dhcp than I am, as
I suspect that _removing_ a gateway from an existing subnet is not
something that was initially planned.
** Changed in: quantum
Status: Confirmed => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to quantum.
https://bugs.launchpad.net/bugs/1178273
Title:
unable to unset gateway_ip on existing subnet
Status in OpenStack Quantum (virtual network service):
Opinion
Bug description:
A subnet can be configured without a gateway_ip if the gateway_ip is
set to null when the subnet is initially created. However it is not
possible to change the gateway_ip to null for an existing subnet.
Trying to unset a subnet's gateway_ip/set it to null, results in a
'failed to detect a valid IP address from None' QuantumError.
This can be easily corrected with the attached diff
To manage notifications about this bug go to:
https://bugs.launchpad.net/quantum/+bug/1178273/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
