cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kirk Kosinski <kirkkosin...@gmail.com>
Subject Re: Stale datastores in database?
Date Thu, 28 Aug 2014 18:29:58 GMT
Hi, what CS version is this, and can you upload more of the log?  It
seems likely to be a bug since the storage with removed != NULL in the
database should be ignored.

Best regards,
Kirk

On 08/28/2014 09:19 AM, Martin Emrich wrote:
> Hi!
> 
> I had to remove a XenServer host (the only one) from Cloudstack, removed it via GUI,
worked well.
> 
> Now I added the replacement machine, and tried to fire up an instance. But I got the
message "Unable to locate datastore with id 1".
> In the database, the storage_pool table contained two entries, the old id 1 and the current
id 2.
> I removed the host (and then replaced the EXT storage with a LVM storage because I misconfigured
it), and added it again. Now I have three entries in the database, and creating an instance
still fails.
> 
> The database now looks like this:
> 
> mysql> select * from storage_pool;
> +----+-----------------------------+--------------------------------------+-----------+------+----------------+--------+------------+------------+----------------+--------------+-----------+------+---------------------+---------------------+-------------+-------------+-----------------------+-------+------------+---------+---------------+
> | id | name                        | uuid                                 | pool_type
| port | data_center_id | pod_id | cluster_id | used_bytes | capacity_bytes | host_address
| user_info | path | created             | removed             | update_time | status    
 | storage_provider_name | scope | hypervisor | managed | capacity_iops |
> +----+-----------------------------+--------------------------------------+-----------+------+----------------+--------+------------+------------+----------------+--------------+-----------+------+---------------------+---------------------+-------------+-------------+-----------------------+-------+------------+---------+---------------+
> |  1 | esc-compute01 Local Storage | NULL                                 | LVM     
 |    0 |              1 |      1 |       NULL |    4194304 |  1190452527104 | 10.8.0.65 
  | NULL      | lvm  | 2014-08-08 14:37:25 | 2014-08-18 08:33:43 | NULL        | Maintenance
| DefaultPrimary        | HOST  | NULL       |       0 |          NULL |
> |  2 | esc-compute01 Local Storage | NULL                                 | EXT     
 |    0 |              1 |      1 |       NULL | 6161043456 |  1171772600320 | 10.8.0.66 
  | NULL      | ext  | 2014-08-27 15:53:58 | 2014-08-28 15:50:41 | NULL        | Maintenance
| DefaultPrimary        | HOST  | NULL       |       0 |          NULL |
> |  3 | esc-compute01 Local Storage | c38b4fa3-4bd4-05a3-4a11-e5e0f15fb9f5 | LVM     
 |    0 |              1 |      1 |          1 |    4194304 |  1190452527104 | 10.8.0.66 
  | NULL      | lvm  | 2014-08-28 15:52:14 | NULL                | NULL        | Up      
   | DefaultPrimary        | HOST  | NULL       |       0 |          NULL |
> +----+-----------------------------+--------------------------------------+-----------+------+----------------+--------+------------+------------+----------------+--------------+-----------+------+---------------------+---------------------+-------------+-------------+-----------------------+-------+------------+---------+---------------+
> 3 rows in set (0.00 sec)
> 
> In the GUI, I can only see one Primary Storage (the current "real" one, obviously ID
3).
> 
> How can I fix my Cloudstack? As there are no instances yet, I could reinstall, but I'd
like to understand what's going on...
> 
> Thanks
> 
> Martin Emrich
> 

Mime
View raw message