Absolutely, I'll get that submitted right away. Thanks
On Jul 5, 2012, at 12:06 AM, Prasanna Santhanam wrote: > On Thu, Jul 05, 2012 at 01:58:20AM -0400, Caleb Call wrote: >> I saw Sailaja email before seeing this one, so I did remove all the >> rows that were Expunging in the vm_instance table. They were all >> system VMs that failed to start due to the initial problem of >> needing vlan support. Although, even after removing them, I still >> can't remove the pod. So I tried to cross reference >> op_dc_ip_address_alloc table with nics and my nics table is empty >> (and all nic_ids in op_dc_ip_address_alloc are set to null >> anyways). >> >> Our current versions are: >> >> Cloudstack - 3.0.2 >> OS - CentOS 6.2 >> Mysql - 5.1.61 (if this info matters) >> > Caleb, > > We could still salvage something here. If you could bundle up the: > > - management server log (/var/log/cloud/management/management-server.log) > - mysql db dump (mysqldump -uroot -p<password> cloud > cloud_backup.sql) > > into a tarball and file a bug for us at bugs.cloudstack.org we could > track this down. Do attach the logs to the bug report. > > > Thanks, > > -- > Prasanna., > > >> Thanks >> >> On Jul 4, 2012, at 11:39 PM, Prasanna Santhanam wrote: >> >>> On Thu, Jul 05, 2012 at 01:26:26AM -0400, Sailaja Mada wrote: >>>> >>>> Can you remove the entries from vm_instance table and then try >>>> deleting the POD. >>>> >>> >>> That's a bad idea - Expunging is the final state of a VM. These are >>> valid entries. As Ahmad pointed out only if you have any that are >>> "Expunging" but failed to be marked as removed would those be invalid >>> entries to look out for. >>> >>> The private IP addresses can be found in the op_dc_ip_address_alloc >>> table. Corresponding to each row in there is a nic_id. Pick the ones >>> with a non-null nic_id and check against the nics table to see if that >>> nic_id is removed. The ones that are in use are in "Reserved" state. >>> >>> Deleting of a zone has been an issue in 3.0.0 IIRC. Which version are >>> you at? >>> >>> -- >>> Prasanna., >>> >>>> >>>> -----Original Message----- >>>> From: Caleb Call [mailto:[email protected]] >>>> Sent: Thursday, July 05, 2012 2:42 AM >>>> To: [email protected] >>>> Subject: Re: Removing a Zone >>>> >>>> @Edison - That's the state we're currently in. The zone is >>>> disabled. We basically removed everything starting with secondary >>>> storage. So we removed Secondary storage, Primary storage, Hosts, >>>> and Clusters. We now can't remove the pod (or zone) because of this >>>> error. >>>> >>>> @Sailaja - That query returns ~2800 rows, but no private IPs are >>>> assigned. However, it looks like all of them are stuck in an >>>> Expunging state. Can I just remove those from the database? >>>> >>>> mysql> select state,COUNT(*) from cloud.vm_instance; >>>> +-----------+----------+ >>>> | state | COUNT(*) | >>>> +-----------+----------+ >>>> | Expunging | 2803 | >>>> +-----------+----------+ >>>> 1 row in set (0.02 sec) >>>> >>>> @Geoff - See above, we have been able to remove everything up to the >>>> pod level, including system VMs and even the hypervisors (hosts). >>>> >>>> At this point, with no hosts added, I can't see any possible way an >>>> IP is actually being used. >>>> >>>> Thanks guys for the quick responses. >>>> >>>> On Jul 4, 2012, at 1:14 AM, Geoff Higginbottom wrote: >>>> >
