cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sangeetha Hariharan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-7733) Admin/Regular User is not allowed to stop/start Vms that are running on disabled hosts.
Date Wed, 15 Oct 2014 22:35:33 GMT

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

Sangeetha Hariharan updated CLOUDSTACK-7733:
--------------------------------------------
    Priority: Critical  (was: Major)

> Admin/Regular User is not allowed to stop/start Vms that are running on disabled hosts.
> ---------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-7733
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7733
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.5.0
>         Environment: Build from master
>            Reporter: Sangeetha Hariharan
>            Priority: Critical
>
> Steps to reproduce the problem:
> Deploy a Vm in a host say host1 using a service offering that has hosttags that matches
with host1.
> Disable host.
> As admin , stop this VM. 
> Now try to start the VM.
> This fails with "job failed due to exception Unable to create a deployment for VM[User|i-20-63-VM"
> {jobprocstatus : 0, created : u'2014-10-15T08:21:04-0400', jobresult : {errorcode : 530,
errortext : u'Job failed due to exception Unable to create a deployment for VM[User|i-20-63-VM]'},
cmd : u'org.apache.cloudstack.api.command.admin.vm.StartVMCmdByAdmin', userid : u'f3d01d86-93bb-4ec7-a249-f1dc59ba33a1',
jobstatus : 2, jobid : u'fbe3432d-f90c-49d7-a5ea-f1e65e88aae7', jobresultcode : 530, jobinstanceid
: u'c9987836-8d76-4a55-bdce-6ef81c4cf51d', jobresulttype : u'object', jobinstancetype : u'VirtualMachine',
accountid : u'54b7a442-2b1f-4df9-b3cc-14a4d8537a74'}
> Management server logs indicating that Vms cannot be started on the last host Id , when
the host is disabled:
> 2014-10-15 09:37:24,480 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Executor-79:ctx-746fc
> d6f job-558/job-559 ctx-246fb1a1) Trying to allocate a host and storage pools from dc:1,
pod:1,clus
> ter:2, requested cpu: 100, requested ram: 134217728
> 2014-10-15 09:37:24,480 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Executor-79:ctx-746fcd6f
job-558/job-559 ctx-246fb1a1) Is ROOT volume READY (pool already allocated)?: Yes
> 2014-10-15 09:37:24,480 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Executor-79:ctx-746fcd6f
job-558/job-559 ctx-246fb1a1) This VM has last host_id specified, trying to choose the same
host: 4
> 2014-10-15 09:37:24,484 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Executor-79:ctx-746fcd6f
job-558/job-559 ctx-246fb1a1) The last host of this VM is not UP or is not enabled, host status
is: Up, host resource state is: Disabled
> 2014-10-15 09:37:24,484 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Executor-79:ctx-746fcd6f
job-558/job-559 ctx-246fb1a1) Cannot choose the last host to deploy this VM



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message