eelarapu"
> To: dev@cloudstack.apache.org
> Sent: Wednesday, 4 March, 2015 04:32:03
> Subject: RE: Cannot delete range as IP is being used for providing dhcp
> service in this subnet
> Hi Nux,
>
> In shared network we keep the guestipaddress that router gets in allocated
...@gmail.com]
Sent: Wednesday, March 04, 2015 7:29 AM
To: dev@cloudstack.apache.org
Subject: Re: Cannot delete range as IP is being used for providing dhcp service
in this subnet
I assume you can make sense of these queries, install something like MySQL
Workbench - or tool you like the most for
age -
From: "Marcus"
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 dis
ing it that way.
Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
> From: "Nux!"
> To: dev@cloudstack.apache.org
> Sent: Tuesday, 3 March, 2015 23:18:24
> Subject: Re: Cannot delete range as IP is being used for pro
annot 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 ensure
Nux!
www.nux.ro
- Original Message -
> From: "Somesh Naidu"
> To: dev@cloudstack.apache.org
> Sent: Tuesday, 3 March, 2015 22:06:44
> Subject: RE: Cannot delete range as IP is being used for providing dhcp
> service in this subnet
> Lucian,
>
> No
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, Ma
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
