cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-10344) Sometimes a bug happens when moving ACL rules (changing their order with drag and drop)
Date Thu, 05 Apr 2018 10:26:00 GMT


ASF GitHub Bot commented on CLOUDSTACK-10344:

rafaelweingartner commented on issue #2511: [CLOUDSTACK-10344] bug when moving ACL rules (change
order with drag and drop)
   I looked into it. The test failed because the uptime of the VR is less than 3 minutes?

   This looks like a "test" prone to fail due to environment differences. Shall we execute
the tests again?
   Traceback (most recent call last):
     File "/marvin/tests/smoke/", line 526, in test_04_restart_network_wo_cleanup
       "Check uptime is less than 3 mins or not"
   AssertionError: Check uptime is less than 3 mins or not

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> Sometimes a bug happens when moving ACL rules (changing their order with drag and drop)

> ----------------------------------------------------------------------------------------
>                 Key: CLOUDSTACK-10344
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Rafael Weingärtner
>            Assignee: Rafael Weingärtner
>            Priority: Major
>             Fix For: 4.12
> An error is happening in certain conditions, such as when you have only 2 ACL rules and
you move the last one to the top. There are other conditions, for instance, when moving ACLs
that are in a sequence of numbers without gaps.
> Example, rules:
> number | rule
> 1 - rule A
> 2 - rule D
> 3 - rule B
> 4 - rule C
> 5 - rule E
> It is not possible to move "rule C" in position 2, 1, and 3.

This message was sent by Atlassian JIRA

View raw message