@hgangwx- As mentioned earlier, the issue mentioned in the bug is solved with
https://review.openstack.org/#/c/255217/
The bug gave an example of the case where we add router-gateway port and
mention the fixed IP explicitly ( leading to possibility of octal IP address
notation). This issue has
Hi Jas,
this bug is already fixed and merged, but current issue still exist, so they
are different issue.
** Changed in: neutron
Status: Invalid => New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
Did you change the status to Invalid by mistake?
There seems no reason to mark it as Invalid. Resetting to New.
** Changed in: neutron
Status: Invalid => New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
Ah I got it. The recent neutron commit fixed the same issue.
It makes sense to mark it as Invalid now.
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
Moved this to neutron since the validation code for ip addresses is done on the
back-end. This also looks like a non-issue. Found this in the validation code:
neutron/api/v2/attributes.py:_validate_ip_address
# A leading '0' in IPv4 address may be interpreted as an octal number,
#
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1531363
Title:
internal server error returned when set gateway of router with an
6 matches
Mail list logo
