That has been around since CloudStack 2.1, maybe even earlier. I don't think the status of secondary storage is ever used after it is added, so it's probably safe to manually set it to Up in the database (host table).
Best regards, Kirk On 04/01/2013 05:23 PM, Chiradeep Vittal wrote: > This would appear to be a known issue > https://issues.apache.org/jira/browse/CLOUDSTACK-668 > > > On 4/1/13 3:24 PM, "Carlos Reategui" <create...@gmail.com> wrote: > >> The "Host Alerts" panel on the main GUI page always show my secondary >> storage NFS as "Alert state detected" but I have no idea why. >> >> In my logs it keeps saying it is ready to launch an SSVM: >> 2013-04-02 03:46:10,049 DEBUG [agent.manager.DirectAgentAttache] >> (DirectAgent-130:null) Seq 1-1079905198: Executing request >> 2013-04-02 03:46:10,570 DEBUG [agent.manager.DirectAgentAttache] >> (DirectAgent-130:null) Seq 1-1079905198: Response Received: >> 2013-04-02 03:46:10,571 DEBUG [agent.transport.Request] >> (StatsCollector-1:null) Seq 1-1079905198: Received: { Ans: , MgmtId: >> 159090355471823, via: 1, Ver: v1, Flags: 10, { GetSto >> rageStatsAnswer } } >> 2013-04-02 03:46:14,166 DEBUG >> [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone 1 >> is ready to launch secondary storage VM >> 2013-04-02 03:46:14,314 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] >> (consoleproxy-1:null) Zone 1 is ready to launch console proxy >> 2013-04-02 03:46:14,653 DEBUG [storage.snapshot.SnapshotSchedulerImpl] >> (SnapshotPollTask:null) Snapshot scheduler.poll is being called at >> 2013-04-01 22:16:14 GMT >> 2013-04-02 03:46:14,655 DEBUG [storage.snapshot.SnapshotSchedulerImpl] >> (SnapshotPollTask:null) Got 0 snapshots to be executed at 2013-04-01 >> 22:16:14 GMT >> 2013-04-02 03:46:14,662 DEBUG >> [cloud.network.ExternalLoadBalancerUsageManagerImpl] >> (ExternalNetworkMonitor-1:null) External load balancer devices stats >> collector is running... >> 2013-04-02 03:46:14,687 INFO [cloud.ha.HighAvailabilityManagerImpl] >> (HA-5:null) checking health of usage server >> 2013-04-02 03:46:14,689 DEBUG [cloud.ha.HighAvailabilityManagerImpl] >> (HA-5:null) usage server running? false, heartbeat: null >> 2013-04-02 03:46:14,698 DEBUG >> [network.router.VirtualNetworkApplianceManagerImpl] (RouterMonitor-1:null) >> Found 0 running routers. >> 2013-04-02 03:46:14,699 DEBUG >> [network.router.VirtualNetworkApplianceManagerImpl] >> (RouterStatusMonitor-1:null) Found 0 routers. >> 2013-04-02 03:46:14,701 DEBUG [cloud.alert.AlertManagerImpl] (HA-5:null) >> Have already sent: 1 emails for alert type '12' -- skipping send email >> 2013-04-02 03:46:16,290 DEBUG [agent.manager.AgentManagerImpl] >> (AgentManager-Handler-14:null) Ping from 3 >> 2013-04-02 03:46:22,037 DEBUG [agent.manager.AgentManagerImpl] >> (AgentManager-Handler-15:null) Ping from 4 >> 2013-04-02 03:46:44,166 DEBUG >> [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone 1 >> is ready to launch secondary storage VM >> 2013-04-02 03:46:44,315 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] >> (consoleproxy-1:null) Zone 1 is ready to launch console proxy >> 2013-04-02 03:46:44,632 DEBUG [cloud.alert.AlertManagerImpl] >> (CapacityChecker:null) Running Capacity Checker ... >> 2013-04-02 03:46:44,632 DEBUG [cloud.alert.AlertManagerImpl] >> (CapacityChecker:null) recalculating system capacity >> 2013-04-02 03:46:44,632 DEBUG [cloud.alert.AlertManagerImpl] >> (CapacityChecker:null) Executing cpu/ram capacity update >> 2013-04-02 03:46:44,646 DEBUG [cloud.capacity.CapacityManagerImpl] >> (CapacityChecker:null) Found 4 VMs on host 1 >> 2013-04-02 03:46:44,647 DEBUG [cloud.capacity.CapacityManagerImpl] >> (CapacityChecker:null) Found 0 VM, not running on host 1 >> 2013-04-02 03:46:44,650 DEBUG [cloud.capacity.CapacityManagerImpl] >> (CapacityChecker:null) No need to calibrate cpu capacity, host:1 usedCpu: >> 3500 reservedCpu: 0 >> 2013-04-02 03:46:44,650 DEBUG [cloud.capacity.CapacityManagerImpl] >> (CapacityChecker:null) No need to calibrate memory capacity, host:1 >> usedMem: 5408555008 reservedMem: 0 >> 2013-04-02 03:46:44,651 DEBUG [cloud.alert.AlertManagerImpl] >> (CapacityChecker:null) Done executing cpu/ram capacity update >> 2013-04-02 03:46:44,651 DEBUG [cloud.alert.AlertManagerImpl] >> (CapacityChecker:null) Executing storage capacity update >> 2013-04-02 03:46:44,658 DEBUG [cloud.storage.StorageManagerImpl] >> (CapacityChecker:null) Successfully set Capacity - 422745128960 for >> capacity type - 9 , DataCenterId - 1, HostOrPo >> olId - 200, PodId 1 >> 2013-04-02 03:46:44,665 DEBUG [cloud.storage.StorageManagerImpl] >> (CapacityChecker:null) Successfully set Capacity - 15872695468032 for >> capacity type - 3 , DataCenterId - 1, HostOr >> PoolId - 201, PodId 1 >> 2013-04-02 03:46:44,665 DEBUG [cloud.alert.AlertManagerImpl] >> (CapacityChecker:null) Done executing storage capacity update >> 2013-04-02 03:46:44,665 DEBUG [cloud.alert.AlertManagerImpl] >> (CapacityChecker:null) Executing capacity updates for public ip and Vlans >> 2013-04-02 03:46:44,672 DEBUG [cloud.alert.AlertManagerImpl] >> (CapacityChecker:null) Done capacity updates for public ip and Vlans >> 2013-04-02 03:46:44,673 DEBUG [cloud.alert.AlertManagerImpl] >> (CapacityChecker:null) Executing capacity updates for private ip >> 2013-04-02 03:46:44,679 DEBUG [cloud.alert.AlertManagerImpl] >> (CapacityChecker:null) Done executing capacity updates for private ip >> 2013-04-02 03:46:44,680 DEBUG [cloud.alert.AlertManagerImpl] >> (CapacityChecker:null) Done recalculating system capacity >> 2013-04-02 03:46:44,696 DEBUG >> [network.router.VirtualNetworkApplianceManagerImpl] >> (RouterStatusMonitor-1:null) Found 0 routers. >> 2013-04-02 03:46:44,701 DEBUG [cloud.alert.AlertManagerImpl] >> (CapacityChecker:null) Done running Capacity Checker ... >> 2013-04-02 03:46:48,011 DEBUG [cloud.server.StatsCollector] >> (StatsCollector-2:null) VmStatsCollector is running... >> >> Here are the current VMs running on my single host: >> # xe vm-list >> uuid ( RO) : 760c34bf-6101-ec31-bd96-53a5b158a4d6 >> name-label ( RW): s-1-VM >> power-state ( RO): running >> >> >> uuid ( RO) : 1df73b13-f169-fe0a-12df-4b7fbd67a81b >> name-label ( RW): v-2-VM >> power-state ( RO): running >> >> >> uuid ( RO) : a4519728-931b-f08c-39af-c84cbb70ccab >> name-label ( RW): i-2-5-VM >> power-state ( RO): running >> >> >> uuid ( RO) : 8154702d-ce80-2332-8222-bd22774ac997 >> name-label ( RW): r-4-VM >> power-state ( RO): running >> >> >> uuid ( RO) : 087eaf6b-29bb-779e-ef32-3dee5b7c99c0 >> name-label ( RW): Control domain on host: noilabsvr01 >> power-state ( RO): running >
