yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #70465
[Bug 1699724] Re: Incorrect message displayed during creation of new secgroup rules if quota exceeded
Reviewed: https://review.openstack.org/534462
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=3929a8b7cd893f0b4c0ff6c20d5d1fd9077b4dd2
Submitter: Zuul
Branch: master
commit 3929a8b7cd893f0b4c0ff6c20d5d1fd9077b4dd2
Author: Simon Collins <simoncollins99@xxxxxxxxx>
Date: Wed Jan 17 12:11:15 2018 +1300
Security group quota error handling
When adding a new rule to a secruity group that would exceede the
quota, the error message displays a quota error, rather than rule
already exists error. It does this my first checking for an
"OverQuotaClient" error, then if that except doesn't trigger it
checks for any other conflict
Change-Id: I8eaa0f00b25c8c3b75fef2bf46979f1f248c6896
Closes-Bug: #1699724
** Changed in: horizon
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1699724
Title:
Incorrect message displayed during creation of new secgroup rules if
quota exceeded
Status in OpenStack Dashboard (Horizon):
Fix Released
Bug description:
Using ocata horizon, I have set quota limit of securitygroup rules to say 2 for admin tenant and now if I try to add security group rules under sec group.
It shows "Error: Security group rule already exists".
Here expected error message should be "Error: Security group rules
quota exceeded"
Steps:-
Login to horizon
1) Go to Projects--> Identity--> admin--> manage members--> quota and set secgroup rule to 2.
2) Now goto project--> network-->Security groups--> default-->manage rules--> add rules --> all icmp and select ok.
3) Error message appeared is not correct.
Please correct error message if securitygroup rules quota exhausts and
user try to create securitygroup rule under security group.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1699724/+subscriptions
References