[jira] [Created] (CLOUDSTACK-2390) [GSLB] After removeFromGSLBRule, still CloudStack things that lb rule is active

["venkata swamybabu budumuru (JIRA)" <ji...@apache.org>]

venkata swamybabu budumuru created CLOUDSTACK-2390:
------------------------------------------------------

             Summary: [GSLB] After removeFromGSLBRule, still CloudStack things that lb rule is active
                 Key: CLOUDSTACK-2390
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2390
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Network Controller
    Affects Versions: 4.2.0
         Environment: commit # 09af15035b9febe6f55e73a1389f950ab042564f
            Reporter: venkata swamybabu budumuru
            Assignee: Murali Reddy
             Fix For: 4.2.0


Steps to reproduce :

1. Have cloudstack with at least one Zone and one physical network that is enabled with GSLB provider
2. As a non-ROOT domain user, create a GSLB rule.


mysql> select * from global_load_balancing_rules;
+----+--------------------------------------+------------+-----------+-----------+-------+-------------+--------+------------+-------------+--------------+------------------+
| id | uuid                                 | account_id | domain_id | region_id | name  | description | state  | algorithm  | persistence | service_type | gslb_domain_name |
+----+--------------------------------------+------------+-----------+-----------+-------+-------------+--------+------------+-------------+--------------+------------------+
| 11 | ba054e83-e436-40f3-be85-dcb802033ad7 |          5 |         2 |         1 | GSLB1 | GSLB1       | Staged | roundrobin | sourceip    | tcp          | GSLB1            |
+----+--------------------------------------+------------+-----------+-----------+-------+-------------+--------+------------+-------------+--------------+------------------+

3. Add at least one lb rule to the above GSLB rule.

mysql> select * from global_load_balancer_lb_rule_map;
+----+--------------+------------+--------+
| id | gslb_rule_id | lb_rule_id | revoke |
+----+--------------+------------+--------+
| 11 |           11 |          7 |      0 |
+----+--------------+------------+--------+

4. Execute removeFromGlobaLoadBalancerRule to remove the above lb rule which was just added above

remove fromgloballoadbalancerrule id=ba054e83-e436-40f3-be85-dcb802033ad7 loadbalancerrulelist=9b5267df-eaf5-41ae-bc46-dc61fa5e9024

mysql> select * from global_load_balancer_lb_rule_map;
+----+--------------+------------+--------+
| id | gslb_rule_id | lb_rule_id | revoke |
+----+--------------+------------+--------+
| 11 |           11 |          7 |      1 |
+----+--------------+------------+--------+
1 row in set (0.00 sec)

Observations:

(i) Thought it is marked as revoked, it still shows up in the UI as active.
(ii) Now tried to add different LB rule that exists in the same zone and it failed with the following error

"Load balancer rule specified should be in unique zone"

(iv) The above error proves that cloudstack still assumes that rule in revoked state as active and it failed to add a different rule.

Attaching all the required logs along with db dump to the bug.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira