cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-2044) [ISOLATED] [Network GC + External Devices] VMs fail to get dhcp ip after Network GC
Date Fri, 03 May 2013 03:18:16 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648142#comment-13648142
] 

ASF subversion and git services commented on CLOUDSTACK-2044:
-------------------------------------------------------------

Commit 2510bf03f6d6b755fc82765c0363c2df43e4e401 in branch refs/heads/master from Sheng Yang
<sheng.yang@citrix.com>
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2510bf0 ]

CLOUDSTACK-2044: Use dnsmasq.conf.tmpl to generate dnsmasq.conf

We add something like dhcp-range_ip4/ip6 in the template for implementing
different setups.

                
> [ISOLATED] [Network GC + External Devices] VMs fail to get dhcp ip after Network GC
> -----------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2044
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2044
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller
>    Affects Versions: 4.1.0, 4.2.0
>         Environment: commit bc3e184b7273da605177b0ac4ed7186f7fa36fbd
>            Reporter: venkata swamybabu budumuru
>            Assignee: Sheng Yang
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> Steps to reproduce :
> 1. Have an advanced zone created with 1 Xen Cluster
> 2. create a network offering with SRX and Netscaler
> mysql> select * from ntwk_offering_service_map where network_offering_id=14;
> +----+---------------------+----------------+---------------+---------------------+
> | id | network_offering_id | service        | provider      | created             |
> +----+---------------------+----------------+---------------+---------------------+
> | 48 |                  14 | Dhcp           | VirtualRouter | 2013-04-15 09:49:58 |
> | 49 |                  14 | Dns            | VirtualRouter | 2013-04-15 09:49:58 |
> | 50 |                  14 | Firewall       | JuniperSRX    | 2013-04-15 09:49:58 |
> | 52 |                  14 | Lb             | Netscaler     | 2013-04-15 09:49:58 |
> | 51 |                  14 | PortForwarding | JuniperSRX    | 2013-04-15 09:49:58 |
> | 47 |                  14 | SourceNat      | JuniperSRX    | 2013-04-15 09:49:58 |
> | 46 |                  14 | StaticNat      | JuniperSRX    | 2013-04-15 09:49:58 |
> | 53 |                  14 | UserData       | VirtualRouter | 2013-04-15 09:49:58 |
> +----+---------------------+----------------+---------------+---------------------+
> 3. create a Network using the above offering
>                    id: 210
>                  name: ExtNet1
>                  uuid: 455f4a1c-204a-4d64-8357-63b9e562d5b7
>          display_text: ExtNet1
>          traffic_type: Guest
> broadcast_domain_type: Vlan
>         broadcast_uri: vlan://902
>               gateway: 10.0.32.1
>                  cidr: 10.0.32.0/20
>                  mode: Dhcp
>   network_offering_id: 14
>   physical_network_id: 200
>        data_center_id: 1
>             guru_name: ExternalGuestNetworkGuru
>                 state: Implemented
>               related: 210
>             domain_id: 2
>            account_id: 3
>                  dns1: 10.103.128.16
>                  dns2: NULL
>             guru_data: NULL
>            set_fields: 0
>              acl_type: Account
>        network_domain: cs3swamy.xen
>        reservation_id: 7f12298d-0c8a-41d7-9407-dd4744342c55
>            guest_type: Isolated
>      restart_required: 0
>               created: 2013-04-15 15:04:53
>               removed: NULL
>     specify_ip_ranges: 0
>                vpc_id: NULL
>           ip6_gateway: NULL
>              ip6_cidr: NULL
>          network_cidr: NULL
> 4. deploy VM using the above network
> 5. create some PF/static Nat rules
> 6. stop the above VM 
> Note : Make sure that "network.gc.interval" and "network.gc.wait" are  set to some small
value. in my case it is set to "10"
> Observations:-
> (i) Before GC the network got the CIDR as 10.0.64.0/20
> (ii) scavenger thread started and cleaned up all the config on the external device and
shutdown the network and set the state to "allocated"
> (iii) Again tried to deploy the VM which again brought the network to Implemented state
with a new CIDR i.e "	10.0.32.0/20"
> (iv) New VM failed to get the IP from router 
> (v) /etc/dnsmasq.conf contains the following lines that points to the old CIDR range
because of which it failed to allocate DCHP IP to the new range.
> (root@r-21-QA:~#)
> dhcp-range=10.0.64.1,static
> dhcp-hostsfile=/etc/dhcphosts.txt
> cat /etc/dhcphosts.txt
> root@r-21-QA:~# cat /etc/dhcphosts.txt 
> 02:00:7b:f2:00:01,set:10_0_33_11,10.0.33.11,VM1,infinite
> Attaching all the required logs along with /etc/dnsmasq.conf 

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

Mime
View raw message