Using Cloudstack 3.02.
I've done this a couple of times now, with the same result.
After importing the cloud and the cloud_usage DB files from
the mysql backup run from the original controller, the replacement
Controller appears fully functional with one exception.
All templates, instances, physical resources, system VM's,
Dashboard, Snapshots, etc. seem to be reporting correctly
and the VM's and are fully accessible and functional.
However, the total storage reported under the Infrastructure
selection, shows the Total Storage to be 0.00 KB.
The Dashboard shows it as 3.62 TB which is correct.
1. How do I get the Infrastructure to agree with the resource?
I am getting the following blurb in the management-server.log:
2013-04-24 14:03:06,562 INFO [cloud.server.StatsCollector]
(StatsCollector-3:null) Unable to reach Pool[201|IscsiLUN]
com.cloud.exception.StorageUnavailableException: Resource [StoragePool:201]
is unreachable: Unable to send command to the pool
at
com.cloud.storage.StorageManagerImpl.sendToPool(StorageManagerImpl.java:1947
)
at
com.cloud.storage.StorageManagerImpl.sendToPool(StorageManagerImpl.java:448)
at
com.cloud.storage.StorageManagerImpl.sendToPool(StorageManagerImpl.java:462)
at
com.cloud.server.StatsCollector$StorageCollector.run(StatsCollector.java:307
)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$
201(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Sch
eduledThreadPoolExecutor.java:267)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:11
46)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:6
15)
at java.lang.Thread.run(Thread.java:679)
Warren
