cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nux! <...@li.nux.ro>
Subject Re: Cannot delete range as IP is being used for providing dhcp service in this subnet
Date Tue, 03 Mar 2015 23:18:24 GMT
Hi Marcus,

Yes, shared guest networks.

I'll try your way.

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

----- Original Message -----
> From: "Marcus" <shadowsor@gmail.com>
> To: dev@cloudstack.apache.org
> Sent: Tuesday, 3 March, 2015 22:20:05
> Subject: Re: Cannot delete range as IP is being used for providing dhcp service in this
subnet

> We're not talking guest networks, right?  In the past I've been able
> to remove these by disabling the zone, then deleting the router and/or
> applicable system vms. Disabling the zone ensures the system vms don't
> come back up. The vms do have to expunge though before you'll have any
> luck.
> 
> On Tue, Mar 3, 2015 at 2:06 PM, Somesh Naidu <Somesh.Naidu@citrix.com> wrote:
>> Lucian,
>>
>> Not sure if you can get past that without destroying that network (or
>> manipulating the DB).
>>
>> I am not sure if network restart with cleanup true releases the VR IP so you
>> probably could try that. If it does, then we'd have to figure how to avoid the
>> new IP getting chosen from the same IP range.
>>
>> Regards,
>> Somesh
>>
>>
>> -----Original Message-----
>> From: Nux! [mailto:nux@li.nux.ro]
>> Sent: Tuesday, March 03, 2015 2:31 PM
>> To: dev
>> Subject: [4.5] Cannot delete range as IP is being used for providing dhcp
>> service in this subnet
>>
>> Hi,
>>
>> I'm having this problem, I've added a secondary subnet/range in my Adv+SG zone
>> and now I want to delete it.
>> All the VMs using it have been deleted (and I've been waiting for a while for
>> the explunge/cleanup jobs to run), yet I am getting this error:
>>
>> "Cannot delete vlan range 2 as 192.168.203.102 is being used for providing dhcp
>> service in this subnet. Delete all VMs in this subnet and try again"
>>
>> All the VMs are deleted, only the virtual router is using IPs from that range.
>>
>> root@r-4-VM:~# ip a|grep 192.168
>>     inet 192.168.203.102/24 brd 192.168.203.255 scope global eth0:55
>>     inet 192.168.203.103/24 brd 192.168.203.255 scope global secondary eth0:56
>>
>> How can I make the VR let go of those IPs?
>>
>> Lucian
>>
>> --
>> Sent from the Delta quadrant using Borg technology!
>>
>> Nux!
> > www.nux.ro

Mime
View raw message