yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #43633
[Bug 1508106] Re: For wrong ethertype exception message is hard coded
Reviewed: https://review.openstack.org/258971
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=be14e905419f0927539e939c1f979430a6e44d42
Submitter: Jenkins
Branch: master
commit be14e905419f0927539e939c1f979430a6e44d42
Author: Sreekumar S <sreesiv@xxxxxxxxx>
Date: Thu Dec 17 02:34:33 2015 +0530
Corrected wrong ethertype exception message
This patch resolves the issue where wrong message was being
shown when ethertype input parameter was not amongst one of
the types supported. New message made akin to other input
parameters like 'protocol'.
Change-Id: I5636f3582c9d9877dad4d091a374284b656923f4
Closes-Bug: #1508106
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1508106
Title:
For wrong ethertype exception message is hard coded
Status in neutron:
Fix Released
Bug description:
if you give any wrong ethertype while creating security group rule.
it will always mention reason None in exception message
Invalid input for ethertype. Reason: 'None' is not in ['IPv4',
'IPv6'].
try
neutron security-group-rule-create --ethertype ip --protocol icmp
<group-id>
it will print
Invalid input for ethertype. Reason: 'None' is not in ['IPv4', 'IPv6'].
but actually it should be Invalid input for ethertype. Reason: 'ip' is
not in ['IPv4', 'IPv6'].
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1508106/+subscriptions
References