Created attachment 902455 [details] screen shot with several Network QOS entities with the same name Description of problem: By clicking quickly on ok button during creation of Network QOS entity we managed to create that entity twice under the specific DC. Version-Release number of selected component (if applicable): How reproducible: Sometimes - it happens always on slow environment Steps to Reproduce: 1. Create new Network QOS entity 2. Fill in parameters 3. Click several times quickly on ok button Actual results: Several entities of Network QOS with the same parameters will be created Expected results: It should be impossible to create more than one Network QOS entity with the same parameters Additional info: It looks like Network QOS is not a single entity that we can create the same instance more than once when it should be blocked
Although this was opened on the GUI (and could be blocked specifically in the GUI), the same problem could probably be triggered via the API by sending two identical add commands at close proximity. Therefore, this should probably be solved in the backend; one alternative would be to define a uniqueness constraint on the DB by a name/DC combination (which should cause one of the actions to fail since the other has already created the DB entry).
Moving to SLA as starting from 3.5 QoS entities are their domain.
3.5.1 is already full with bugs (over 80), and since none of these bugs were added as urgent for 3.5.1 release in the tracker bug, moving to 3.5.2
Verified on - 3.6.0-0.0.master.20150412172306.git55ba764.el6
this bug has both 3.5.z & 3.6.0 flags, in bugzilla lang it means its a clone candidate from 3.6.0 to 3.5.z meaning it's pending a clone and wasn't fixed for 3.5.z. if this isn't the case, please fix flags accordingly, if it is the case, then please clone the bugs to 3.5.7 (3.5.6 was built already)