[jira] [Updated] (CLOUDSTACK-6497) SSVM running but not operational for XenServer deployment

["Doug Clark (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-6497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Doug Clark updated CLOUDSTACK-6497:
-----------------------------------

    Attachment: SS capacity not shown.jpg

> SSVM running but not operational for XenServer deployment
> ---------------------------------------------------------
>
>                 Key: CLOUDSTACK-6497
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6497
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: XenServer
>    Affects Versions: Future, 4.4.0
>         Environment: MS: Master (http://jenkins.buildacloud.org/job/package-rhel63-master/2647)
> XenServer 6.2
> NFS storage (for primary and secondary)
>            Reporter: Doug Clark
>            Priority: Blocker
>             Fix For: 4.4.0
>
>         Attachments: Original SSVM paused - new instance created.jpg, SS capacity not shown.jpg
>
>
> Create a basic networking 1 Zone, 1 Pod, 1 Cluster, 2 host deployment using XenServer.
> The Zone is shown as enabled.  A SSVM and Console Proxy VM have both been created on the hypervisors and are running.
> The resources view doesn't report the capacity information for SS (see screenshot).
> There are no alerts shown in the UI.
> The MS doesn't attempt to download the built-in CentOS template.
> There are no obvious related exceptions in the MS log but the following appears a number of times:
> {noformat}
> 2014-04-24 13:44:38,387 DEBUG [c.c.s.StatsCollector] (StatsCollector-3:ctx-4bea82df) There is no secondary storage VM for secondary storage host nfs://10.81.40.30/nfs/676963-u1VtYo
> {noformat}
> After some time the original SSVM enters a paused state and a new SSVM instance is created (see screenshot) - this does resolve anything.



--
This message was sent by Atlassian JIRA
(v6.2#6252)