You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Alena Prokharchyk (JIRA)" <ji...@apache.org> on 2013/07/11 00:37:48 UTC

[jira] [Resolved] (CLOUDSTACK-3455) deleteDomain doesn't cleanup the domain level networks

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alena Prokharchyk resolved CLOUDSTACK-3455.
-------------------------------------------

    Resolution: Fixed

Fixed in both 4.2 and master branches with commit c7795651ecb55ada5836c6659dace07834b102f0.
                
> deleteDomain doesn't cleanup the domain level networks
> ------------------------------------------------------
>
>                 Key: CLOUDSTACK-3455
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3455
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0
>            Reporter: Alena Prokharchyk
>            Assignee: Alena Prokharchyk
>             Fix For: 4.2.0
>
>
> DeleteDomain doesn't clear the corresponding network resources. The problem happens because the domain owner is stored in another table -
> network_domain_ref, and the createNetwork caller info (account_id, domain_id)
> gets stored in networks table. Here is the example of the network created in
> domain id=2 by the ROOT admin (who belongs to domain id=1):
> mysql> select id,uuid,name,domain_id from networks where id=204;
> +-----+--------------------------------------+--------+-----------+
> | id  | uuid                                 | name   | domain_id |
> +-----+--------------------------------------+--------+-----------+
> | 204 | 75e20ab4-e133-4c4b-a9be-cc54678ea819 | shared |         1 |
> +-----+--------------------------------------+--------+-----------+
> 1 row in set (0.00 sec)
> mysql> select * from domain_network_ref where network_id=204;
> +----+-----------+------------+------------------+
> | id | domain_id | network_id | subdomain_access |
> +----+-----------+------------+------------------+
> |  1 |         2 |        204 |                0 |
> +----+-----------+------------+------------------+
> But when delete is called for the domain, we try to locate all its networks by
> the network.domain_id reference, and as it always has domain_id=1 there, so the
> network is skipped from the deletion.
> The fix will be - when delete the network, query shared networks by domain_id
> based on the information present in domain_network_ref table.

--
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