[jira] [Created] (CLOUDSTACK-7701) Triage and fix Coverity defects
Santhosh Kumar Edukulla created CLOUDSTACK-7701: --- Summary: Triage and fix Coverity defects Key: CLOUDSTACK-7701 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7701 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Santhosh Kumar Edukulla Assignee: Santhosh Kumar Edukulla Fix For: 4.5.0 1. We have Coverity setup available, running as scheduled and individual owners are assigned with analyzed bugs. 2. As part of this bug, please triage and fix the relevant Coverity bugs assigned. It could be a count as small as 25 bugs. 3. First start with high impact in order to others later. 4. We can either triage them accordingly as fix required or false positive or not a bug accordingly. But, triage and fix accordingly wherever relevant and applicable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7702) keytool not in sudoers file
Daan Hoogland created CLOUDSTACK-7702: - Summary: keytool not in sudoers file Key: CLOUDSTACK-7702 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7702 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.1.1 Reporter: Daan Hoogland Assignee: Daan Hoogland Fix For: 4.4.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7702) keytool not in sudoers file
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14170647#comment-14170647 ] ASF subversion and git services commented on CLOUDSTACK-7702: - Commit d8359211f11b2462c35389b6c80d51df5159ae69 in cloudstack's branch refs/heads/4.4 from [~dahn] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d835921 ] CLOUDSTACK-7702 added keytool to sudoers modification specs keytool not in sudoers file --- Key: CLOUDSTACK-7702 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7702 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.1.1 Reporter: Daan Hoogland Assignee: Daan Hoogland Fix For: 4.4.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7702) keytool not in sudoers file
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14170648#comment-14170648 ] Daan Hoogland commented on CLOUDSTACK-7702: --- see http://markmail.org/message/3rxgvjgfqkyj24zj for problem description and resolution keytool not in sudoers file --- Key: CLOUDSTACK-7702 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7702 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.1.1 Reporter: Daan Hoogland Assignee: Daan Hoogland Fix For: 4.4.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-6860) DataCenter creation is failing in DevCloud in 4.4,errors out with failing to initialize agent
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14170719#comment-14170719 ] Santhosh Kumar Edukulla commented on CLOUDSTACK-6860: - DevCloud4 is the latest working version of devcloud and can be used instead. Fix is not required for current devcloud. Below is devcloud4 from ian. So, will mark this bug as resolved https://github.com/imduffy15/devcloud4 DataCenter creation is failing in DevCloud in 4.4,errors out with failing to initialize agent - Key: CLOUDSTACK-6860 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6860 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: DevCloud Affects Versions: 4.4.0 Reporter: Santhosh Kumar Edukulla Assignee: Santhosh Kumar Edukulla Attachments: vmops.log Deploying a datacenter in devcloud is failing, few of the exceptions seen in log are below, 1. com.cloud.utils.exception.CloudRuntimeException: Cannot create directory /opt/cloud/bin on XenServer hosts com.cloud.hypervisor.xen.resource.CitrixResourceBase.setupServer(CitrixResourceBase.java:4846) 2. 014-06-03 18:08:20,790 WARN [c.c.r.ResourceManagerImpl] (ApiServer-3:ctx-f7cfbcb4 ctx-a1a82b64) Unable to connect due to com.cloud.exception.ConnectionException: Reinitialize agent after setup. com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.processConnect(XcpServerDiscoverer.java:656) Steps: 1. Import Devcloud image 2. Run deploy DataCenter script to create a data center -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-6860) DataCenter creation is failing in DevCloud in 4.4,errors out with failing to initialize agent
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla resolved CLOUDSTACK-6860. - Resolution: Won't Fix DataCenter creation is failing in DevCloud in 4.4,errors out with failing to initialize agent - Key: CLOUDSTACK-6860 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6860 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: DevCloud Affects Versions: 4.4.0 Reporter: Santhosh Kumar Edukulla Assignee: Santhosh Kumar Edukulla Attachments: vmops.log Deploying a datacenter in devcloud is failing, few of the exceptions seen in log are below, 1. com.cloud.utils.exception.CloudRuntimeException: Cannot create directory /opt/cloud/bin on XenServer hosts com.cloud.hypervisor.xen.resource.CitrixResourceBase.setupServer(CitrixResourceBase.java:4846) 2. 014-06-03 18:08:20,790 WARN [c.c.r.ResourceManagerImpl] (ApiServer-3:ctx-f7cfbcb4 ctx-a1a82b64) Unable to connect due to com.cloud.exception.ConnectionException: Reinitialize agent after setup. com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.processConnect(XcpServerDiscoverer.java:656) Steps: 1. Import Devcloud image 2. Run deploy DataCenter script to create a data center -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7703) Cloudstack server endless loop when trying to create a volume while storage pool is full
JF Vincent created CLOUDSTACK-7703: -- Summary: Cloudstack server endless loop when trying to create a volume while storage pool is full Key: CLOUDSTACK-7703 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7703 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.3.0 Environment: Centos 6.5 Reporter: JF Vincent Priority: Critical When trying to create a VM, and thus a volume for it and the primary storage is full (over 90%), the managament server enter in and endless loop (extract below) and we have to restart it to exit this loop. 2014-10-14 11:39:20,701 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (Job-Executor-10:ctx-02d42f8f ctx-e581af2c) No suitable pools found for volume: Vol[5436|vm=5855|DATADISK] under cluster: 2 2014-10-14 11:39:20,702 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (Job-Executor-10:ctx-02d42f8f ctx-e581af2c) No suitable pools found 2014-10-14 11:39:20,702 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (Job-Executor-10:ctx-02d42f8f ctx-e581af2c) No suitable storagePools found under this Cluster: 2 2014-10-14 11:39:20,705 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (Job-Executor-10:ctx-02d42f8f ctx-e581af2c) Could not find suitable Deployment Destination for this VM under any clusters, returning. 2014-10-14 11:39:20,705 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:ctx-02d42f8f ctx-e581af2c) Searching all possible resources under this Zone: 2 2014-10-14 11:39:20,705 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:ctx-02d42f8f ctx-e581af2c) Listing clusters in order of aggregate capacity, that have (atleast one host with) enough CPU and RAM capacity under this Zone: 2 2014-10-14 11:39:20,707 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:ctx-02d42f8f ctx-e581af2c) Removing from the clusterId list these clusters from avoid set: [] 2014-10-14 11:39:20,714 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (Job-Executor-10:ctx-02d42f8f ctx-e581af2c) Checking resources in Cluster: 2 under Pod: 2 2014-10-14 11:39:20,714 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:ctx-02d42f8f ctx-e581af2c FirstFitRoutingAllocator) Looking for hosts in dc: 2 pod:2 cluster:2 2014-10-14 11:39:20,716 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:ctx-02d42f8f ctx-e581af2c FirstFitRoutingAllocator) FirstFitAllocator has 3 hosts to check for allocation: [Host[-79-Routing], Host[-89-Routing], Host[-77-Routing]] 2014-10-14 11:39:20,717 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:ctx-02d42f8f ctx-e581af2c FirstFitRoutingAllocator) Found 3 hosts for allocation after prioritization: [Host[-79-Routing], Host[-89-Routing], Host[-77-Routing]] 2014-10-14 11:39:20,717 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:ctx-02d42f8f ctx-e581af2c FirstFitRoutingAllocator) Looking for speed=500Mhz, Ram=500 2014-10-14 11:39:20,720 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:ctx-02d42f8f ctx-e581af2c FirstFitRoutingAllocator) Host: 79 has cpu capability (cpu:8, speed:2399) to support requested CPU: 1 and requested speed: 500 2014-10-14 11:39:20,720 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:ctx-02d42f8f ctx-e581af2c FirstFitRoutingAllocator) Checking if host: 79 has enough capacity for requested CPU: 500 and requested RAM: 524288000 , cpuOverprovisioningFactor: 4.0 2014-10-14 11:39:20,721 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:ctx-02d42f8f ctx-e581af2c FirstFitRoutingAllocator) Hosts's actual total CPU: 19192 and CPU after applying overprovisioning: 76768 2014-10-14 11:39:20,721 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:ctx-02d42f8f ctx-e581af2c FirstFitRoutingAllocator) Free CPU: 57268 , Requested CPU: 500 2014-10-14 11:39:20,721 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:ctx-02d42f8f ctx-e581af2c FirstFitRoutingAllocator) Free RAM: 93916725248 , Requested RAM: 524288000 2014-10-14 11:39:20,721 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:ctx-02d42f8f ctx-e581af2c FirstFitRoutingAllocator) Host has enough CPU and RAM available 2014-10-14 11:39:20,721 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:ctx-02d42f8f ctx-e581af2c FirstFitRoutingAllocator) STATS: Can alloc CPU from host: 79, used: 19000, reserved: 500, actual total: 19192, total with overprovisioning: 76768; requested cpu:500,alloc_from_last_host?:false ,considerReservedCapacity?: true 2014-10-14 11:39:20,721 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:ctx-02d42f8f ctx-e581af2c FirstFitRoutingAllocator) STATS: Can alloc MEM from host: 79, used: 17192452096, reserved: 524288000, total: 111633465344; requested mem:
[jira] [Created] (CLOUDSTACK-7704) Triage and fix Coverity defects
Santhosh Kumar Edukulla created CLOUDSTACK-7704: --- Summary: Triage and fix Coverity defects Key: CLOUDSTACK-7704 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7704 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Santhosh Kumar Edukulla Assignee: Santhosh Kumar Edukulla Fix For: 4.5.0 1. We have Coverity setup available, running as scheduled and individual owners are assigned with analyzed bugs. 2. As part of this bug, please triage and fix the relevant Coverity bugs assigned. It could be a count as small as 25 bugs. 3. First start with high impact in order to others later. 4. We can either triage them accordingly as fix required or false positive or not a bug accordingly. But, triage and fix accordingly wherever relevant and applicable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7705) Triage and fix Coverity defects
Santhosh Kumar Edukulla created CLOUDSTACK-7705: --- Summary: Triage and fix Coverity defects Key: CLOUDSTACK-7705 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7705 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Santhosh Kumar Edukulla Assignee: Santhosh Kumar Edukulla Fix For: 4.5.0 1. We have Coverity setup available, running as scheduled and individual owners are assigned with analyzed bugs. 2. As part of this bug, please triage and fix the relevant Coverity bugs assigned. It could be a count as small as 25 bugs. 3. First start with high impact in order to others later. 4. We can either triage them accordingly as fix required or false positive or not a bug accordingly. But, triage and fix accordingly wherever relevant and applicable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7706) Triage and fix Coverity defects
Santhosh Kumar Edukulla created CLOUDSTACK-7706: --- Summary: Triage and fix Coverity defects Key: CLOUDSTACK-7706 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7706 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Santhosh Kumar Edukulla Assignee: Santhosh Kumar Edukulla Fix For: 4.5.0 1. We have Coverity setup available, running as scheduled and individual owners are assigned with analyzed bugs. 2. As part of this bug, please triage and fix the relevant Coverity bugs assigned. It could be a count as small as 25 bugs. 3. First start with high impact in order to others later. 4. We can either triage them accordingly as fix required or false positive or not a bug accordingly. But, triage and fix accordingly wherever relevant and applicable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7706) Triage and fix Coverity defects
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla updated CLOUDSTACK-7706: Assignee: Harikrishna Patnala (was: Santhosh Kumar Edukulla) Triage and fix Coverity defects --- Key: CLOUDSTACK-7706 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7706 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Santhosh Kumar Edukulla Assignee: Harikrishna Patnala Fix For: 4.5.0 1. We have Coverity setup available, running as scheduled and individual owners are assigned with analyzed bugs. 2. As part of this bug, please triage and fix the relevant Coverity bugs assigned. It could be a count as small as 25 bugs. 3. First start with high impact in order to others later. 4. We can either triage them accordingly as fix required or false positive or not a bug accordingly. But, triage and fix accordingly wherever relevant and applicable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7707) Triage and fix Coverity defects
Santhosh Kumar Edukulla created CLOUDSTACK-7707: --- Summary: Triage and fix Coverity defects Key: CLOUDSTACK-7707 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7707 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Santhosh Kumar Edukulla Assignee: Santhosh Kumar Edukulla Fix For: 4.5.0 1. We have Coverity setup available, running as scheduled and individual owners are assigned with analyzed bugs. 2. As part of this bug, please triage and fix the relevant Coverity bugs assigned. It could be a count as small as 25 bugs. 3. First start with high impact in order to others later. 4. We can either triage them accordingly as fix required or false positive or not a bug accordingly. But, triage and fix accordingly wherever relevant and applicable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7707) Triage and fix Coverity defects
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla updated CLOUDSTACK-7707: Assignee: Jayapal Reddy (was: Santhosh Kumar Edukulla) Triage and fix Coverity defects --- Key: CLOUDSTACK-7707 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7707 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Santhosh Kumar Edukulla Assignee: Jayapal Reddy Fix For: 4.5.0 1. We have Coverity setup available, running as scheduled and individual owners are assigned with analyzed bugs. 2. As part of this bug, please triage and fix the relevant Coverity bugs assigned. It could be a count as small as 25 bugs. 3. First start with high impact in order to others later. 4. We can either triage them accordingly as fix required or false positive or not a bug accordingly. But, triage and fix accordingly wherever relevant and applicable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7708) Triage and fix Coverity defects
Santhosh Kumar Edukulla created CLOUDSTACK-7708: --- Summary: Triage and fix Coverity defects Key: CLOUDSTACK-7708 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7708 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Santhosh Kumar Edukulla Assignee: Santhosh Kumar Edukulla Fix For: 4.5.0 1. We have Coverity setup available, running as scheduled and individual owners are assigned with analyzed bugs. 2. As part of this bug, please triage and fix the relevant Coverity bugs assigned. It could be a count as small as 25 bugs. 3. First start with high impact in order to others later. 4. We can either triage them accordingly as fix required or false positive or not a bug accordingly. But, triage and fix accordingly wherever relevant and applicable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7708) Triage and fix Coverity defects
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla updated CLOUDSTACK-7708: Assignee: Kishan Kavala (was: Santhosh Kumar Edukulla) Triage and fix Coverity defects --- Key: CLOUDSTACK-7708 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7708 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Santhosh Kumar Edukulla Assignee: Kishan Kavala Fix For: 4.5.0 1. We have Coverity setup available, running as scheduled and individual owners are assigned with analyzed bugs. 2. As part of this bug, please triage and fix the relevant Coverity bugs assigned. It could be a count as small as 25 bugs. 3. First start with high impact in order to others later. 4. We can either triage them accordingly as fix required or false positive or not a bug accordingly. But, triage and fix accordingly wherever relevant and applicable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7709) Triage and fix Coverity defects
Santhosh Kumar Edukulla created CLOUDSTACK-7709: --- Summary: Triage and fix Coverity defects Key: CLOUDSTACK-7709 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7709 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Santhosh Kumar Edukulla Assignee: Santhosh Kumar Edukulla Fix For: 4.5.0 1. We have Coverity setup available, running as scheduled and individual owners are assigned with analyzed bugs. 2. As part of this bug, please triage and fix the relevant Coverity bugs assigned. It could be a count as small as 25 bugs. 3. First start with high impact in order to others later. 4. We can either triage them accordingly as fix required or false positive or not a bug accordingly. But, triage and fix accordingly wherever relevant and applicable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7709) Triage and fix Coverity defects
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla updated CLOUDSTACK-7709: Assignee: Koushik Das (was: Santhosh Kumar Edukulla) Triage and fix Coverity defects --- Key: CLOUDSTACK-7709 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7709 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Santhosh Kumar Edukulla Assignee: Koushik Das Fix For: 4.5.0 1. We have Coverity setup available, running as scheduled and individual owners are assigned with analyzed bugs. 2. As part of this bug, please triage and fix the relevant Coverity bugs assigned. It could be a count as small as 25 bugs. 3. First start with high impact in order to others later. 4. We can either triage them accordingly as fix required or false positive or not a bug accordingly. But, triage and fix accordingly wherever relevant and applicable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7710) Triage and fix Coverity defects
Santhosh Kumar Edukulla created CLOUDSTACK-7710: --- Summary: Triage and fix Coverity defects Key: CLOUDSTACK-7710 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7710 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Santhosh Kumar Edukulla Assignee: Santhosh Kumar Edukulla Fix For: 4.5.0 1. We have Coverity setup available, running as scheduled and individual owners are assigned with analyzed bugs. 2. As part of this bug, please triage and fix the relevant Coverity bugs assigned. It could be a count as small as 25 bugs. 3. First start with high impact in order to others later. 4. We can either triage them accordingly as fix required or false positive or not a bug accordingly. But, triage and fix accordingly wherever relevant and applicable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7711) Triage and fix Coverity defects
Santhosh Kumar Edukulla created CLOUDSTACK-7711: --- Summary: Triage and fix Coverity defects Key: CLOUDSTACK-7711 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7711 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Santhosh Kumar Edukulla Assignee: Santhosh Kumar Edukulla Fix For: 4.5.0 1. We have Coverity setup available, running as scheduled and individual owners are assigned with analyzed bugs. 2. As part of this bug, please triage and fix the relevant Coverity bugs assigned. It could be a count as small as 25 bugs. 3. First start with high impact in order to others later. 4. We can either triage them accordingly as fix required or false positive or not a bug accordingly. But, triage and fix accordingly wherever relevant and applicable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CLOUDSTACK-7710) Triage and fix Coverity defects
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla reassigned CLOUDSTACK-7710: --- Assignee: Bharat Kumar (was: Santhosh Kumar Edukulla) Triage and fix Coverity defects --- Key: CLOUDSTACK-7710 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7710 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Santhosh Kumar Edukulla Assignee: Bharat Kumar Fix For: 4.5.0 1. We have Coverity setup available, running as scheduled and individual owners are assigned with analyzed bugs. 2. As part of this bug, please triage and fix the relevant Coverity bugs assigned. It could be a count as small as 25 bugs. 3. First start with high impact in order to others later. 4. We can either triage them accordingly as fix required or false positive or not a bug accordingly. But, triage and fix accordingly wherever relevant and applicable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7711) Triage and fix Coverity defects
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla updated CLOUDSTACK-7711: Assignee: Saksham Srivastava (was: Santhosh Kumar Edukulla) Triage and fix Coverity defects --- Key: CLOUDSTACK-7711 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7711 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Santhosh Kumar Edukulla Assignee: Saksham Srivastava Fix For: 4.5.0 1. We have Coverity setup available, running as scheduled and individual owners are assigned with analyzed bugs. 2. As part of this bug, please triage and fix the relevant Coverity bugs assigned. It could be a count as small as 25 bugs. 3. First start with high impact in order to others later. 4. We can either triage them accordingly as fix required or false positive or not a bug accordingly. But, triage and fix accordingly wherever relevant and applicable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7712) Triage and fix Coverity defects
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla updated CLOUDSTACK-7712: Assignee: Rajesh Battala (was: Santhosh Kumar Edukulla) Triage and fix Coverity defects --- Key: CLOUDSTACK-7712 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7712 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Santhosh Kumar Edukulla Assignee: Rajesh Battala Fix For: 4.5.0 1. We have Coverity setup available, running as scheduled and individual owners are assigned with analyzed bugs. 2. As part of this bug, please triage and fix the relevant Coverity bugs assigned. It could be a count as small as 25 bugs. 3. First start with high impact in order to others later. 4. We can either triage them accordingly as fix required or false positive or not a bug accordingly. But, triage and fix accordingly wherever relevant and applicable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7713) Triage and fix Coverity defects
Santhosh Kumar Edukulla created CLOUDSTACK-7713: --- Summary: Triage and fix Coverity defects Key: CLOUDSTACK-7713 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7713 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Santhosh Kumar Edukulla Assignee: Santhosh Kumar Edukulla Fix For: 4.5.0 1. We have Coverity setup available, running as scheduled and individual owners are assigned with analyzed bugs. 2. As part of this bug, please triage and fix the relevant Coverity bugs assigned. It could be a count as small as 25 bugs. 3. First start with high impact in order to others later. 4. We can either triage them accordingly as fix required or false positive or not a bug accordingly. But, triage and fix accordingly wherever relevant and applicable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7714) Triage and fix Coverity defects
Santhosh Kumar Edukulla created CLOUDSTACK-7714: --- Summary: Triage and fix Coverity defects Key: CLOUDSTACK-7714 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7714 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Santhosh Kumar Edukulla Assignee: Santhosh Kumar Edukulla Fix For: 4.5.0 1. We have Coverity setup available, running as scheduled and individual owners are assigned with analyzed bugs. 2. As part of this bug, please triage and fix the relevant Coverity bugs assigned. It could be a count as small as 25 bugs. 3. First start with high impact in order to others later. 4. We can either triage them accordingly as fix required or false positive or not a bug accordingly. But, triage and fix accordingly wherever relevant and applicable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7713) Triage and fix Coverity defects
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla updated CLOUDSTACK-7713: Assignee: Likitha Shetty (was: Santhosh Kumar Edukulla) Triage and fix Coverity defects --- Key: CLOUDSTACK-7713 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7713 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Santhosh Kumar Edukulla Assignee: Likitha Shetty Fix For: 4.5.0 1. We have Coverity setup available, running as scheduled and individual owners are assigned with analyzed bugs. 2. As part of this bug, please triage and fix the relevant Coverity bugs assigned. It could be a count as small as 25 bugs. 3. First start with high impact in order to others later. 4. We can either triage them accordingly as fix required or false positive or not a bug accordingly. But, triage and fix accordingly wherever relevant and applicable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7714) Triage and fix Coverity defects
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla updated CLOUDSTACK-7714: Assignee: Sateesh Chodapuneedi (was: Santhosh Kumar Edukulla) Triage and fix Coverity defects --- Key: CLOUDSTACK-7714 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7714 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Santhosh Kumar Edukulla Assignee: Sateesh Chodapuneedi Fix For: 4.5.0 1. We have Coverity setup available, running as scheduled and individual owners are assigned with analyzed bugs. 2. As part of this bug, please triage and fix the relevant Coverity bugs assigned. It could be a count as small as 25 bugs. 3. First start with high impact in order to others later. 4. We can either triage them accordingly as fix required or false positive or not a bug accordingly. But, triage and fix accordingly wherever relevant and applicable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7715) Triage and fix Coverity defects
Santhosh Kumar Edukulla created CLOUDSTACK-7715: --- Summary: Triage and fix Coverity defects Key: CLOUDSTACK-7715 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7715 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Santhosh Kumar Edukulla Assignee: Santhosh Kumar Edukulla Fix For: 4.5.0 1. We have Coverity setup available, running as scheduled and individual owners are assigned with analyzed bugs. 2. As part of this bug, please triage and fix the relevant Coverity bugs assigned. It could be a count as small as 25 bugs. 3. First start with high impact in order to others later. 4. We can either triage them accordingly as fix required or false positive or not a bug accordingly. But, triage and fix accordingly wherever relevant and applicable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7716) Triage and fix Coverity defects
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla updated CLOUDSTACK-7716: Assignee: Devdeep Singh (was: Santhosh Kumar Edukulla) Triage and fix Coverity defects --- Key: CLOUDSTACK-7716 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7716 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Santhosh Kumar Edukulla Assignee: Devdeep Singh Fix For: 4.5.0 1. We have Coverity setup available, running as scheduled and individual owners are assigned with analyzed bugs. 2. As part of this bug, please triage and fix the relevant Coverity bugs assigned. It could be a count as small as 25 bugs. 3. First start with high impact in order to others later. 4. We can either triage them accordingly as fix required or false positive or not a bug accordingly. But, triage and fix accordingly wherever relevant and applicable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7716) Triage and fix Coverity defects
Santhosh Kumar Edukulla created CLOUDSTACK-7716: --- Summary: Triage and fix Coverity defects Key: CLOUDSTACK-7716 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7716 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Santhosh Kumar Edukulla Assignee: Santhosh Kumar Edukulla Fix For: 4.5.0 1. We have Coverity setup available, running as scheduled and individual owners are assigned with analyzed bugs. 2. As part of this bug, please triage and fix the relevant Coverity bugs assigned. It could be a count as small as 25 bugs. 3. First start with high impact in order to others later. 4. We can either triage them accordingly as fix required or false positive or not a bug accordingly. But, triage and fix accordingly wherever relevant and applicable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7717) Triage and fix Coverity defects
Santhosh Kumar Edukulla created CLOUDSTACK-7717: --- Summary: Triage and fix Coverity defects Key: CLOUDSTACK-7717 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7717 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Santhosh Kumar Edukulla Assignee: Santhosh Kumar Edukulla Fix For: 4.5.0 1. We have Coverity setup available, running as scheduled and individual owners are assigned with analyzed bugs. 2. As part of this bug, please triage and fix the relevant Coverity bugs assigned. It could be a count as small as 25 bugs. 3. First start with high impact in order to others later. 4. We can either triage them accordingly as fix required or false positive or not a bug accordingly. But, triage and fix accordingly wherever relevant and applicable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7717) Triage and fix Coverity defects
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla updated CLOUDSTACK-7717: Assignee: Anshul Gangwar (was: Santhosh Kumar Edukulla) Triage and fix Coverity defects --- Key: CLOUDSTACK-7717 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7717 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Santhosh Kumar Edukulla Assignee: Anshul Gangwar Fix For: 4.5.0 1. We have Coverity setup available, running as scheduled and individual owners are assigned with analyzed bugs. 2. As part of this bug, please triage and fix the relevant Coverity bugs assigned. It could be a count as small as 25 bugs. 3. First start with high impact in order to others later. 4. We can either triage them accordingly as fix required or false positive or not a bug accordingly. But, triage and fix accordingly wherever relevant and applicable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7712) Triage and fix Coverity defects
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14170779#comment-14170779 ] Rajesh Battala commented on CLOUDSTACK-7712: will work on this in the coming sprint. Triage and fix Coverity defects --- Key: CLOUDSTACK-7712 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7712 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Santhosh Kumar Edukulla Assignee: Rajesh Battala Fix For: 4.5.0 1. We have Coverity setup available, running as scheduled and individual owners are assigned with analyzed bugs. 2. As part of this bug, please triage and fix the relevant Coverity bugs assigned. It could be a count as small as 25 bugs. 3. First start with high impact in order to others later. 4. We can either triage them accordingly as fix required or false positive or not a bug accordingly. But, triage and fix accordingly wherever relevant and applicable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7715) Triage and fix Coverity defects
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla updated CLOUDSTACK-7715: Assignee: Sanjay Tripathi (was: Santhosh Kumar Edukulla) Triage and fix Coverity defects --- Key: CLOUDSTACK-7715 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7715 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Santhosh Kumar Edukulla Assignee: Sanjay Tripathi Fix For: 4.5.0 1. We have Coverity setup available, running as scheduled and individual owners are assigned with analyzed bugs. 2. As part of this bug, please triage and fix the relevant Coverity bugs assigned. It could be a count as small as 25 bugs. 3. First start with high impact in order to others later. 4. We can either triage them accordingly as fix required or false positive or not a bug accordingly. But, triage and fix accordingly wherever relevant and applicable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-7502) [UI] Host detail page - Display KVM agent version and Qemu version
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mihaela Stoica closed CLOUDSTACK-7502. -- Resolution: Invalid [UI] Host detail page - Display KVM agent version and Qemu version -- Key: CLOUDSTACK-7502 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7502 Project: CloudStack Issue Type: Task Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Mihaela Stoica Assignee: Mihaela Stoica Fix For: 4.5.0 Attachments: KVM host.png, XenServer host.png UI - Host detail page - Display KVM agent version and Qemu version. For KVM hosts, Host detail page should include KVM agent version and Qemu version. The information can be obtained via listHosts API command, details field: Qemu.Img.Version is the version of qemu image, and KVM.Agent.Version is the version of kvm agent. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CLOUDSTACK-7502) [UI] Host detail page - Display KVM agent version and Qemu version
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14170829#comment-14170829 ] Mihaela Stoica edited comment on CLOUDSTACK-7502 at 10/14/14 11:56 AM: --- These fields (KVM agent version and Qemu version) are not in the ACS database. Closing the ticket as Invalid. was (Author: mihaelas): These fields (KVM agent version and Qemu version) are not in the ACS database [UI] Host detail page - Display KVM agent version and Qemu version -- Key: CLOUDSTACK-7502 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7502 Project: CloudStack Issue Type: Task Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Mihaela Stoica Assignee: Mihaela Stoica Fix For: 4.5.0 Attachments: KVM host.png, XenServer host.png UI - Host detail page - Display KVM agent version and Qemu version. For KVM hosts, Host detail page should include KVM agent version and Qemu version. The information can be obtained via listHosts API command, details field: Qemu.Img.Version is the version of qemu image, and KVM.Agent.Version is the version of kvm agent. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7502) [UI] Host detail page - Display KVM agent version and Qemu version
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mihaela Stoica updated CLOUDSTACK-7502: --- Status: Open (was: Reviewable) These fields (KVM agent version and Qemu version) are not in the ACS database [UI] Host detail page - Display KVM agent version and Qemu version -- Key: CLOUDSTACK-7502 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7502 Project: CloudStack Issue Type: Task Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Mihaela Stoica Assignee: Mihaela Stoica Fix For: 4.5.0 Attachments: KVM host.png, XenServer host.png UI - Host detail page - Display KVM agent version and Qemu version. For KVM hosts, Host detail page should include KVM agent version and Qemu version. The information can be obtained via listHosts API command, details field: Qemu.Img.Version is the version of qemu image, and KVM.Agent.Version is the version of kvm agent. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-6650) Reorder Cluster list in deployment planner to protect GPU enabled hosts from non-GPU VM deployment
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14170848#comment-14170848 ] ASF subversion and git services commented on CLOUDSTACK-6650: - Commit e4a8bbcdf42bd3133e5cb7e3230b45c0e7018426 in cloudstack's branch refs/heads/master from [~sanjay.tripathi] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e4a8bbc ] CLOUDSTACK-6650: Reorder Cluster list in deployment planner to protect GPU enabled hosts from non-GPU VM deployment. Cluster reordering is based on the number of unique host tags in a cluster, cluster with most number of unique host tags will put at the end of list. Hosts with GPU capability will get tagged with implicit tags defined by global config param 'implicit.host.tags' at the time os host discovery. Also added FirstFitPlannerTest unit test file. Reorder Cluster list in deployment planner to protect GPU enabled hosts from non-GPU VM deployment -- Key: CLOUDSTACK-6650 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6650 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Environment: MS 4.4 XS 620SP1 Reporter: Sanjay Tripathi Assignee: Sanjay Tripathi Fix For: 4.4.0 If CS environment has GPU cards then for non-GPU enabled VM deployments, deployment planner should check the non-GPU hosts first and if they are out of capacity then deploy in GPU enabled hosts. For now, this restriction is imposed at cluster level not at zone level, so to protect GPU resources, CS should give lower priority to clusters which has GPU enabled host and high priority to clusters which contains non-GPU enabled hosts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-6650) Reorder Cluster list in deployment planner to protect GPU enabled hosts from non-GPU VM deployment
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14170850#comment-14170850 ] ASF subversion and git services commented on CLOUDSTACK-6650: - Commit 176e0d47bb86fcc4ab0cdb33f95f73d751f2d814 in cloudstack's branch refs/heads/4.5 from [~sanjay.tripathi] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=176e0d4 ] CLOUDSTACK-6650: Reorder Cluster list in deployment planner to protect GPU enabled hosts from non-GPU VM deployment. Cluster reordering is based on the number of unique host tags in a cluster, cluster with most number of unique host tags will put at the end of list. Hosts with GPU capability will get tagged with implicit tags defined by global config param 'implicit.host.tags' at the time os host discovery. Also added FirstFitPlannerTest unit test file. Reorder Cluster list in deployment planner to protect GPU enabled hosts from non-GPU VM deployment -- Key: CLOUDSTACK-6650 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6650 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Environment: MS 4.4 XS 620SP1 Reporter: Sanjay Tripathi Assignee: Sanjay Tripathi Fix For: 4.4.0 If CS environment has GPU cards then for non-GPU enabled VM deployments, deployment planner should check the non-GPU hosts first and if they are out of capacity then deploy in GPU enabled hosts. For now, this restriction is imposed at cluster level not at zone level, so to protect GPU resources, CS should give lower priority to clusters which has GPU enabled host and high priority to clusters which contains non-GPU enabled hosts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-5883) unable to copy vmware routing template to primary storage
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14170865#comment-14170865
]
prashant kumar mishra commented on CLOUDSTACK-5883:
---
facing same issue :
==
014-10-14 19:03:40,774 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
2014-10-14 19:03:40,779 DEBUG [storage.image.TemplateDataFactoryImpl]
(consoleproxy-1:null) template 8 is already in store:2, type:Image
2014-10-14 19:03:40,780 DEBUG [cloud.storage.VolumeManagerImpl]
(consoleproxy-1:null) Creating volume from template 8in the zone 1
2014-10-14 19:03:40,793 DEBUG [agent.transport.Request] (secstorage-1:null) Seq
1-1018036365: Sending { Cmd , MgmtId: 7204337877055, via: 1, Ver: v1, Flags:
100111,
[{org.apache.cloudstack.storage.command.CopyCommand:{srcTO:{org.apache.cloudstack.storage.to.TemplateObjectTO:{path:template/tmpl/1/8/,origUrl:http://download.cloud.com/templates/4.2/systemvmtemplate-4.2-vh7.ova,uuid:7f576ed0-53bf-11e4-ab93-068d643f,id:8,format:OVA,accountId:1,checksum:8fde62b1089e5844a9cd3b9b953f9596,hvm:false,displayText:SystemVM
Template
(vSphere),imageDataStore:{com.cloud.agent.api.to.NfsTO:{_url:nfs://10.147.28.7/export/home/prashant/4.2.1.6_vmware,_role:Image}},name:routing-8,hypervisorType:VMware}},destTO:{org.apache.cloudstack.storage.to.TemplateObjectTO:{origUrl:http://download.cloud.com/templates/4.2/systemvmtemplate-4.2-vh7.ova,uuid:7f576ed0-53bf-11e4-ab93-068d643f,id:8,format:OVA,accountId:1,checksum:8fde62b1089e5844a9cd3b9b953f9596,hvm:false,displayText:SystemVM
Template
(vSphere),imageDataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:4ebfb2e7-9c62-31a1-a94f-43e285f334c8,id:2,poolType:NetworkFilesystem,host:10.147.28.7,path:/export/home/prashant/pm1,port:2049}},name:routing-8,hypervisorType:VMware}},executeInSequence:true,wait:10800}}]
}
2014-10-14 19:03:40,799 DEBUG [agent.transport.Request] (secstorage-1:null) Seq
1-1018036365: Executing: { Cmd , MgmtId: 7204337877055, via: 1, Ver: v1,
Flags: 100111,
[{org.apache.cloudstack.storage.command.CopyCommand:{srcTO:{org.apache.cloudstack.storage.to.TemplateObjectTO:{path:template/tmpl/1/8/,origUrl:http://download.cloud.com/templates/4.2/systemvmtemplate-4.2-vh7.ova,uuid:7f576ed0-53bf-11e4-ab93-068d643f,id:8,format:OVA,accountId:1,checksum:8fde62b1089e5844a9cd3b9b953f9596,hvm:false,displayText:SystemVM
Template
(vSphere),imageDataStore:{com.cloud.agent.api.to.NfsTO:{_url:nfs://10.147.28.7/export/home/prashant/4.2.1.6_vmware,_role:Image}},name:routing-8,hypervisorType:VMware}},destTO:{org.apache.cloudstack.storage.to.TemplateObjectTO:{origUrl:http://download.cloud.com/templates/4.2/systemvmtemplate-4.2-vh7.ova,uuid:7f576ed0-53bf-11e4-ab93-068d643f,id:8,format:OVA,accountId:1,checksum:8fde62b1089e5844a9cd3b9b953f9596,hvm:false,displayText:SystemVM
Template
(vSphere),imageDataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:4ebfb2e7-9c62-31a1-a94f-43e285f334c8,id:2,poolType:NetworkFilesystem,host:10.147.28.7,path:/export/home/prashant/pm1,port:2049}},name:routing-8,hypervisorType:VMware}},executeInSequence:true,wait:10800}}]
}
2014-10-14 19:03:40,797 DEBUG [storage.image.TemplateDataFactoryImpl]
(consoleproxy-1:null) template 8 is already in store:2, type:Primary
2014-10-14 19:03:40,802 DEBUG [storage.volume.VolumeServiceImpl]
(consoleproxy-1:null) Found template routing-8 in storage pool 2 with
VMTemplateStoragePool id: 33
2014-10-14 19:03:40,803 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-70:null) Seq 1-1018036365: Executing request
2014-10-14 19:03:40,804 INFO [storage.resource.VmwareStorageProcessor]
(DirectAgent-70:10.147.40.7, cmd: CopyCommand) Template mount point:
template/tmpl/1/8/, name: routing-8
2014-10-14 19:03:40,809 DEBUG [storage.volume.VolumeServiceImpl]
(consoleproxy-1:null) Acquire lock on VMTemplateStoragePool 33 with timeout
3600 seconds
2014-10-14 19:03:40,895 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 0 routers to update status.
2014-10-14 19:03:40,898 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
2014-10-14 19:03:40,932 INFO [storage.resource.VmwareStorageProcessor]
(DirectAgent-70:10.147.40.7, cmd: CopyCommand) Template routing-8 is not setup
yet, setup template from secondary storage with uuid name:
a125168264ee3509a169cf05964ec66c
2014-10-14 19:03:41,007 INFO [storage.resource.VmwareStorageProcessor]
(DirectAgent-70:10.147.40.7, cmd: CopyCommand) Executing
copyTemplateFromSecondaryToPrimary. secondaryStorage:
nfs://10.147.28.7/export/home/prashant/4.2.1.6_vmware,
templatePathAtSecondaryStorage: template/tmpl/1/8/, templateName: routing-8
2014-10-14 19:03:41,007 INFO
[jira] [Commented] (CLOUDSTACK-7702) keytool not in sudoers file
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14170867#comment-14170867 ] Pierre-Luc Dion commented on CLOUDSTACK-7702: - I suspect this is also in master branch. keytool not in sudoers file --- Key: CLOUDSTACK-7702 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7702 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.1.1 Reporter: Daan Hoogland Assignee: Daan Hoogland Fix For: 4.4.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7718) No Field Validations on Zone Form
Gabor Apati-Nagy created CLOUDSTACK-7718: Summary: No Field Validations on Zone Form Key: CLOUDSTACK-7718 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7718 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.3.0 Reporter: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Priority: Minor Fix For: 4.5.0 1. Go to the form for creating a new Zone 2. Specify the Zone type and then go to the Setup Zone options. In the Setup zone tab, there are no field validations for the IP address fields: IPv4 DNS1, IPv4DNS2, etc. Refer to attached snapshot for details. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7718) No Field Validations on Zone Form
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy updated CLOUDSTACK-7718: - Description: 1. Go to the form for creating a new Zone 2. Specify the Zone type and then go to the Setup Zone options. In the Setup zone tab, there are no field validations for the IP address fields: IPv4 DNS1, IPv4DNS2, etc. was: 1. Go to the form for creating a new Zone 2. Specify the Zone type and then go to the Setup Zone options. In the Setup zone tab, there are no field validations for the IP address fields: IPv4 DNS1, IPv4DNS2, etc. Refer to attached snapshot for details. No Field Validations on Zone Form - Key: CLOUDSTACK-7718 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7718 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.3.0 Reporter: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Priority: Minor Fix For: 4.5.0 1. Go to the form for creating a new Zone 2. Specify the Zone type and then go to the Setup Zone options. In the Setup zone tab, there are no field validations for the IP address fields: IPv4 DNS1, IPv4DNS2, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7719) Notification shows wrong error message after Scalling up failed
Mihaela Stoica created CLOUDSTACK-7719: -- Summary: Notification shows wrong error message after Scalling up failed Key: CLOUDSTACK-7719 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7719 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Mihaela Stoica Priority: Minor Fix For: 4.5.0 Try to scale up vm by changing the service offering to a custom offering and provide invalid values like Expected: scaling up fails and the notification shows correct message Actual: === scaling up fails but notification shows instance scaled up -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7719) Notification shows wrong error message after Scalling up failed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mihaela Stoica updated CLOUDSTACK-7719: --- Description: Try to scale up vm by changing the service offering to a custom offering and provide invalid values like Memory = 1 Expected: scaling up fails and the notification shows correct message Actual: === scaling up fails but notification shows instance scaled up. See attached screenshot. was: Try to scale up vm by changing the service offering to a custom offering and provide invalid values like Expected: scaling up fails and the notification shows correct message Actual: === scaling up fails but notification shows instance scaled up Notification shows wrong error message after Scalling up failed --- Key: CLOUDSTACK-7719 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7719 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Mihaela Stoica Priority: Minor Fix For: 4.5.0 Try to scale up vm by changing the service offering to a custom offering and provide invalid values like Memory = 1 Expected: scaling up fails and the notification shows correct message Actual: === scaling up fails but notification shows instance scaled up. See attached screenshot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7719) Notification shows wrong error message after Scalling up failed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mihaela Stoica updated CLOUDSTACK-7719: --- Attachment: screenshot-1.png Notification shows wrong error message after Scalling up failed --- Key: CLOUDSTACK-7719 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7719 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Mihaela Stoica Priority: Minor Fix For: 4.5.0 Attachments: screenshot-1.png Try to scale up vm by changing the service offering to a custom offering and provide invalid values like Memory = 1 Expected: scaling up fails and the notification shows correct message Actual: === scaling up fails but notification shows instance scaled up. See attached screenshot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CLOUDSTACK-7719) Notification shows wrong error message after Scalling up failed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mihaela Stoica reassigned CLOUDSTACK-7719: -- Assignee: Mihaela Stoica Notification shows wrong error message after Scalling up failed --- Key: CLOUDSTACK-7719 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7719 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Mihaela Stoica Assignee: Mihaela Stoica Priority: Minor Fix For: 4.5.0 Attachments: screenshot-1.png Try to scale up vm by changing the service offering to a custom offering and provide invalid values like Memory = 1 Expected: scaling up fails and the notification shows correct message Actual: === scaling up fails but notification shows instance scaled up. See attached screenshot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7719) [UI] Notification shows wrong error message after Scalling up failed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mihaela Stoica updated CLOUDSTACK-7719: --- Summary: [UI] Notification shows wrong error message after Scalling up failed (was: Notification shows wrong error message after Scalling up failed) [UI] Notification shows wrong error message after Scalling up failed Key: CLOUDSTACK-7719 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7719 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Mihaela Stoica Assignee: Mihaela Stoica Priority: Minor Fix For: 4.5.0 Attachments: screenshot-1.png Try to scale up vm by changing the service offering to a custom offering and provide invalid values like Memory = 1 Expected: scaling up fails and the notification shows correct message Actual: === scaling up fails but notification shows instance scaled up. See attached screenshot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7105) Detail errortext in the API response
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Animesh Chaturvedi updated CLOUDSTACK-7105: --- Assignee: Anshul Gangwar Detail errortext in the API response Key: CLOUDSTACK-7105 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7105 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Reporter: Anshul Gangwar Assignee: Anshul Gangwar Priority: Minor While using cloudstack API and GUI, we feel error text should be in detail to recognize the error condition and trace the error cause. For example, in deployVirtualMachine API ◾Case1) if there is no resource available, # of POD resource full ◾Case2) if service offering is not correct, There's no host (or storage) to support service offering ◾Case3) if volume migration failed while attaching volumes to vm of other cluster, Volume attach/detach timeout error ◾And so on. We can trace management-server.log, but not all other system using cloudstack api can trace that log file. This requirement can be a little vague and broad. But it can be very helpful in operational point of view. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7666) [Automation] Management server failed to start in latest RPM build
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Animesh Chaturvedi updated CLOUDSTACK-7666: --- Assignee: Sanjay Tripathi [Automation] Management server failed to start in latest RPM build --- Key: CLOUDSTACK-7666 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7666 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.5.0 Reporter: Rayees Namathponnan Assignee: Sanjay Tripathi Priority: Blocker Fix For: 4.5.0 Management server failed to start with latest RPM build with below error Error while decrypting: GPU 2014-10-02 03:21:40,424 INFO [c.c.s.ConfigurationServerImpl] (main:null) Injected public and private keys into systemvm iso with result : null 2014-10-02 03:21:40,600 INFO [c.c.c.ClusterManagerImpl] (main:null) Start configuring cluster manager : ClusterManagerImpl 2014-10-02 03:21:40,600 INFO [c.c.c.ClusterManagerImpl] (main:null) Cluster node IP : 127.0.0.1 2014-10-02 03:21:40,641 INFO [c.c.c.ClusterManagerImpl] (main:null) Cluster manager is configured. 2014-10-02 03:21:40,704 DEBUG [c.c.u.c.DBEncryptionUtil] (main:null) Error while decrypting: GPU 2014-10-02 03:21:51,541 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.CloudStackAccountDaoImpl_EnhancerByCloudStack_66b08393 2014-10-02 03:21:51,554 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.OfferingDaoImpl_EnhancerByCloudStack_fbbaf2ed 2014-10-02 03:21:51,554 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.SMetaDaoImpl_EnhancerByCloudStack_1861e2e5 Looks like its regression in below checkin https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=39fe766c2b6fb6edd4c1bf828625b29d9bb87719 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-6807) [HyperV] [Doc] Hyper-v requires all virtual switch names should be same across the entire cluster for live migration of VM to succeed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Animesh Chaturvedi updated CLOUDSTACK-6807: --- Assignee: Radhika Nair [HyperV] [Doc] Hyper-v requires all virtual switch names should be same across the entire cluster for live migration of VM to succeed - Key: CLOUDSTACK-6807 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6807 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Anshul Gangwar Assignee: Radhika Nair Priority: Critical Labels: docs, hyper-V,, hyper-v Fix For: 4.5.0 In setup process we have to mention one more step that Hyper-v requires all virtual switch names should be same across the entire cluster for live migration of VM to succeed as mentioned @http://technet.microsoft.com/en-us/library/ff715313%28v=ws.10%29.aspx#BKMK_switchname. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-6835) db abstraction layer in upgrade path
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Animesh Chaturvedi updated CLOUDSTACK-6835: --- Fix Version/s: (was: 4.5.0) 4.6.0 db abstraction layer in upgrade path Key: CLOUDSTACK-6835 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6835 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Rajani Karuturi Priority: Critical Fix For: 4.6.0 about 198 of the issues reported by covery scan[1] on 26 May, 2014 are in the Upgrade###to###.java code and many of them related to Resource leaks and not closing the prepared statements. I think we should have a DB abstraction layer in the upgrade path so the the developer who needs to do select/insert/update data in the upgrade path need not write native sqls and worry about these recurring issues. [1] https://scan.coverity.com/projects/943 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (CLOUDSTACK-6835) db abstraction layer in upgrade path
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Animesh Chaturvedi updated CLOUDSTACK-6835: --- Comment: was deleted (was: BULK EDIT Moving some of the recent created issues with fixVersion EMPTY to 4.5. These require further triage) db abstraction layer in upgrade path Key: CLOUDSTACK-6835 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6835 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Rajani Karuturi Priority: Critical Fix For: 4.6.0 about 198 of the issues reported by covery scan[1] on 26 May, 2014 are in the Upgrade###to###.java code and many of them related to Resource leaks and not closing the prepared statements. I think we should have a DB abstraction layer in the upgrade path so the the developer who needs to do select/insert/update data in the upgrade path need not write native sqls and worry about these recurring issues. [1] https://scan.coverity.com/projects/943 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7242) adding a Secure config using the new ConfigDepot and ConfigKey breaks the build when encryption is enabled
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Animesh Chaturvedi updated CLOUDSTACK-7242:
---
Assignee: Kishan Kavala
adding a Secure config using the new ConfigDepot and ConfigKey breaks the
build when encryption is enabled
--
Key: CLOUDSTACK-7242
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7242
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Reporter: Rajani Karuturi
Assignee: Kishan Kavala
Priority: Critical
Fix For: 4.5.0
In the inner layers, when it get the value of the key it tries to do decrypt
if its a secure or hidden field. But, it doesn’t encrypt while adding the
config.
Here is code snippet from ConfigurationVO
{noformat}
@Override
public String getValue() {
return ((Hidden.equals(getCategory()) ||
Secure.equals(getCategory())) ? DBEncryptionUtil.decrypt(value) : value);
}
public void setValue(String value) {
this.value = value;
}
{noformat}
we should make the getter and setter consistent. Otherwise, you won’t be able
to introduce any new secure/hidden configs unless you put the encrypted value
in the db before.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7242) adding a Secure config using the new ConfigDepot and ConfigKey breaks the build when encryption is enabled
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14171206#comment-14171206
]
Animesh Chaturvedi commented on CLOUDSTACK-7242:
Kishan can you help with this issue?
adding a Secure config using the new ConfigDepot and ConfigKey breaks the
build when encryption is enabled
--
Key: CLOUDSTACK-7242
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7242
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Reporter: Rajani Karuturi
Assignee: Kishan Kavala
Priority: Critical
Fix For: 4.5.0
In the inner layers, when it get the value of the key it tries to do decrypt
if its a secure or hidden field. But, it doesn’t encrypt while adding the
config.
Here is code snippet from ConfigurationVO
{noformat}
@Override
public String getValue() {
return ((Hidden.equals(getCategory()) ||
Secure.equals(getCategory())) ? DBEncryptionUtil.decrypt(value) : value);
}
public void setValue(String value) {
this.value = value;
}
{noformat}
we should make the getter and setter consistent. Otherwise, you won’t be able
to introduce any new secure/hidden configs unless you put the encrypted value
in the db before.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7532) [Templates] Template status is not shown in UI/API response for non-default account users
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Animesh Chaturvedi updated CLOUDSTACK-7532: --- Assignee: Nitin Mehta [Templates] Template status is not shown in UI/API response for non-default account users - Key: CLOUDSTACK-7532 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7532 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, Template Affects Versions: 4.5.0 Environment: Latest build from master with commit: c33fea2cd27664db32c1173e98511470bf0a0724 Reporter: Sanjeev N Assignee: Nitin Mehta Priority: Critical Labels: api, templates Fix For: 4.5.0 Attachments: template_status.PNG [Templates] Template status is not shown in UI/API response for non-default account users Steps to Reproduce: === 1.Bring up CS with latest build 2.Create one account under root domain 3.Register template using the account created above 4.After the template download is completed verify the template status using the account created at step2 Expected Result: == In UI/API response status field should be there and it should be set to Download Complete after the successful template download. Actual Behavior: Status is shown only for the default admin user. But it is not showed to other account users. Impact: == Marvin tests which use template register would fail because of the status filed missing. Following is the code from base.py where the tests are failing: elif 'Downloaded' in template.status: time.sleep(interval) becasue template.status is NoneType API: http://10.147.40.10:8080/client/api?command=listTemplatessessionkey=SgRK4kwpxxjg3Jx%2FwePLoS0aK3c%3Dtemplatefilter=selfid=550ad6ac-38d2-11e4-a56e-d4ae527ccfaa_=1410351906876 API Response: === listtemplatesresponse cloud-stack-version=4.5.0-SNAPSHOTcount1/counttemplateid550ad6ac-38d2-11e4-a56e-d4ae527ccfaa/idnameCentOS 5.6(64-bit) no GUI (XenServer)/namedisplaytextCentOS 5.6(64-bit) no GUI (XenServer)/displaytextispublictrue/ispubliccreated2014-09-10T15:59:38+0530/createdisreadytrue/isreadypasswordenabledfalse/passwordenabledformatVHD/formatisfeaturedtrue/isfeaturedcrossZonestrue/crossZonesostypeid572126ea-38d2-11e4-a56e-d4ae527ccfaa/ostypeidostypenameCentOS 5.6 (64-bit)/ostypenameaccountsystem/accountzoneid680f7c3a-a9ee-4ed3-b594-981d56f8da4b/zoneidzonenamez2/zonenamesize21474836480/sizetemplatetypeBUILTIN/templatetypehypervisorXenServer/hypervisordomainROOT/domaindomainid54e9d4e4-38d2-11e4-a56e-d4ae527ccfaa/domainidisextractabletrue/isextractablechecksum905cec879afd9c9d22ecc8036131a180/checksumsshkeyenabledfalse/sshkeyenabledisdynamicallyscalabletrue/isdynamicallyscalable/template/listtemplatesresponse In the above API response status field is missing. This bug is easily reproducible. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7430) [UI] no option to remove /delete host from cluster from UI
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Animesh Chaturvedi updated CLOUDSTACK-7430: --- Assignee: Jessica Wang [UI] no option to remove /delete host from cluster from UI -- Key: CLOUDSTACK-7430 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7430 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: shweta agarwal Assignee: Jessica Wang Fix For: 4.5.0 Attachments: delete-host.png Repro steps: 1. Create a Zone 2. Put host to maintenance 3. when host is in maintenance try to remove/delete host from cluster via Ui Bug: No option to delete host attaching snapshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7720) No IP Address Validation for Acquire new secondary IP
Gabor Apati-Nagy created CLOUDSTACK-7720: Summary: No IP Address Validation for Acquire new secondary IP Key: CLOUDSTACK-7720 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7720 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.3.0 Reporter: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Priority: Minor Fix For: 4.5.0 Steps: 1. Go to Instances -- NICs tab. 2. Click on the View Secondary IPs 3. Click on Acquire new secondary IP There is No IP address validation for Acquire new secondary IP. Additionally, this field should be a required field. Clicking Ok generates an IP, but it can be confusing to the end user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7718) No Field Validations on Zone Form
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Apati-Nagy updated CLOUDSTACK-7718: - Status: Reviewable (was: In Progress) No Field Validations on Zone Form - Key: CLOUDSTACK-7718 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7718 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.3.0 Reporter: Gabor Apati-Nagy Assignee: Gabor Apati-Nagy Priority: Minor Fix For: 4.5.0 1. Go to the form for creating a new Zone 2. Specify the Zone type and then go to the Setup Zone options. In the Setup zone tab, there are no field validations for the IP address fields: IPv4 DNS1, IPv4DNS2, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7605) [Basic zone] Restart network with clean up set to true in a zone with multiple pods leave routers in stopped state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14171297#comment-14171297 ] ASF subversion and git services commented on CLOUDSTACK-7605: - Commit db86bdfb2cae2673a10dac31995ee5e5af64a994 in cloudstack's branch refs/heads/master from [~wilder.rodrigues] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=db86bdf ] Applygin fix from commit ID aaeadc5c44e3fe16a1deea5348b085b08b5f4f4d Sheng Yang changed 2 classes, ut only one was related to the bug CLOUDSTACK-7605. I applied the changed on the routerslist, used during the deployment of the virtual routers. Tested Advanced Zone against the simulator. 69 happy tests in place [Basic zone] Restart network with clean up set to true in a zone with multiple pods leave routers in stopped state -- Key: CLOUDSTACK-7605 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7605 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Sheng Yang Assignee: Sheng Yang Priority: Critical Fix For: 4.5.0 In a basic zone with more than one pod, if network is restarted with clean up set to true, routers in all Pods get recreated but remain in Stopped state. Only one router gets started up. Exception like this: 2014-09-22 15:42:21,583 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Work-Job-Executor-14:ctx-51d3b3f9 job-25/job-32 ctx-79fd1959) Wake up jobs joined with job- 32 and disjoin all subjobs created from job- 32 2014-09-22 15:42:21,587 DEBUG [c.c.v.VmWorkJobDispatcher] (Work-Job-Executor-14:ctx-51d3b3f9 job-25/job-32) Done with run of VM work job: com.cloud.vm.VmWorkStart for VM 13, job origin: 25 2014-09-22 15:42:21,587 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Work-Job-Executor-14:ctx-51d3b3f9 job-25/job-32) Done executing com.cloud.vm.VmWorkStart for job-32 2014-09-22 15:42:21,594 DEBUG [o.a.c.e.o.NetworkOrchestrator] (API-Job-Executor-13:ctx-693acbb4 job-25 ctx-5a20d246) Asking SecurityGroupProvider to implemenet Ntwk[204|Guest|6] 2014-09-22 15:42:21,595 WARN [o.a.c.e.o.NetworkOrchestrator] (API-Job-Executor-13:ctx-693acbb4 job-25 ctx-5a20d246) Failed to implement network Ntwk[204|Guest|6] elements and resources as a part of network restart due to java.lang.NullPointerException at com.cloud.network.element.VirtualRouterElement.getRouters(VirtualRouterElement.java:971) at com.cloud.network.element.VirtualRouterElement.prepareAggregatedExecution(VirtualRouterElement.java:1118) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.implementNetworkElementsAndResources(NetworkOrchestrator.java:1120) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.restartNetwork(NetworkOrchestrator.java:2484) at com.cloud.network.NetworkServiceImpl.restartNetwork(NetworkServiceImpl.java:1873) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at com.sun.proxy.$Proxy173.restartNetwork(Unknown Source) at org.apache.cloudstack.api.command.user.network.RestartNetworkCmd.execute(RestartNetworkCmd.java:95) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141) at
[jira] [Commented] (CLOUDSTACK-7563) ClassCastException in VirtualMachineManagerImpl in handling various Agent command answer.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14171306#comment-14171306 ] ASF subversion and git services commented on CLOUDSTACK-7563: - Commit 4b8bfe26275f7eb6e98abe77849153eaa93e8205 in cloudstack's branch refs/heads/master from [~minchen07] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4b8bfe2 ] CLOUDSTACK-7563: Fix potential NPE from FingBugs. ClassCastException in VirtualMachineManagerImpl in handling various Agent command answer. - Key: CLOUDSTACK-7563 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7563 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.3.0 Reporter: Min Chen Assignee: Min Chen Priority: Critical Fix For: 4.5.0 irtualMachineManagerImpl has many methods directly cast the Answer received from AgentManager.send or AgentManager.easySend to the expected Answer class in the normal case. This will throw unhandled ClassCastException in some unexcepted cases where host is down and agent is disconnected, which will lead to cloud instability. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7563) ClassCastException in VirtualMachineManagerImpl in handling various Agent command answer.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14171315#comment-14171315 ] ASF subversion and git services commented on CLOUDSTACK-7563: - Commit e7fa3a29594eb748b201865dac3a85f8da024075 in cloudstack's branch refs/heads/4.5 from [~minchen07] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e7fa3a2 ] CLOUDSTACK-7563: Fix potential NPE from FingBugs. ClassCastException in VirtualMachineManagerImpl in handling various Agent command answer. - Key: CLOUDSTACK-7563 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7563 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.3.0 Reporter: Min Chen Assignee: Min Chen Priority: Critical Fix For: 4.5.0 irtualMachineManagerImpl has many methods directly cast the Answer received from AgentManager.send or AgentManager.easySend to the expected Answer class in the normal case. This will throw unhandled ClassCastException in some unexcepted cases where host is down and agent is disconnected, which will lead to cloud instability. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7721) [Automation] [Hyper-V] System VMs fail to deploy due to NPE: InvocationTargetException when invoking RPC callback for command: copyBaseImageCallback
Chandan Purushothama created CLOUDSTACK-7721: Summary: [Automation] [Hyper-V] System VMs fail to deploy due to NPE: InvocationTargetException when invoking RPC callback for command: copyBaseImageCallback Key: CLOUDSTACK-7721 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7721 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.5.0 Reporter: Chandan Purushothama Priority: Blocker Fix For: 4.5.0 = NullPointerException: = 2014-10-14 15:40:28,113 DEBUG [o.a.c.s.i.s.TemplateObject] (Work-Job-Executor-2:ctx-8958a812 job-17/job-19 ctx-d2c645ce) failed to process event and answer java.lang.NullPointerException at org.apache.cloudstack.storage.image.store.TemplateObject.processEvent(TemplateObject.java:194) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.copyBaseImageCallback(VolumeServiceImpl.java:568) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.apache.cloudstack.framework.async.AsyncCallbackDispatcher.dispatch(AsyncCallbackDispatcher.java:148) at org.apache.cloudstack.framework.async.InplaceAsyncCallbackDriver.performCompletionCallback(InplaceAsyncCallbackDriver.java:25) at org.apache.cloudstack.framework.async.AsyncCallbackDispatcher.complete(AsyncCallbackDispatcher.java:126) at org.apache.cloudstack.storage.motion.AncientDataMotionStrategy.copyAsync(AncientDataMotionStrategy.java:449) at org.apache.cloudstack.storage.motion.DataMotionServiceImpl.copyAsync(DataMotionServiceImpl.java:68) at org.apache.cloudstack.storage.motion.DataMotionServiceImpl.copyAsync(DataMotionServiceImpl.java:73) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.createBaseImageAsync(VolumeServiceImpl.java:502) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.createVolumeFromTemplateAsync(VolumeServiceImpl.java:748) at org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.recreateVolume(VolumeOrchestrator.java:1227) at org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.prepare(VolumeOrchestrator.java:1297) at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:972) at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:4593) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107) at com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:4749) at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:513) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:470) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) 2014-10-14 15:40:28,117 DEBUG [o.a.c.s.v.VolumeServiceImpl] (Work-Job-Executor-2:ctx-8958a812 job-17/job-19 ctx-d2c645ce) failed to create template on storage java.lang.RuntimeException: InvocationTargetException when invoking RPC callback for
[jira] [Created] (CLOUDSTACK-7722) add.label: Add button for tags show the label not Add text
Pierre-Luc Dion created CLOUDSTACK-7722: --- Summary: add.label: Add button for tags show the label not Add text Key: CLOUDSTACK-7722 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7722 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0, 4.4.1 Reporter: Pierre-Luc Dion Priority: Trivial on every language, all sections the Add button display add.label instead of Add on the button of the UI. example: at the bottom of the page for a selected template in tags section. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7723) UI Storage detail view add Disk Offering field
Jessica Wang created CLOUDSTACK-7723: Summary: UI Storage detail view add Disk Offering field Key: CLOUDSTACK-7723 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7723 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Reporter: Jessica Wang Assignee: Jessica Wang -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7723) UI Storage detail view add Disk Offering field.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang updated CLOUDSTACK-7723: - Summary: UI Storage detail view add Disk Offering field. (was: UI Storage detail view add Disk Offering field) UI Storage detail view add Disk Offering field. - Key: CLOUDSTACK-7723 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7723 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Jessica Wang Assignee: Jessica Wang -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7723) UI Storage detail view add Disk Offering field.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14171516#comment-14171516 ] ASF subversion and git services commented on CLOUDSTACK-7723: - Commit 340bcc60c0142e5c7f026dec78ca393278d4b60f in cloudstack's branch refs/heads/master from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=340bcc6 ] CLOUDSTACK-7723: UI Storage detail view add Disk Offering field. UI Storage detail view add Disk Offering field. - Key: CLOUDSTACK-7723 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7723 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Jessica Wang Assignee: Jessica Wang -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7723) UI Storage detail view add Disk Offering field.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14171546#comment-14171546 ] ASF subversion and git services commented on CLOUDSTACK-7723: - Commit 26f3e8499a6889e00b6e2ea63a0a9425c1b2647e in cloudstack's branch refs/heads/4.5 from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=26f3e849 ] CLOUDSTACK-7723: UI Storage detail view add Disk Offering field. UI Storage detail view add Disk Offering field. - Key: CLOUDSTACK-7723 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7723 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Jessica Wang Assignee: Jessica Wang -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-7723) UI Storage detail view add Disk Offering field.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang closed CLOUDSTACK-7723. UI Storage detail view add Disk Offering field. - Key: CLOUDSTACK-7723 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7723 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Jessica Wang Assignee: Jessica Wang -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7723) UI Storage detail view add Disk Offering field.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang updated CLOUDSTACK-7723: - Attachment: jessica-2014-10-14.PNG UI Storage detail view add Disk Offering field. - Key: CLOUDSTACK-7723 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7723 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Jessica Wang Assignee: Jessica Wang Attachments: jessica-2014-10-14.PNG -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7722) add.label: Add button for tags show the label not Add text
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion resolved CLOUDSTACK-7722. - Resolution: Fixed Fix Version/s: 4.5.0 already fixed in master and 4.5 branch. add.label: Add button for tags show the label not Add text Key: CLOUDSTACK-7722 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7722 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0, 4.4.1 Reporter: Pierre-Luc Dion Priority: Trivial Fix For: 4.5.0 on every language, all sections the Add button display add.label instead of Add on the button of the UI. example: at the bottom of the page for a selected template in tags section. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7724) [Automation][HyperV] Unable to migrate VM due to JsonParseException: The JsonDeserializer EnumTypeAdapter failed to deserialize json object Running
Chandan Purushothama created CLOUDSTACK-7724:
Summary: [Automation][HyperV] Unable to migrate VM due to
JsonParseException: The JsonDeserializer EnumTypeAdapter failed to deserialize
json object Running
Key: CLOUDSTACK-7724
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7724
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Automation
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Priority: Critical
Fix For: 4.5.0
=
JsonParseException: The JsonDeserializer EnumTypeAdapter failed to deserialize
json object Running
=
2014-10-14 19:34:47,983 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-65:ctx-81e9b15c job-191/job-192 ctx-b908f714) Seq
1-5051068457072722114: Sending { Cmd , MgmtId: 192182403311206, via:
1(10.81.56.124), Ver: v1, Flags: 100011,
[{com.cloud.agent.api.CheckVirtualMachineCommand:{vmName:i-16-36-VM,wait:20}}]
}
2014-10-14 19:34:47,983 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-65:ctx-81e9b15c job-191/job-192 ctx-b908f714) Seq
1-5051068457072722114: Executing: { Cmd , MgmtId: 192182403311206, via:
1(10.81.56.124), Ver: v1, Flags: 100011,
[{com.cloud.agent.api.CheckVirtualMachineCommand:{vmName:i-16-36-VM,wait:20}}]
}
2014-10-14 19:34:47,983 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-110:ctx-409b4476) Seq 1-5051068457072722114: Executing request
2014-10-14 19:34:47,984 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-110:ctx-409b4476) POST request to
https://10.81.56.124:8250/api/HypervResource/com.cloud.agent.api.CheckVirtualMachineCommand
with contents
{vmName:i-16-36-VM,contextMap:{job:job-191/job-192},wait:20}
2014-10-14 19:34:47,990 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-110:ctx-409b4476) Sending cmd to
https://10.81.56.124:8250/api/HypervResource/com.cloud.agent.api.CheckVirtualMachineCommand
cmd
data:{vmName:i-16-36-VM,contextMap:{job:job-191/job-192},wait:20}
2014-10-14 19:34:48,099 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-110:ctx-409b4476) POST response is
[{com.cloud.agent.api.CheckVirtualMachineAnswer:{result:true,details:null,state:Running,contextMap:{}}}]
2014-10-14 19:34:48,148 WARN [c.c.a.m.DirectAgentAttache]
(DirectAgent-110:ctx-409b4476) Seq 1-5051068457072722114: Throwable caught
while executing command
com.google.gson.JsonParseException: The JsonDeserializer EnumTypeAdapter failed
to deserialize json object Running given the type class
com.cloud.vm.VirtualMachine$PowerState
at
com.google.gson.JsonDeserializerExceptionWrapper.deserialize(JsonDeserializerExceptionWrapper.java:64)
at
com.google.gson.JsonDeserializationVisitor.invokeCustomDeserializer(JsonDeserializationVisitor.java:92)
at
com.google.gson.JsonObjectDeserializationVisitor.visitFieldUsingCustomHandler(JsonObjectDeserializationVisitor.java:117)
at
com.google.gson.ReflectingFieldNavigator.visitFieldsReflectively(ReflectingFieldNavigator.java:63)
at com.google.gson.ObjectNavigator.accept(ObjectNavigator.java:120)
at
com.google.gson.JsonDeserializationContextDefault.fromJsonObject(JsonDeserializationContextDefault.java:76)
at
com.google.gson.JsonDeserializationContextDefault.deserialize(JsonDeserializationContextDefault.java:54)
at com.google.gson.Gson.fromJson(Gson.java:551)
at com.google.gson.Gson.fromJson(Gson.java:521)
at
com.cloud.agent.transport.ArrayTypeAdaptor.deserialize(ArrayTypeAdaptor.java:80)
at
com.cloud.agent.transport.ArrayTypeAdaptor.deserialize(ArrayTypeAdaptor.java:40)
at
com.google.gson.JsonDeserializerExceptionWrapper.deserialize(JsonDeserializerExceptionWrapper.java:51)
at
com.google.gson.JsonDeserializationVisitor.invokeCustomDeserializer(JsonDeserializationVisitor.java:92)
at
com.google.gson.JsonDeserializationVisitor.visitUsingCustomHandler(JsonDeserializationVisitor.java:80)
at com.google.gson.ObjectNavigator.accept(ObjectNavigator.java:101)
at
com.google.gson.JsonDeserializationContextDefault.fromJsonArray(JsonDeserializationContextDefault.java:67)
at
com.google.gson.JsonDeserializationContextDefault.deserialize(JsonDeserializationContextDefault.java:52)
at com.google.gson.Gson.fromJson(Gson.java:551)
at com.google.gson.Gson.fromJson(Gson.java:498)
at com.google.gson.Gson.fromJson(Gson.java:467)
at com.google.gson.Gson.fromJson(Gson.java:417)
at com.google.gson.Gson.fromJson(Gson.java:389)
at
com.cloud.hypervisor.hyperv.resource.HypervDirectConnectResource.executeRequest(HypervDirectConnectResource.java:518)
at
[jira] [Created] (CLOUDSTACK-7725) [Automation][HyperV] After sometime System VM 'agents' get disconnected due to Ping Issues and get shut down
Chandan Purushothama created CLOUDSTACK-7725: Summary: [Automation][HyperV] After sometime System VM 'agents' get disconnected due to Ping Issues and get shut down Key: CLOUDSTACK-7725 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7725 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.5.0 Reporter: Chandan Purushothama Priority: Blocker Fix For: 4.5.0 There is something still wrong with the Agents in System VMs on HyperV Setup. The System VM agents got disconnected due to Ping Issues and VMs got shut down. I found this observation when I noticed that all the SSVM Test cases failed. Someone has to look at what is happening between management server and agents communication. I don’t think it is anything wrong with the Setup based on the success of other test suites. Disconnection Information Log is as shown below: 2014-10-14 19:21:50,378 INFO [c.c.a.m.AgentManagerImpl] (AgentMonitor-1:ctx-72fa526b) Found the following agents behind on ping: [3, 4] 2014-10-14 19:21:50,380 WARN [c.c.a.m.AgentManagerImpl] (AgentMonitor-1:ctx-72fa526b) Disconnect agent for CPVM/SSVM due to physical connection close. host: 3 2014-10-14 19:21:50,381 INFO [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) Host 3 is disconnecting with event PingTimeout 2014-10-14 19:21:50,382 WARN [c.c.a.m.AgentManagerImpl] (AgentMonitor-1:ctx-72fa526b) Disconnect agent for CPVM/SSVM due to physical connection close. host: 4 2014-10-14 19:21:50,383 INFO [c.c.a.m.AgentManagerImpl] (AgentTaskPool-6:ctx-f560f275) Host 4 is disconnecting with event PingTimeout 2014-10-14 19:21:50,384 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) The next status of agent 3 is Alert, current status is Up 2014-10-14 19:21:50,384 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) Deregistering link for 3 with state Alert 2014-10-14 19:21:50,384 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) Remove Agent : 3 2014-10-14 19:21:50,384 DEBUG [c.c.a.m.ConnectedAgentAttache] (AgentTaskPool-5:ctx-693d2497) Processing Disconnect. 2014-10-14 19:21:50,384 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) Sending Disconnect to listener: com.cloud.hypervisor.xenserver.discoverer.XcpServerDiscoverer 2014-10-14 19:21:50,384 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) Sending Disconnect to listener: com.cloud.hypervisor.hyperv.discoverer.HypervServerDiscoverer 2014-10-14 19:21:50,384 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) Sending Disconnect to listener: com.cloud.storage.secondary.SecondaryStorageListener 2014-10-14 19:21:50,385 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-6:ctx-f560f275) The next status of agent 4 is Alert, current status is Up 2014-10-14 19:21:50,385 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-6:ctx-f560f275) Deregistering link for 4 with state Alert 2014-10-14 19:21:50,385 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-6:ctx-f560f275) Remove Agent : 4 2014-10-14 19:21:50,385 DEBUG [c.c.a.m.ConnectedAgentAttache] (AgentTaskPool-6:ctx-f560f275) Processing Disconnect. 2014-10-14 19:21:50,385 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) Sending Disconnect to listener: com.cloud.vm.ClusteredVirtualMachineManagerImpl 2014-10-14 19:21:50,385 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) Sending Disconnect to listener: org.apache.cloudstack.engine.orchestration.NetworkOrchestrator 2014-10-14 19:21:50,385 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) Sending Disconnect to listener: com.cloud.storage.listener.StoragePoolMonitor 2014-10-14 19:21:50,385 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) Sending Disconnect to listener: com.cloud.hypervisor.vmware.manager.VmwareManagerImpl 2014-10-14 19:21:50,385 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) Sending Disconnect to listener: com.cloud.deploy.DeploymentPlanningManagerImpl 2014-10-14 19:21:50,385 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-6:ctx-f560f275) Sending Disconnect to listener: com.cloud.hypervisor.xenserver.discoverer.XcpServerDiscoverer 2014-10-14 19:21:50,385 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-6:ctx-f560f275) Sending Disconnect to listener: com.cloud.hypervisor.hyperv.discoverer.HypervServerDiscoverer 2014-10-14 19:21:50,385 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-6:ctx-f560f275) Sending Disconnect to listener: com.cloud.storage.secondary.SecondaryStorageListener 2014-10-14 19:21:50,385 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) Sending Disconnect to listener: com.cloud.network.security.SecurityGroupListener 2014-10-14
[jira] [Updated] (CLOUDSTACK-7721) [Automation] [Hyper-V] System VMs fail to deploy due to NPE: InvocationTargetException when invoking RPC callback for command: copyBaseImageCallback
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Purushothama updated CLOUDSTACK-7721: - Priority: Critical (was: Blocker) [Automation] [Hyper-V] System VMs fail to deploy due to NPE: InvocationTargetException when invoking RPC callback for command: copyBaseImageCallback Key: CLOUDSTACK-7721 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7721 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.5.0 Reporter: Chandan Purushothama Priority: Critical Fix For: 4.5.0 = NullPointerException: = 2014-10-14 15:40:28,113 DEBUG [o.a.c.s.i.s.TemplateObject] (Work-Job-Executor-2:ctx-8958a812 job-17/job-19 ctx-d2c645ce) failed to process event and answer java.lang.NullPointerException at org.apache.cloudstack.storage.image.store.TemplateObject.processEvent(TemplateObject.java:194) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.copyBaseImageCallback(VolumeServiceImpl.java:568) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.apache.cloudstack.framework.async.AsyncCallbackDispatcher.dispatch(AsyncCallbackDispatcher.java:148) at org.apache.cloudstack.framework.async.InplaceAsyncCallbackDriver.performCompletionCallback(InplaceAsyncCallbackDriver.java:25) at org.apache.cloudstack.framework.async.AsyncCallbackDispatcher.complete(AsyncCallbackDispatcher.java:126) at org.apache.cloudstack.storage.motion.AncientDataMotionStrategy.copyAsync(AncientDataMotionStrategy.java:449) at org.apache.cloudstack.storage.motion.DataMotionServiceImpl.copyAsync(DataMotionServiceImpl.java:68) at org.apache.cloudstack.storage.motion.DataMotionServiceImpl.copyAsync(DataMotionServiceImpl.java:73) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.createBaseImageAsync(VolumeServiceImpl.java:502) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.createVolumeFromTemplateAsync(VolumeServiceImpl.java:748) at org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.recreateVolume(VolumeOrchestrator.java:1227) at org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.prepare(VolumeOrchestrator.java:1297) at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:972) at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:4593) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107) at com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:4749) at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:513) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:470) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at
[jira] [Closed] (CLOUDSTACK-7598) Cloudstack VM State is not in sync with state from Hypervisor
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada closed CLOUDSTACK-7598. This is fixed now. Hence closing the bug. Cloudstack VM State is not in sync with state from Hypervisor - Key: CLOUDSTACK-7598 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7598 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: XenServer Affects Versions: 4.5.0 Reporter: Sailaja Mada Assignee: Devdeep Singh Priority: Blocker Fix For: 4.5.0 Attachments: vmsynclogs.rar Steps: 1. Install and configure Adv zone using XS 6.5 Hypervisor 2. Deploy Linux VM , Windows VM 3. After VM is up and running login to the VM and shutdown the instance 4. It moved to Shutdown state in the hypervisor 5. But this state is not synced to cloudstack and it remained in running state in cloudstack Observation: Cloudstack VM State is not in sync with state from Hypervisor Ob -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7725) [Automation][HyperV] After sometime System VM 'agents' get disconnected due to Ping Issues and get shut down
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Purushothama updated CLOUDSTACK-7725: - Attachment: management-server.zip [Automation][HyperV] After sometime System VM 'agents' get disconnected due to Ping Issues and get shut down Key: CLOUDSTACK-7725 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7725 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.5.0 Reporter: Chandan Purushothama Priority: Blocker Fix For: 4.5.0 Attachments: management-server.zip There is something still wrong with the Agents in System VMs on HyperV Setup. The System VM agents got disconnected due to Ping Issues and VMs got shut down. I found this observation when I noticed that all the SSVM Test cases failed. Someone has to look at what is happening between management server and agents communication. I don’t think it is anything wrong with the Setup based on the success of other test suites. === Disconnection Information Log is as shown below: === 2014-10-14 19:21:50,378 INFO [c.c.a.m.AgentManagerImpl] (AgentMonitor-1:ctx-72fa526b) Found the following agents behind on ping: [3, 4] 2014-10-14 19:21:50,380 WARN [c.c.a.m.AgentManagerImpl] (AgentMonitor-1:ctx-72fa526b) Disconnect agent for CPVM/SSVM due to physical connection close. host: 3 2014-10-14 19:21:50,381 INFO [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) Host 3 is disconnecting with event PingTimeout 2014-10-14 19:21:50,382 WARN [c.c.a.m.AgentManagerImpl] (AgentMonitor-1:ctx-72fa526b) Disconnect agent for CPVM/SSVM due to physical connection close. host: 4 2014-10-14 19:21:50,383 INFO [c.c.a.m.AgentManagerImpl] (AgentTaskPool-6:ctx-f560f275) Host 4 is disconnecting with event PingTimeout 2014-10-14 19:21:50,384 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) The next status of agent 3 is Alert, current status is Up 2014-10-14 19:21:50,384 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) Deregistering link for 3 with state Alert 2014-10-14 19:21:50,384 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) Remove Agent : 3 2014-10-14 19:21:50,384 DEBUG [c.c.a.m.ConnectedAgentAttache] (AgentTaskPool-5:ctx-693d2497) Processing Disconnect. 2014-10-14 19:21:50,384 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) Sending Disconnect to listener: com.cloud.hypervisor.xenserver.discoverer.XcpServerDiscoverer 2014-10-14 19:21:50,384 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) Sending Disconnect to listener: com.cloud.hypervisor.hyperv.discoverer.HypervServerDiscoverer 2014-10-14 19:21:50,384 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) Sending Disconnect to listener: com.cloud.storage.secondary.SecondaryStorageListener 2014-10-14 19:21:50,385 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-6:ctx-f560f275) The next status of agent 4 is Alert, current status is Up 2014-10-14 19:21:50,385 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-6:ctx-f560f275) Deregistering link for 4 with state Alert 2014-10-14 19:21:50,385 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-6:ctx-f560f275) Remove Agent : 4 2014-10-14 19:21:50,385 DEBUG [c.c.a.m.ConnectedAgentAttache] (AgentTaskPool-6:ctx-f560f275) Processing Disconnect. 2014-10-14 19:21:50,385 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) Sending Disconnect to listener: com.cloud.vm.ClusteredVirtualMachineManagerImpl 2014-10-14 19:21:50,385 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) Sending Disconnect to listener: org.apache.cloudstack.engine.orchestration.NetworkOrchestrator 2014-10-14 19:21:50,385 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) Sending Disconnect to listener: com.cloud.storage.listener.StoragePoolMonitor 2014-10-14 19:21:50,385 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) Sending Disconnect to listener: com.cloud.hypervisor.vmware.manager.VmwareManagerImpl 2014-10-14 19:21:50,385 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-5:ctx-693d2497) Sending Disconnect to listener: com.cloud.deploy.DeploymentPlanningManagerImpl 2014-10-14 19:21:50,385 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-6:ctx-f560f275) Sending Disconnect to listener: com.cloud.hypervisor.xenserver.discoverer.XcpServerDiscoverer 2014-10-14 19:21:50,385 DEBUG [c.c.a.m.AgentManagerImpl]
[jira] [Commented] (CLOUDSTACK-7693) Fix pep8 issues in various test suites
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14172013#comment-14172013 ] ASF subversion and git services commented on CLOUDSTACK-7693: - Commit 35e05a69a51496c343cf3bf8545c9d3650d4c6e8 in cloudstack's branch refs/heads/master from [~gauravaradhye] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=35e05a6 ] CLOUDSTACK-7693: Fixing pep8 issues pep8 fixes for test_routers.py Signed-off-by: SrikanteswaraRao Talluri tall...@apache.org Fix pep8 issues in various test suites -- Key: CLOUDSTACK-7693 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7693 Project: CloudStack Issue Type: Task Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.5.0 Reporter: Gaurav Aradhye Assignee: Gaurav Aradhye Labels: automation Fix For: 4.5.0 Fix all pep8 issues in various regression and BVT test suites. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7690) test_escalations_volumes.py is missing unittest import
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14172018#comment-14172018 ] ASF subversion and git services commented on CLOUDSTACK-7690: - Commit bd9d57e20c4f8bd49fd403841cff909016987ced in cloudstack's branch refs/heads/master from [~gauravaradhye] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=bd9d57e ] CLOUDSTACK-7690: Added missing unittest import to test_escalations_volumes.py fixed pep8 issues Signed-off-by: SrikanteswaraRao Talluri tall...@apache.org test_escalations_volumes.py is missing unittest import Key: CLOUDSTACK-7690 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7690 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.5.0 Reporter: Gaurav Aradhye Assignee: Gaurav Aradhye Labels: automation Fix For: 4.5.0 The previous commit added Added hyper-v hypervisor checks for automated tests functionality and used unittest.skipTest to skip tests, but the file is missing the unittest import. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7505) Windows 2012 and Windows 8 instances created with 6.5 PV tools installed template are getting into repair state, Later XenServer 6.5 Is shutting down these instances
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-7505: - Fix Version/s: 4.5.0 Windows 2012 and Windows 8 instances created with 6.5 PV tools installed template are getting into repair state, Later XenServer 6.5 Is shutting down these instances automatically Key: CLOUDSTACK-7505 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7505 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: XenServer Affects Versions: 4.5.0 Reporter: Sailaja Mada Assignee: Anthony Xu Priority: Blocker Fix For: 4.5.0 Attachments: i-2-10-VM-from-tools-template, i-2-7-vm-params-after-registeriso-PVtoolsinstallation Steps: 1. Configure Adv Zone using XenServer 6.5 2. Registered Windows 8 and Windows 2012 templates which has XS 6.5 PV tools installed.I have enabled option Original XS Version is 6.1+: Yes 3. Deployed VM using this template 4. VM got started and moved to running state. But got into repair state, Later XenServer 6.5 Is shutting down these instances automatically. VM Parameters are : platform (MRW): timeoffset: 0; viridian: true; acpi: 1; ap ic: true; pae: true; videoram: 8; device_id: 0002; nx: true; vga: std allowed-operations (SRO): changing_dynamic_range; hard_reboot; hard_ shutdown; pause; snapshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-7505) Windows 2012 and Windows 8 instances created with 6.5 PV tools installed template are getting into repair state, Later XenServer 6.5 Is shutting down these instances
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada closed CLOUDSTACK-7505. This is fixed now. Hence closing the bug. Windows 2012 and Windows 8 instances created with 6.5 PV tools installed template are getting into repair state, Later XenServer 6.5 Is shutting down these instances automatically Key: CLOUDSTACK-7505 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7505 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: XenServer Affects Versions: 4.5.0 Reporter: Sailaja Mada Assignee: Anthony Xu Priority: Blocker Fix For: 4.5.0 Attachments: i-2-10-VM-from-tools-template, i-2-7-vm-params-after-registeriso-PVtoolsinstallation Steps: 1. Configure Adv Zone using XenServer 6.5 2. Registered Windows 8 and Windows 2012 templates which has XS 6.5 PV tools installed.I have enabled option Original XS Version is 6.1+: Yes 3. Deployed VM using this template 4. VM got started and moved to running state. But got into repair state, Later XenServer 6.5 Is shutting down these instances automatically. VM Parameters are : platform (MRW): timeoffset: 0; viridian: true; acpi: 1; ap ic: true; pae: true; videoram: 8; device_id: 0002; nx: true; vga: std allowed-operations (SRO): changing_dynamic_range; hard_reboot; hard_ shutdown; pause; snapshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
