[jira] [Commented] (CLOUDSTACK-2653) Resources aren't allocated for SystemVMs correctly
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741320#comment-13741320 ] Sudha Ponnaganti commented on CLOUDSTACK-2653: -- Wido - looks like this is not an issue. can I close it?? Resources aren't allocated for SystemVMs correctly -- Key: CLOUDSTACK-2653 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2653 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: Future Environment: Ubuntu 12.04 running master branch Reporter: Wido den Hollander Assignee: Prachi Damle Fix For: 4.2.0 I just upgraded my 4.1 management server to the master branch and after a painful database upgrade it is running. I don't have a SSVM, so it's trying to start it, but that fails. The logs show: 2013-05-23 17:50:13,199 DEBUG [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone 1 is ready to launch secondary storage VM 2013-05-23 17:50:13,203 INFO [cloud.secstorage.PremiumSecondaryStorageManagerImpl] (secstorage-1:null) No running secondary storage vms found in datacenter id=1, starting one 2013-05-23 17:50:13,207 INFO [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Found a stopped secondary storage vm, bring it up to running pool. secStorageVm vm id : 3864 2013-05-23 17:50:13,212 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:null) VM state transitted from :Stopped to Starting with event: StartRequestedvm's original host id: null new host id: null host id before state transition: null 2013-05-23 17:50:13,212 DEBUG [cloud.vm.VirtualMachineManagerImpl] (secstorage-1:null) Successfully transitioned to start state for VM[SecondaryStorageVm|s-3864-VM] reservation id = 6a001536-691b-406d-b7fe-9d8236cefc17 2013-05-23 17:50:13,246 DEBUG [cloud.vm.VirtualMachineManagerImpl] (secstorage-1:null) Trying to deploy VM, vm has dcId: 1 and podId: null 2013-05-23 17:50:13,246 DEBUG [cloud.vm.VirtualMachineManagerImpl] (secstorage-1:null) Deploy avoids pods: null, clusters: null, hosts: null 2013-05-23 17:50:13,247 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (secstorage-1:null) Deploy avoids pods: null, clusters: null, hosts: null 2013-05-23 17:50:13,248 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (secstorage-1:null) DeploymentPlanner allocation algorithm: com.cloud.deploy.FirstFitPlanner_EnhancerByCloudStack_eb858ef2@67cb9b56 2013-05-23 17:50:13,248 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (secstorage-1:null) Trying to allocate a host and storage pools from dc:1, pod:null,cluster:null, requested cpu: 500, requested ram: 268435456 2013-05-23 17:50:13,248 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (secstorage-1:null) Is ROOT volume READY (pool already allocated)?: No 2013-05-23 17:50:13,248 DEBUG [cloud.deploy.FirstFitPlanner] (secstorage-1:null) Searching all possible resources under this Zone: 1 2013-05-23 17:50:13,248 DEBUG [cloud.deploy.FirstFitPlanner] (secstorage-1:null) Listing clusters in order of aggregate capacity, that have (atleast one host with) enough CPU and RAM capacity under this Zone: 1 2013-05-23 17:50:13,250 DEBUG [cloud.deploy.FirstFitPlanner] (secstorage-1:null) No clusters found having a host with enough capacity, returning. 2013-05-23 17:50:13,313 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:null) VM state transitted from :Starting to Stopped with event: OperationFailedvm's original host id: null new host id: null host id before state transition: null 2013-05-23 17:50:13,314 WARN [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Exception while trying to start secondary storage vm com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[SecondaryStorageVm|s-3864-VM]Scope=interface com.cloud.dc.DataCenter; id=1 at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:813) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:550) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:543) at com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(SecondaryStorageManagerImpl.java:262) at com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:687) at com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1303) at
[jira] [Commented] (CLOUDSTACK-3366) Autoscaling won't scale down
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741323#comment-13741323
]
Sudha Ponnaganti commented on CLOUDSTACK-3366:
--
Francois,
I will close it and pl reopen if you see this again
thanks
/sudha
Autoscaling won't scale down
Key: CLOUDSTACK-3366
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3366
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.1.0, 4.2.0
Reporter: Francois Gaudreault
Assignee: Rajesh Battala
Priority: Critical
Fix For: 4.2.0
When configuring Autoscaling, the autoscale will go UP, but not DOWN when
traffic is back under thresholds.
NetScaler seems to be triggering the SCALE_DOWN, but nothing happens on the
CS side.
Netscaler did:
Autoscale: Evaluating autoscale policy
Cloud-AutoScale-Policy-x-80-12Autoscale: Triggering autoscale action:
SCALE_DOWN for policy: Cloud-AutoScale-ScaleDownAction-x-80Autoscale:
:::925###POST /provision HTTP/1.1
Host: NS
Content-Length: 866
{ autoscale : { ns : { sysid : 9831cb254307ee78 }, vserver : {
name : Cloud-VirtualServer-x-80, servicegroupname :
Cloudf84eaf4ed3fe43aebbc4d2ff9f7311bc }, cloudprofile : { type :
CLOUDSTACK, url : http://172.30.100.15:8080/client/api;, apiKey :
x2134OIL1TKNyW6PahIq4NubxMn1tK3krpQFyDWks8fv_[...], sharedsecret :
HtpqjvHENGMqZLBcn_o-_[...] }, action : { type : SCALE_DOWN, params
:
command=destroyVirtualMachinelbruleid=24aab38f-f466-45c5-9878-484841ba1b9d,
quiettime : 300, destroyVMGracePeriod : 30 }, autoprovisiondns : {
nsdomainname :
autoscale-internal_server_Cloudf84eaf4ed3fe43aebbc4d2ff9f7311bc,
nsservername :
autoscale-internal_server_Cloudf84eaf4ed3fe43aebbc4d2ff9f7311bc } } }:::
current time is Tue Jul 2 21:09:09 2013
Autoscale: Timer Event: Cloud-AutoScale-Timer-x-80
Returning avg_val: 67
If I look in CloudStack, I do see the deployVirtualMachine calls coming from
the NetScaler during the scale up, but I don't see any destroyVirtualMachine
hitting the server for the scale down.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-3366) Autoscaling won't scale down
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sudha Ponnaganti closed CLOUDSTACK-3366.
Autoscaling won't scale down
Key: CLOUDSTACK-3366
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3366
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.1.0, 4.2.0
Reporter: Francois Gaudreault
Assignee: Rajesh Battala
Priority: Critical
Fix For: 4.2.0
When configuring Autoscaling, the autoscale will go UP, but not DOWN when
traffic is back under thresholds.
NetScaler seems to be triggering the SCALE_DOWN, but nothing happens on the
CS side.
Netscaler did:
Autoscale: Evaluating autoscale policy
Cloud-AutoScale-Policy-x-80-12Autoscale: Triggering autoscale action:
SCALE_DOWN for policy: Cloud-AutoScale-ScaleDownAction-x-80Autoscale:
:::925###POST /provision HTTP/1.1
Host: NS
Content-Length: 866
{ autoscale : { ns : { sysid : 9831cb254307ee78 }, vserver : {
name : Cloud-VirtualServer-x-80, servicegroupname :
Cloudf84eaf4ed3fe43aebbc4d2ff9f7311bc }, cloudprofile : { type :
CLOUDSTACK, url : http://172.30.100.15:8080/client/api;, apiKey :
x2134OIL1TKNyW6PahIq4NubxMn1tK3krpQFyDWks8fv_[...], sharedsecret :
HtpqjvHENGMqZLBcn_o-_[...] }, action : { type : SCALE_DOWN, params
:
command=destroyVirtualMachinelbruleid=24aab38f-f466-45c5-9878-484841ba1b9d,
quiettime : 300, destroyVMGracePeriod : 30 }, autoprovisiondns : {
nsdomainname :
autoscale-internal_server_Cloudf84eaf4ed3fe43aebbc4d2ff9f7311bc,
nsservername :
autoscale-internal_server_Cloudf84eaf4ed3fe43aebbc4d2ff9f7311bc } } }:::
current time is Tue Jul 2 21:09:09 2013
Autoscale: Timer Event: Cloud-AutoScale-Timer-x-80
Returning avg_val: 67
If I look in CloudStack, I do see the deployVirtualMachine calls coming from
the NetScaler during the scale up, but I don't see any destroyVirtualMachine
hitting the server for the scale down.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-1868) GetVmStatsCommand throws NullPointerException with VMWare
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-1868: - Assignee: Sateesh Chodapuneedi GetVmStatsCommand throws NullPointerException with VMWare - Key: CLOUDSTACK-1868 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1868 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.1.0, 4.2.0 Reporter: Francois Gaudreault Assignee: Sateesh Chodapuneedi Fix For: 4.2.0 Attachments: management.log, management-server.log.tgz, screenshot-1.jpg We see bunch of these in the log files of CloudStack. Looks like the GetVmStatsCommand crash with a Null pointer exception. We don't think it's permission related since our CS user on vSphere can see all performance and VM statistics using the vSphere client. INFO [agent.manager.AgentManagerImpl] (AgentTaskPool-6:) Agent is determined to be up and running ERROR [vmware.resource.VmwareResource] (DirectAgent-383:yul01vi13.ops.dot) Unable to execute GetVmStatsCommand due to : Exception: java.lang.NullPointerException Message: null java.lang.NullPointerException WARN [cloud.vm.UserVmManagerImpl] (StatsCollector-2:) Unable to obtain VM statistics. ERROR [vmware.resource.VmwareResource] (DirectAgent-67:yul01vi12.ops.dot) Unable to execute GetVmStatsCommand due to : Exception: java.lang.NullPointerException Message: null java.lang.NullPointerException WARN [cloud.vm.UserVmManagerImpl] (StatsCollector-2:) Unable to obtain VM statistics. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-1868) GetVmStatsCommand throws NullPointerException with VMWare
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741326#comment-13741326 ] Sudha Ponnaganti commented on CLOUDSTACK-1868: -- Ilya and Sateesh mentioned that they are not able to reproduce. Pl reopen if you see this problem again thanks /sudha GetVmStatsCommand throws NullPointerException with VMWare - Key: CLOUDSTACK-1868 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1868 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.1.0, 4.2.0 Reporter: Francois Gaudreault Assignee: Sateesh Chodapuneedi Fix For: 4.2.0 Attachments: management.log, management-server.log.tgz, screenshot-1.jpg We see bunch of these in the log files of CloudStack. Looks like the GetVmStatsCommand crash with a Null pointer exception. We don't think it's permission related since our CS user on vSphere can see all performance and VM statistics using the vSphere client. INFO [agent.manager.AgentManagerImpl] (AgentTaskPool-6:) Agent is determined to be up and running ERROR [vmware.resource.VmwareResource] (DirectAgent-383:yul01vi13.ops.dot) Unable to execute GetVmStatsCommand due to : Exception: java.lang.NullPointerException Message: null java.lang.NullPointerException WARN [cloud.vm.UserVmManagerImpl] (StatsCollector-2:) Unable to obtain VM statistics. ERROR [vmware.resource.VmwareResource] (DirectAgent-67:yul01vi12.ops.dot) Unable to execute GetVmStatsCommand due to : Exception: java.lang.NullPointerException Message: null java.lang.NullPointerException WARN [cloud.vm.UserVmManagerImpl] (StatsCollector-2:) Unable to obtain VM statistics. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-1868) GetVmStatsCommand throws NullPointerException with VMWare
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-1868. GetVmStatsCommand throws NullPointerException with VMWare - Key: CLOUDSTACK-1868 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1868 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.1.0, 4.2.0 Reporter: Francois Gaudreault Assignee: Sateesh Chodapuneedi Fix For: 4.2.0 Attachments: management.log, management-server.log.tgz, screenshot-1.jpg We see bunch of these in the log files of CloudStack. Looks like the GetVmStatsCommand crash with a Null pointer exception. We don't think it's permission related since our CS user on vSphere can see all performance and VM statistics using the vSphere client. INFO [agent.manager.AgentManagerImpl] (AgentTaskPool-6:) Agent is determined to be up and running ERROR [vmware.resource.VmwareResource] (DirectAgent-383:yul01vi13.ops.dot) Unable to execute GetVmStatsCommand due to : Exception: java.lang.NullPointerException Message: null java.lang.NullPointerException WARN [cloud.vm.UserVmManagerImpl] (StatsCollector-2:) Unable to obtain VM statistics. ERROR [vmware.resource.VmwareResource] (DirectAgent-67:yul01vi12.ops.dot) Unable to execute GetVmStatsCommand due to : Exception: java.lang.NullPointerException Message: null java.lang.NullPointerException WARN [cloud.vm.UserVmManagerImpl] (StatsCollector-2:) Unable to obtain VM statistics. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2072) Virtual Routers Failover not working
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741328#comment-13741328 ] Sudha Ponnaganti commented on CLOUDSTACK-2072: -- Closing with Kaushik's comments Virtual Routers Failover not working Key: CLOUDSTACK-2072 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2072 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, Network Controller, Virtual Router Affects Versions: 4.0.1, 4.1.0, 4.2.0 Reporter: Jeronimo Assignee: Koushik Das Fix For: 4.2.0 I've experienced some erratic behavior when when setting a host in maintenance mode: I had about 6 Virtual routers running and 2 system vms in a given host , after putting this host in maintenance mode the system vms failed over successfully. The problem came in when the VirtualRouters failed over , they did not start up at all, even after waiting 1 hour for HA to kick in . When i went on and start the virtual routers manually it would fail with this error: 2013-04-17 08:54:39,566 DEBUG [allocator.impl.FirstFitAllocator] (catalina-exec-2:null) Host name: kickseed, hostId: 1 is in avoid set, skipping this and trying other available hosts 2013-04-17 08:54:39,566 DEBUG [allocator.impl.FirstFitAllocator] (catalina-exec-2:null) Host Allocator returning 0 suitable hosts The work around i found is : Destroying the virtual router for network X Restart network X Is this the expected behaviour for virtual router fail over ? I'm using cloudstack 4.0.1 on Ubuntu . Thanks! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-2072) Virtual Routers Failover not working
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-2072. Virtual Routers Failover not working Key: CLOUDSTACK-2072 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2072 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, Network Controller, Virtual Router Affects Versions: 4.0.1, 4.1.0, 4.2.0 Reporter: Jeronimo Assignee: Koushik Das Fix For: 4.2.0 I've experienced some erratic behavior when when setting a host in maintenance mode: I had about 6 Virtual routers running and 2 system vms in a given host , after putting this host in maintenance mode the system vms failed over successfully. The problem came in when the VirtualRouters failed over , they did not start up at all, even after waiting 1 hour for HA to kick in . When i went on and start the virtual routers manually it would fail with this error: 2013-04-17 08:54:39,566 DEBUG [allocator.impl.FirstFitAllocator] (catalina-exec-2:null) Host name: kickseed, hostId: 1 is in avoid set, skipping this and trying other available hosts 2013-04-17 08:54:39,566 DEBUG [allocator.impl.FirstFitAllocator] (catalina-exec-2:null) Host Allocator returning 0 suitable hosts The work around i found is : Destroying the virtual router for network X Restart network X Is this the expected behaviour for virtual router fail over ? I'm using cloudstack 4.0.1 on Ubuntu . Thanks! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-4357) [Automation] Failed to create snapshot in vmware, failed with SOAP Exception
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sudha Ponnaganti updated CLOUDSTACK-4357:
-
Priority: Critical (was: Major)
[Automation] Failed to create snapshot in vmware, failed with SOAP Exception
Key: CLOUDSTACK-4357
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4357
Project: CloudStack
Issue Type: Test
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation, Snapshot, VMware
Affects Versions: 4.2.0
Environment: 4.2 build
Automation setup in vmware
Reporter: Rayees Namathponnan
Priority: Critical
Fix For: 4.2.0
Create snapshot from volume in vmware, snapshot creation failed with below
error
result:true,wait:0}}] }
2013-08-15 11:28:36,021 DEBUG [agent.transport.Request]
(Job-Executor-132:job-2140 = [ 5e9e1e44-ab33-4b64-bd3b-5b6ab4e69389 ]) Seq
3-1674384702: Received: { Ans: , MgmtId: 90
928106758026, via: 3, Ver: v1, Flags: 10, {
CreateObjectAnswer } }
2013-08-15 11:28:36,116 DEBUG [storage.motion.AncientDataMotionStrategy]
(Job-Executor-132:job-2140 = [ 5e9e1e44-ab33-4b64-bd3b-5b6ab4e69389 ])
copyAsync inspecting src type S
NAPSHOT copyAsync inspecting dest type SNAPSHOT
2013-08-15 11:28:36,205 DEBUG [agent.transport.Request]
(Job-Executor-132:job-2140 = [ 5e9e1e44-ab33-4b64-bd3b-5b6ab4e69389 ]) Seq
9-1658651749: Sending { Cmd , MgmtId: 90928
106758026, via: 9, Ver: v1, Flags: 100011,
[{org.apache.cloudstack.storage.command.CopyCommand:{srcTO:{org.apache.cloudstack.storage.to.SnapshotObjectTO:{path:7e5f482
3-9341-4d82-84a2-885f690523a3,volume:{uuid:a3cb5568-9e7d-432b-b2b9-b7947fc34f2d,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{
uuid:16c8ee2e-3f26-3062-8878-b7d6c53c5797,id:2,poolType:NetworkFilesystem,host:10.223.110.232,path:/export/home/automation/SC-CLOUD-QA03/primary2,port:2049
}},name:ROOT-585,size:2147483648,path:ROOT-585,volumeId:642,vmName:i-2-585-TestVM,accountId:2,format:OVA,id:642,hypervisorType:VMware},dataStore:
{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:16c8ee2e-3f26-3062-8878-b7d6c53c5797,id:2,poolType:NetworkFilesystem,host:10.223.110.232,path:/ex
port/home/automation/SC-CLOUD-QA03/primary2,port:2049}},vmName:i-2-585-TestVM,name:ryzVM_ROOT-585_20130815182835,hypervisorType:VMware,id:21}},destTO:{org.
apache.cloudstack.storage.to.SnapshotObjectTO:{path:snapshots/2/642,volume:{uuid:a3cb5568-9e7d-432b-b2b9-b7947fc34f2d,volumeType:ROOT,dataStore:{org.apache.c
loudstack.storage.to.PrimaryDataStoreTO:{uuid:16c8ee2e-3f26-3062-8878-b7d6c53c5797,id:2,poolType:NetworkFilesystem,host:10.223.110.232,path:/export/home/auto
mation/SC-CLOUD-QA03/primary2,port:2049}},name:ROOT-585,size:2147483648,path:ROOT-585,volumeId:642,vmName:i-2-585-TestVM,accountId:2,format:OVA,id:6
42,hypervisorType:VMware},dataStore:{com.cloud.agent.api.to.NfsTO:{_url:nfs://10.223.110.232:/export/home/automation/SC-CLOUD-QA03/secondary1,_role:Image}},vm
Name:i-2-585-TestVM,name:ryzVM_ROOT-585_20130815182835,hypervisorType:VMware,id:21}},executeInSequence:false,wait:21600}}]
}
2013-08-15 11:28:36,459 DEBUG [agent.transport.Request]
(AgentManager-Handler-6:null) Seq 9-1658651749: Processing: { Ans: , MgmtId:
90928106758026, via: 9, Ver: v1, Flags: 1
0,
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:backup
snapshot exception: Exception:
javax.xml.ws.soap.SOAPFaultException\nMessage: \nRe
quired property obj is missing from data
object of type ObjectSpec\n\nwhile parsing serialized DataObject of type
vmodl.query.PropertyCollector.ObjectSpec\nat line 1, column 3
05\n\nwhile parsing property
\objectSet\ of static
[jira] [Updated] (CLOUDSTACK-4357) [Automation] Failed to create snapshot in vmware, failed with SOAP Exception
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sudha Ponnaganti updated CLOUDSTACK-4357:
-
Issue Type: Bug (was: Test)
[Automation] Failed to create snapshot in vmware, failed with SOAP Exception
Key: CLOUDSTACK-4357
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4357
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation, Snapshot, VMware
Affects Versions: 4.2.0
Environment: 4.2 build
Automation setup in vmware
Reporter: Rayees Namathponnan
Priority: Critical
Fix For: 4.2.0
Create snapshot from volume in vmware, snapshot creation failed with below
error
result:true,wait:0}}] }
2013-08-15 11:28:36,021 DEBUG [agent.transport.Request]
(Job-Executor-132:job-2140 = [ 5e9e1e44-ab33-4b64-bd3b-5b6ab4e69389 ]) Seq
3-1674384702: Received: { Ans: , MgmtId: 90
928106758026, via: 3, Ver: v1, Flags: 10, {
CreateObjectAnswer } }
2013-08-15 11:28:36,116 DEBUG [storage.motion.AncientDataMotionStrategy]
(Job-Executor-132:job-2140 = [ 5e9e1e44-ab33-4b64-bd3b-5b6ab4e69389 ])
copyAsync inspecting src type S
NAPSHOT copyAsync inspecting dest type SNAPSHOT
2013-08-15 11:28:36,205 DEBUG [agent.transport.Request]
(Job-Executor-132:job-2140 = [ 5e9e1e44-ab33-4b64-bd3b-5b6ab4e69389 ]) Seq
9-1658651749: Sending { Cmd , MgmtId: 90928
106758026, via: 9, Ver: v1, Flags: 100011,
[{org.apache.cloudstack.storage.command.CopyCommand:{srcTO:{org.apache.cloudstack.storage.to.SnapshotObjectTO:{path:7e5f482
3-9341-4d82-84a2-885f690523a3,volume:{uuid:a3cb5568-9e7d-432b-b2b9-b7947fc34f2d,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{
uuid:16c8ee2e-3f26-3062-8878-b7d6c53c5797,id:2,poolType:NetworkFilesystem,host:10.223.110.232,path:/export/home/automation/SC-CLOUD-QA03/primary2,port:2049
}},name:ROOT-585,size:2147483648,path:ROOT-585,volumeId:642,vmName:i-2-585-TestVM,accountId:2,format:OVA,id:642,hypervisorType:VMware},dataStore:
{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:16c8ee2e-3f26-3062-8878-b7d6c53c5797,id:2,poolType:NetworkFilesystem,host:10.223.110.232,path:/ex
port/home/automation/SC-CLOUD-QA03/primary2,port:2049}},vmName:i-2-585-TestVM,name:ryzVM_ROOT-585_20130815182835,hypervisorType:VMware,id:21}},destTO:{org.
apache.cloudstack.storage.to.SnapshotObjectTO:{path:snapshots/2/642,volume:{uuid:a3cb5568-9e7d-432b-b2b9-b7947fc34f2d,volumeType:ROOT,dataStore:{org.apache.c
loudstack.storage.to.PrimaryDataStoreTO:{uuid:16c8ee2e-3f26-3062-8878-b7d6c53c5797,id:2,poolType:NetworkFilesystem,host:10.223.110.232,path:/export/home/auto
mation/SC-CLOUD-QA03/primary2,port:2049}},name:ROOT-585,size:2147483648,path:ROOT-585,volumeId:642,vmName:i-2-585-TestVM,accountId:2,format:OVA,id:6
42,hypervisorType:VMware},dataStore:{com.cloud.agent.api.to.NfsTO:{_url:nfs://10.223.110.232:/export/home/automation/SC-CLOUD-QA03/secondary1,_role:Image}},vm
Name:i-2-585-TestVM,name:ryzVM_ROOT-585_20130815182835,hypervisorType:VMware,id:21}},executeInSequence:false,wait:21600}}]
}
2013-08-15 11:28:36,459 DEBUG [agent.transport.Request]
(AgentManager-Handler-6:null) Seq 9-1658651749: Processing: { Ans: , MgmtId:
90928106758026, via: 9, Ver: v1, Flags: 1
0,
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:backup
snapshot exception: Exception:
javax.xml.ws.soap.SOAPFaultException\nMessage: \nRe
quired property obj is missing from data
object of type ObjectSpec\n\nwhile parsing serialized DataObject of type
vmodl.query.PropertyCollector.ObjectSpec\nat line 1, column 3
05\n\nwhile parsing property
\objectSet\ of static type
[jira] [Closed] (CLOUDSTACK-1868) GetVmStatsCommand throws NullPointerException with VMWare
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-1868. GetVmStatsCommand throws NullPointerException with VMWare - Key: CLOUDSTACK-1868 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1868 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.1.0, 4.2.0 Reporter: Francois Gaudreault Assignee: Sateesh Chodapuneedi Fix For: 4.2.0 Attachments: management.log, management-server.log.tgz, screenshot-1.jpg We see bunch of these in the log files of CloudStack. Looks like the GetVmStatsCommand crash with a Null pointer exception. We don't think it's permission related since our CS user on vSphere can see all performance and VM statistics using the vSphere client. INFO [agent.manager.AgentManagerImpl] (AgentTaskPool-6:) Agent is determined to be up and running ERROR [vmware.resource.VmwareResource] (DirectAgent-383:yul01vi13.ops.dot) Unable to execute GetVmStatsCommand due to : Exception: java.lang.NullPointerException Message: null java.lang.NullPointerException WARN [cloud.vm.UserVmManagerImpl] (StatsCollector-2:) Unable to obtain VM statistics. ERROR [vmware.resource.VmwareResource] (DirectAgent-67:yul01vi12.ops.dot) Unable to execute GetVmStatsCommand due to : Exception: java.lang.NullPointerException Message: null java.lang.NullPointerException WARN [cloud.vm.UserVmManagerImpl] (StatsCollector-2:) Unable to obtain VM statistics. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-2610) Unable to add host due to missing setiptables plugin
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sudha Ponnaganti closed CLOUDSTACK-2610.
Unable to add host due to missing setiptables plugin
Key: CLOUDSTACK-2610
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2610
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Affects Versions: 4.0.2
Environment: CentOS 6.2 (64-bit) installed from RPM packages
Reporter: Michael Dickey
Assignee: Anthony Xu
Priority: Critical
Fix For: 4.2.0
After upgrade from 4.0.1 to 4.0.2 I am unable to add hosts back into my
cluster. I keep getting an error about a missing setIptables plugin:
{noformat}
INFO [xen.discoverer.XcpServerDiscoverer] (AgentTaskPool-3:) Host: xen3
connected with hypervisor type: XenServer. Checking CIDR...
INFO [agent.manager.DirectAgentAttache] (AgentTaskPool-3:) StartupAnswer
received 10 Interval = 60
INFO [xen.resource.CitrixResourceBase] (DirectAgent-5:) Host 10.0.2.13
OpaqueRef:16671632-3d13-fded-3729-7e675c3ab790: Host 10.0.2.13 is already
setup.
WARN [xen.resource.CitrixResourceBase] (DirectAgent-5:) callHostPlugin
failed for cmd: setIptables with args due to The requested plugin could not
be found.
WARN [xen.resource.CitrixResourceBase] (DirectAgent-5:) Unable to setup
com.cloud.utils.exception.CloudRuntimeException: callHostPlugin failed for
cmd: setIptables with args due to The requested plugin could not be found.
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.callHostPlugin(CitrixResourceBase.java:3745)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.setIptables(CitrixResourceBase.java:3757)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:4528)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:485)
at
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
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.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
WARN [xen.discoverer.XcpServerDiscoverer] (AgentTaskPool-3:) Unable to setup
agent 10 due to callHostPlugin failed for cmd: setIptables with args due to
The requested plugin could not be found.
WARN [agent.manager.AgentManagerImpl] (AgentTaskPool-3:) Monitor
XcpServerDiscoverer$$EnhancerByCGLIB$$350a7d8b says there is an error in the
connect process for 10 due to Reinitialize agent after setup.
INFO [agent.manager.AgentManagerImpl] (AgentTaskPool-3:) Host 10 is
disconnecting with event AgentDisconnected
WARN [cloud.resource.ResourceManagerImpl] (AgentTaskPool-3:) Unable to
connect due to
com.cloud.exception.ConnectionException: Reinitialize agent after setup.
at
com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.processConnect(XcpServerDiscoverer.java:651)
at
com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:605)
at
com.cloud.agent.manager.AgentManagerImpl.handleDirectConnectAgent(AgentManagerImpl.java:1505)
at
com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1631)
at
com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1668)
at
com.cloud.agent.manager.AgentManagerImpl$SimulateStartTask.run(AgentManagerImpl.java:1200)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2610) Unable to add host due to missing setiptables plugin
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741332#comment-13741332
]
Sudha Ponnaganti commented on CLOUDSTACK-2610:
--
closing it - pl reopen if you see it again
Unable to add host due to missing setiptables plugin
Key: CLOUDSTACK-2610
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2610
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Affects Versions: 4.0.2
Environment: CentOS 6.2 (64-bit) installed from RPM packages
Reporter: Michael Dickey
Assignee: Anthony Xu
Priority: Critical
Fix For: 4.2.0
After upgrade from 4.0.1 to 4.0.2 I am unable to add hosts back into my
cluster. I keep getting an error about a missing setIptables plugin:
{noformat}
INFO [xen.discoverer.XcpServerDiscoverer] (AgentTaskPool-3:) Host: xen3
connected with hypervisor type: XenServer. Checking CIDR...
INFO [agent.manager.DirectAgentAttache] (AgentTaskPool-3:) StartupAnswer
received 10 Interval = 60
INFO [xen.resource.CitrixResourceBase] (DirectAgent-5:) Host 10.0.2.13
OpaqueRef:16671632-3d13-fded-3729-7e675c3ab790: Host 10.0.2.13 is already
setup.
WARN [xen.resource.CitrixResourceBase] (DirectAgent-5:) callHostPlugin
failed for cmd: setIptables with args due to The requested plugin could not
be found.
WARN [xen.resource.CitrixResourceBase] (DirectAgent-5:) Unable to setup
com.cloud.utils.exception.CloudRuntimeException: callHostPlugin failed for
cmd: setIptables with args due to The requested plugin could not be found.
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.callHostPlugin(CitrixResourceBase.java:3745)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.setIptables(CitrixResourceBase.java:3757)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:4528)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:485)
at
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
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.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
WARN [xen.discoverer.XcpServerDiscoverer] (AgentTaskPool-3:) Unable to setup
agent 10 due to callHostPlugin failed for cmd: setIptables with args due to
The requested plugin could not be found.
WARN [agent.manager.AgentManagerImpl] (AgentTaskPool-3:) Monitor
XcpServerDiscoverer$$EnhancerByCGLIB$$350a7d8b says there is an error in the
connect process for 10 due to Reinitialize agent after setup.
INFO [agent.manager.AgentManagerImpl] (AgentTaskPool-3:) Host 10 is
disconnecting with event AgentDisconnected
WARN [cloud.resource.ResourceManagerImpl] (AgentTaskPool-3:) Unable to
connect due to
com.cloud.exception.ConnectionException: Reinitialize agent after setup.
at
com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.processConnect(XcpServerDiscoverer.java:651)
at
com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:605)
at
com.cloud.agent.manager.AgentManagerImpl.handleDirectConnectAgent(AgentManagerImpl.java:1505)
at
com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1631)
at
com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1668)
at
com.cloud.agent.manager.AgentManagerImpl$SimulateStartTask.run(AgentManagerImpl.java:1200)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-4202) [IPv4][dnsmasq] VM not able get ip from dhcp which is previously assigned to vm
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-4202. [IPv4][dnsmasq] VM not able get ip from dhcp which is previously assigned to vm Key: CLOUDSTACK-4202 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4202 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller, Virtual Router Affects Versions: 4.2.0 Environment: CentOS 6.3 64bit for KVM Host. Reporter: Naoki Sakamoto Assignee: Jayapal Reddy Priority: Critical Fix For: 4.2.0 Original Estimate: 168h Remaining Estimate: 168h Related : CLOUDSTACK-3533 [IPv6][dnsmasq] VM not able get ip from dhcp which is previously assigned to vm IPv4 has same issue. 1. Create VPC (Super CIDR = 10.0.0.0/16) 2. Create Tier (CIDR = 10.0.0.0/30, GW = 10.0.0.1, Netmask = 255.255.255.252) 3. Deploy VM01 (IP = 10.0.0.2) 4. Destroy VM01 5. Deploy VM02 (IP = 10.0.0.2) VM02 Guest OS is not getting IP Address. I confirmed in bigger range Tier (CIDR = 10.0.0.0/27, Netmask = 255.255.255.224) about 30 VMs and same issue occurred. New VM can't get IP that is exhousted and released. On Virtual Router /var/log/dnsmasq.log Aug 8 08:53:16 dnsmasq[13590]: read /etc/hosts - 6 addresses Aug 8 08:53:16 dnsmasq-dhcp[13590]: read /etc/dhcphosts.txt Aug 8 08:53:16 dnsmasq-dhcp[13590]: read /etc/dhcpopts.txt Aug 8 08:54:27 dnsmasq-dhcp[13590]: not using configured address 10.0.0.2 because it is leased to 02:00:68:25:00:07 Aug 8 08:54:27 dnsmasq-dhcp[13590]: DHCPDISCOVER(eth2) 10.0.2.15 02:00:5d:19:00:09 no address available Aug 8 08:54:31 dnsmasq-dhcp[13590]: not using configured address 10.0.0.2 because it is leased to 02:00:68:25:00:07 Aug 8 08:54:31 dnsmasq-dhcp[13590]: DHCPDISCOVER(eth2) 10.0.2.15 02:00:5d:19:00:09 no address available Aug 8 08:54:41 dnsmasq-dhcp[13590]: not using configured address 10.0.0.2 because it is leased to 02:00:68:25:00:07 Aug 8 08:54:41 dnsmasq-dhcp[13590]: DHCPDISCOVER(eth2) 10.0.2.15 02:00:5d:19:00:09 no address available Aug 8 08:55:02 dnsmasq-dhcp[13590]: not using configured address 10.0.0.2 because it is leased to 02:00:68:25:00:07 Aug 8 08:55:02 dnsmasq-dhcp[13590]: DHCPDISCOVER(eth2) 10.0.2.15 02:00:5d:19:00:09 no address available Aug 8 08:55:21 dnsmasq-dhcp[13590]: not using configured address 10.0.0.2 because it is leased to 02:00:68:25:00:07 Aug 8 08:55:21 dnsmasq-dhcp[13590]: DHCPDISCOVER(eth2) 10.0.2.15 02:00:5d:19:00:09 no address available 02:00:68:25:00:07 is VM01's Mac Address. On Virtual Router /var/log/messages (on issue time) Aug 8 08:53:01 r-11-VM cloud: Password server failed with error code 1. Restarting socat... Aug 8 08:53:04 r-11-VM cloud: Password server failed with error code 1. Restarting socat... Aug 8 08:53:07 r-11-VM cloud: Password server failed with error code 1. Restarting socat... Aug 8 08:53:10 r-11-VM cloud: Password server failed with error code 1. Restarting socat... Aug 8 08:53:13 r-11-VM cloud: Password server failed with error code 1. Restarting socat... Aug 8 08:53:16 r-11-VM cloud: edithosts: releasing 10.0.0.2 Aug 8 08:53:16 r-11-VM cloud: edithosts: released 10.0.0.2 Aug 8 08:53:16 r-11-VM cloud: edithosts: update 02:00:5d:19:00:09 10.0.0.2 sakamoto035 to hosts Aug 8 08:53:16 r-11-VM cloud: Password server failed with error code 1. Restarting socat... Aug 8 08:53:19 r-11-VM cloud: Password server failed with error code 1. Restarting socat... Aug 8 08:53:22 r-11-VM cloud: Password server failed with error code 1. Restarting socat... Aug 8 08:53:25 r-11-VM cloud: Password server failed with error code 1. Restarting socat... Aug 8 08:53:28 r-11-VM cloud: Password server failed with error code 1. Restarting socat... I found edithosts: releasing 10.0.0.2 and edithosts: released 10.0.0.2. Then I think no_dhcp_release = 0 in edithosts.sh at that time. I used latest edithosts.sh. I could recover as following. 1. On Virtual Router # service dnsmasq restart 2. Restart VM02 by GUI. VM02 got IP Address 10.0.0.2. System template version : root@r-11-VM:~# sh /opt/cloud/bin/get_template_version.sh Cloudstack Release 4.2.0 Thu Jun 13 04:15:09 UTC 201351faf0c40beaa004fda92a7cabce6094 root@r-11-VM:~# dhcp_release version : root@r-11-VM:~# which dhcp_release /usr/bin/dhcp_release root@r-11-VM:~# root@r-11-VM:~# ls -lrth /usr/bin/dhcp_release -rwxr-xr-x 1 root root 9.5K Feb 13 02:56 /usr/bin/dhcp_release root@r-11-VM:~# root@r-11-VM:~# md5sum /usr/bin/dhcp_release 5d68314ce7084a2036e8d2d204e764cb /usr/bin/dhcp_release root@r-11-VM:~# Please help
[jira] [Closed] (CLOUDSTACK-3863) [Image Store] NoTransitionException: Unable to transition to a new state from Ready via CreateOnlyRequested
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-3863. [Image Store] NoTransitionException: Unable to transition to a new state from Ready via CreateOnlyRequested Key: CLOUDSTACK-3863 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3863 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Storage Controller Affects Versions: 4.2.0 Environment: cloudstack over vmware esxi 5.0 servers Reporter: Sateesh Chodapuneedi Assignee: Sateesh Chodapuneedi Priority: Critical Fix For: 4.2.0 1) Deploy advanced zone over VMware esxi 5.0 servers. 2) Deploy VM with 1 data disk 3) Take snapshot of data disk 4) Try to download volume from snapshot created in above step-3. Seeing following state transition Exception and failing. I confirm that download of volume to secondary storage is success as I could see the download volume in correct path of the secondary storage. So success event processing went bad. ERROR [storage.volume.VolumeServiceImpl] (Job-Executor-2:job-40 = [ 8b85d927-77bb-4172-a7f1-b62c22823e1c ]) failed to copy volume to image store com.cloud.utils.exception.CloudRuntimeException: Failed to update state:com.cloud.utils.fsm.NoTransitionException: Unable to transition to a new state from Ready via CreateOnlyRequested at org.apache.cloudstack.storage.volume.VolumeObject.processEventOnly(VolumeObject.java:308) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.copyVolumeFromPrimaryToImage(VolumeServiceImpl.java:703) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.copyVolume(VolumeServiceImpl.java:759) at com.cloud.storage.VolumeManagerImpl.extractVolume(VolumeManagerImpl.java:2812) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd.execute(ExtractVolumeCmd.java:130) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) 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:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) WARN [storage.datastore.ObjectInDataStoreManagerImpl] (Job-Executor-2:job-40 = [ 8b85d927-77bb-4172-a7f1-b62c22823e1c ]) Unsupported data object (VOLUME, org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@15bbd17) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3863) [Image Store] NoTransitionException: Unable to transition to a new state from Ready via CreateOnlyRequested
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741339#comment-13741339 ] Sudha Ponnaganti commented on CLOUDSTACK-3863: -- closing it as sateesh can not reproduce now [Image Store] NoTransitionException: Unable to transition to a new state from Ready via CreateOnlyRequested Key: CLOUDSTACK-3863 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3863 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Storage Controller Affects Versions: 4.2.0 Environment: cloudstack over vmware esxi 5.0 servers Reporter: Sateesh Chodapuneedi Assignee: Sateesh Chodapuneedi Priority: Critical Fix For: 4.2.0 1) Deploy advanced zone over VMware esxi 5.0 servers. 2) Deploy VM with 1 data disk 3) Take snapshot of data disk 4) Try to download volume from snapshot created in above step-3. Seeing following state transition Exception and failing. I confirm that download of volume to secondary storage is success as I could see the download volume in correct path of the secondary storage. So success event processing went bad. ERROR [storage.volume.VolumeServiceImpl] (Job-Executor-2:job-40 = [ 8b85d927-77bb-4172-a7f1-b62c22823e1c ]) failed to copy volume to image store com.cloud.utils.exception.CloudRuntimeException: Failed to update state:com.cloud.utils.fsm.NoTransitionException: Unable to transition to a new state from Ready via CreateOnlyRequested at org.apache.cloudstack.storage.volume.VolumeObject.processEventOnly(VolumeObject.java:308) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.copyVolumeFromPrimaryToImage(VolumeServiceImpl.java:703) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.copyVolume(VolumeServiceImpl.java:759) at com.cloud.storage.VolumeManagerImpl.extractVolume(VolumeManagerImpl.java:2812) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd.execute(ExtractVolumeCmd.java:130) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) 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:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) WARN [storage.datastore.ObjectInDataStoreManagerImpl] (Job-Executor-2:job-40 = [ 8b85d927-77bb-4172-a7f1-b62c22823e1c ]) Unsupported data object (VOLUME, org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@15bbd17) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-4202) [IPv4][dnsmasq] VM not able get ip from dhcp which is previously assigned to vm
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741336#comment-13741336 ] Sudha Ponnaganti commented on CLOUDSTACK-4202: -- closing it as jayapal mentioned not repro - pl reopen if you still see it [IPv4][dnsmasq] VM not able get ip from dhcp which is previously assigned to vm Key: CLOUDSTACK-4202 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4202 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller, Virtual Router Affects Versions: 4.2.0 Environment: CentOS 6.3 64bit for KVM Host. Reporter: Naoki Sakamoto Assignee: Jayapal Reddy Priority: Critical Fix For: 4.2.0 Original Estimate: 168h Remaining Estimate: 168h Related : CLOUDSTACK-3533 [IPv6][dnsmasq] VM not able get ip from dhcp which is previously assigned to vm IPv4 has same issue. 1. Create VPC (Super CIDR = 10.0.0.0/16) 2. Create Tier (CIDR = 10.0.0.0/30, GW = 10.0.0.1, Netmask = 255.255.255.252) 3. Deploy VM01 (IP = 10.0.0.2) 4. Destroy VM01 5. Deploy VM02 (IP = 10.0.0.2) VM02 Guest OS is not getting IP Address. I confirmed in bigger range Tier (CIDR = 10.0.0.0/27, Netmask = 255.255.255.224) about 30 VMs and same issue occurred. New VM can't get IP that is exhousted and released. On Virtual Router /var/log/dnsmasq.log Aug 8 08:53:16 dnsmasq[13590]: read /etc/hosts - 6 addresses Aug 8 08:53:16 dnsmasq-dhcp[13590]: read /etc/dhcphosts.txt Aug 8 08:53:16 dnsmasq-dhcp[13590]: read /etc/dhcpopts.txt Aug 8 08:54:27 dnsmasq-dhcp[13590]: not using configured address 10.0.0.2 because it is leased to 02:00:68:25:00:07 Aug 8 08:54:27 dnsmasq-dhcp[13590]: DHCPDISCOVER(eth2) 10.0.2.15 02:00:5d:19:00:09 no address available Aug 8 08:54:31 dnsmasq-dhcp[13590]: not using configured address 10.0.0.2 because it is leased to 02:00:68:25:00:07 Aug 8 08:54:31 dnsmasq-dhcp[13590]: DHCPDISCOVER(eth2) 10.0.2.15 02:00:5d:19:00:09 no address available Aug 8 08:54:41 dnsmasq-dhcp[13590]: not using configured address 10.0.0.2 because it is leased to 02:00:68:25:00:07 Aug 8 08:54:41 dnsmasq-dhcp[13590]: DHCPDISCOVER(eth2) 10.0.2.15 02:00:5d:19:00:09 no address available Aug 8 08:55:02 dnsmasq-dhcp[13590]: not using configured address 10.0.0.2 because it is leased to 02:00:68:25:00:07 Aug 8 08:55:02 dnsmasq-dhcp[13590]: DHCPDISCOVER(eth2) 10.0.2.15 02:00:5d:19:00:09 no address available Aug 8 08:55:21 dnsmasq-dhcp[13590]: not using configured address 10.0.0.2 because it is leased to 02:00:68:25:00:07 Aug 8 08:55:21 dnsmasq-dhcp[13590]: DHCPDISCOVER(eth2) 10.0.2.15 02:00:5d:19:00:09 no address available 02:00:68:25:00:07 is VM01's Mac Address. On Virtual Router /var/log/messages (on issue time) Aug 8 08:53:01 r-11-VM cloud: Password server failed with error code 1. Restarting socat... Aug 8 08:53:04 r-11-VM cloud: Password server failed with error code 1. Restarting socat... Aug 8 08:53:07 r-11-VM cloud: Password server failed with error code 1. Restarting socat... Aug 8 08:53:10 r-11-VM cloud: Password server failed with error code 1. Restarting socat... Aug 8 08:53:13 r-11-VM cloud: Password server failed with error code 1. Restarting socat... Aug 8 08:53:16 r-11-VM cloud: edithosts: releasing 10.0.0.2 Aug 8 08:53:16 r-11-VM cloud: edithosts: released 10.0.0.2 Aug 8 08:53:16 r-11-VM cloud: edithosts: update 02:00:5d:19:00:09 10.0.0.2 sakamoto035 to hosts Aug 8 08:53:16 r-11-VM cloud: Password server failed with error code 1. Restarting socat... Aug 8 08:53:19 r-11-VM cloud: Password server failed with error code 1. Restarting socat... Aug 8 08:53:22 r-11-VM cloud: Password server failed with error code 1. Restarting socat... Aug 8 08:53:25 r-11-VM cloud: Password server failed with error code 1. Restarting socat... Aug 8 08:53:28 r-11-VM cloud: Password server failed with error code 1. Restarting socat... I found edithosts: releasing 10.0.0.2 and edithosts: released 10.0.0.2. Then I think no_dhcp_release = 0 in edithosts.sh at that time. I used latest edithosts.sh. I could recover as following. 1. On Virtual Router # service dnsmasq restart 2. Restart VM02 by GUI. VM02 got IP Address 10.0.0.2. System template version : root@r-11-VM:~# sh /opt/cloud/bin/get_template_version.sh Cloudstack Release 4.2.0 Thu Jun 13 04:15:09 UTC 201351faf0c40beaa004fda92a7cabce6094 root@r-11-VM:~# dhcp_release version : root@r-11-VM:~# which dhcp_release /usr/bin/dhcp_release root@r-11-VM:~# root@r-11-VM:~# ls -lrth /usr/bin/dhcp_release -rwxr-xr-x 1 root root 9.5K Feb 13 02:56 /usr/bin/dhcp_release
[jira] [Commented] (CLOUDSTACK-4202) [IPv4][dnsmasq] VM not able get ip from dhcp which is previously assigned to vm
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741336#comment-13741336 ] Sudha Ponnaganti commented on CLOUDSTACK-4202: -- closing it as jayapal mentioned not repro - pl reopen if you still see it [IPv4][dnsmasq] VM not able get ip from dhcp which is previously assigned to vm Key: CLOUDSTACK-4202 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4202 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller, Virtual Router Affects Versions: 4.2.0 Environment: CentOS 6.3 64bit for KVM Host. Reporter: Naoki Sakamoto Assignee: Jayapal Reddy Priority: Critical Fix For: 4.2.0 Original Estimate: 168h Remaining Estimate: 168h Related : CLOUDSTACK-3533 [IPv6][dnsmasq] VM not able get ip from dhcp which is previously assigned to vm IPv4 has same issue. 1. Create VPC (Super CIDR = 10.0.0.0/16) 2. Create Tier (CIDR = 10.0.0.0/30, GW = 10.0.0.1, Netmask = 255.255.255.252) 3. Deploy VM01 (IP = 10.0.0.2) 4. Destroy VM01 5. Deploy VM02 (IP = 10.0.0.2) VM02 Guest OS is not getting IP Address. I confirmed in bigger range Tier (CIDR = 10.0.0.0/27, Netmask = 255.255.255.224) about 30 VMs and same issue occurred. New VM can't get IP that is exhousted and released. On Virtual Router /var/log/dnsmasq.log Aug 8 08:53:16 dnsmasq[13590]: read /etc/hosts - 6 addresses Aug 8 08:53:16 dnsmasq-dhcp[13590]: read /etc/dhcphosts.txt Aug 8 08:53:16 dnsmasq-dhcp[13590]: read /etc/dhcpopts.txt Aug 8 08:54:27 dnsmasq-dhcp[13590]: not using configured address 10.0.0.2 because it is leased to 02:00:68:25:00:07 Aug 8 08:54:27 dnsmasq-dhcp[13590]: DHCPDISCOVER(eth2) 10.0.2.15 02:00:5d:19:00:09 no address available Aug 8 08:54:31 dnsmasq-dhcp[13590]: not using configured address 10.0.0.2 because it is leased to 02:00:68:25:00:07 Aug 8 08:54:31 dnsmasq-dhcp[13590]: DHCPDISCOVER(eth2) 10.0.2.15 02:00:5d:19:00:09 no address available Aug 8 08:54:41 dnsmasq-dhcp[13590]: not using configured address 10.0.0.2 because it is leased to 02:00:68:25:00:07 Aug 8 08:54:41 dnsmasq-dhcp[13590]: DHCPDISCOVER(eth2) 10.0.2.15 02:00:5d:19:00:09 no address available Aug 8 08:55:02 dnsmasq-dhcp[13590]: not using configured address 10.0.0.2 because it is leased to 02:00:68:25:00:07 Aug 8 08:55:02 dnsmasq-dhcp[13590]: DHCPDISCOVER(eth2) 10.0.2.15 02:00:5d:19:00:09 no address available Aug 8 08:55:21 dnsmasq-dhcp[13590]: not using configured address 10.0.0.2 because it is leased to 02:00:68:25:00:07 Aug 8 08:55:21 dnsmasq-dhcp[13590]: DHCPDISCOVER(eth2) 10.0.2.15 02:00:5d:19:00:09 no address available 02:00:68:25:00:07 is VM01's Mac Address. On Virtual Router /var/log/messages (on issue time) Aug 8 08:53:01 r-11-VM cloud: Password server failed with error code 1. Restarting socat... Aug 8 08:53:04 r-11-VM cloud: Password server failed with error code 1. Restarting socat... Aug 8 08:53:07 r-11-VM cloud: Password server failed with error code 1. Restarting socat... Aug 8 08:53:10 r-11-VM cloud: Password server failed with error code 1. Restarting socat... Aug 8 08:53:13 r-11-VM cloud: Password server failed with error code 1. Restarting socat... Aug 8 08:53:16 r-11-VM cloud: edithosts: releasing 10.0.0.2 Aug 8 08:53:16 r-11-VM cloud: edithosts: released 10.0.0.2 Aug 8 08:53:16 r-11-VM cloud: edithosts: update 02:00:5d:19:00:09 10.0.0.2 sakamoto035 to hosts Aug 8 08:53:16 r-11-VM cloud: Password server failed with error code 1. Restarting socat... Aug 8 08:53:19 r-11-VM cloud: Password server failed with error code 1. Restarting socat... Aug 8 08:53:22 r-11-VM cloud: Password server failed with error code 1. Restarting socat... Aug 8 08:53:25 r-11-VM cloud: Password server failed with error code 1. Restarting socat... Aug 8 08:53:28 r-11-VM cloud: Password server failed with error code 1. Restarting socat... I found edithosts: releasing 10.0.0.2 and edithosts: released 10.0.0.2. Then I think no_dhcp_release = 0 in edithosts.sh at that time. I used latest edithosts.sh. I could recover as following. 1. On Virtual Router # service dnsmasq restart 2. Restart VM02 by GUI. VM02 got IP Address 10.0.0.2. System template version : root@r-11-VM:~# sh /opt/cloud/bin/get_template_version.sh Cloudstack Release 4.2.0 Thu Jun 13 04:15:09 UTC 201351faf0c40beaa004fda92a7cabce6094 root@r-11-VM:~# dhcp_release version : root@r-11-VM:~# which dhcp_release /usr/bin/dhcp_release root@r-11-VM:~# root@r-11-VM:~# ls -lrth /usr/bin/dhcp_release -rwxr-xr-x 1 root root 9.5K Feb 13 02:56 /usr/bin/dhcp_release
[jira] [Commented] (CLOUDSTACK-2059) Support remove network over VMware deployments with dvSwitch
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741340#comment-13741340 ] Sudha Ponnaganti commented on CLOUDSTACK-2059: -- closing as sateesh confirms that it is not an issue anymore Support remove network over VMware deployments with dvSwitch Key: CLOUDSTACK-2059 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2059 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Sateesh Chodapuneedi Assignee: Sateesh Chodapuneedi Priority: Critical Fix For: 4.2.0 Remove network from user VM is supported in VMware only for standard vSwitches. This need to be supported for dvSwitches as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-2059) Support remove network over VMware deployments with dvSwitch
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-2059. Support remove network over VMware deployments with dvSwitch Key: CLOUDSTACK-2059 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2059 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Sateesh Chodapuneedi Assignee: Sateesh Chodapuneedi Priority: Critical Fix For: 4.2.0 Remove network from user VM is supported in VMware only for standard vSwitches. This need to be supported for dvSwitches as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-4113) [Upgrade][3.0.7 to 4.2][AWS Style Health Checks]Health check policies are not getting created on an upgraded setup
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sudha Ponnaganti updated CLOUDSTACK-4113:
-
Assignee: Jessica Tomechak (was: Rajesh Battala)
[Upgrade][3.0.7 to 4.2][AWS Style Health Checks]Health check policies are not
getting created on an upgraded setup
--
Key: CLOUDSTACK-4113
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4113
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Doc, Upgrade
Affects Versions: 4.2.0
Environment: Upgraded from 3.0.7 to 4.2
NS : NetScaler NS9.3: Build 63.4.nc, Date: Jul 3 2013, 14:57:34
Reporter: Abhinav Roy
Assignee: Jessica Tomechak
Priority: Blocker
Fix For: 4.2.0
Attachments: CS4113.zip
Steps :
==
1. Create an advanced zone setup with Cs 3.0.7
2. Add NS device, NetScaler NS9.3: Build 63.4.nc, Date: Jul 3 2013, 14:57:34.
3. do some configurations on the setup
4. Upgrade to 4.2
5. Create a NS lb rule, attach VMs and then try to create a health check
policy for that LB rule
Expected behaviour :
=
The health check policy should be successfully created.
Observed behaviour :
The creation of health check policy fails with
(DirectAgent-113:null) Seq 5-2026438658: Processing: { Ans: , MgmtId:
7067804893289, via: 5, Ver: v1, Flags: 10,
[{com.cloud.agent.api.UnsupportedAnswer:{result:false,details:Unsupported
command issued:com.cloud.agent.api.CleanupNetworkRulesCmd. Are you sure you
got the right type of server?,wait:0}}] }
2013-08-06 22:10:24,348 DEBUG [network.resource.NetscalerResource]
(DirectAgent-209:null) Trying to bind the monitor :Cloud-Hc-10.147.47.5-22
to the service :Cloud-Service-10.0.49.39-22
2013-08-06 22:10:24,400 ERROR [network.resource.NetscalerResource]
(DirectAgent-209:null) Failed to execute LoadBalancerConfigCommand due to
com.cloud.utils.exception.ExecutionException: Failed to create new monitor
:Cloud-Hc-10.147.47.5-22 due to Invalid argument [monitor_name]
at
com.cloud.network.resource.NetscalerResource.bindServiceToMonitor(NetscalerResource.java:2447)
at
com.cloud.network.resource.NetscalerResource.execute(NetscalerResource.java:585)
at
com.cloud.network.resource.NetscalerResource.executeRequest(NetscalerResource.java:351)
at
com.cloud.network.resource.NetscalerResource.retry(NetscalerResource.java:3227)
at
com.cloud.network.resource.NetscalerResource.execute(NetscalerResource.java:692)
at
com.cloud.network.resource.NetscalerResource.executeRequest(NetscalerResource.java:351)
at
com.cloud.network.resource.NetscalerResource.retry(NetscalerResource.java:3227)
at
com.cloud.network.resource.NetscalerResource.execute(NetscalerResource.java:692)
at
com.cloud.network.resource.NetscalerResource.executeRequest(NetscalerResource.java:351)
at
com.cloud.network.resource.NetscalerResource.executeRequest(NetscalerResource.java:340)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
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.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
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:679)
2013-08-06 22:10:24,442 DEBUG [agent.transport.Request] (Timer-9:null) Seq
12-602996868: Sending { Cmd , MgmtId: 7067804893289, via: 12, Ver: v1,
Flags: 100011,
[{org.apache.cloudstack.storage.command.DownloadProgressCommand:{jobId:a6f1fe56-3f34-4669-a024-7fec6bc7f56e,request:GET_STATUS,hvm:true,description:Win8Serv,maxDownloadSizeInBytes:53687091200,id:210,resourceType:TEMPLATE,installPath:template/tmpl/1/210,_store:{com.cloud.agent.api.to.NfsTO:{_url:nfs://10.147.28.7/export/home/manasa/secondaryxen,_role:Image}},url:http://10.147.28.7/templates/Windows2012/WindowsServer2012.vhd,format:VHD,accountId:1,name:210-1-cdcf9608-7e70-3e2b-b73f-a39c1921ae79,secUrl:nfs://10.147.28.7/export/home/manasa/secondaryxen,wait:0}}]
}
2013-08-06
[jira] [Reopened] (CLOUDSTACK-4113) [Upgrade][3.0.7 to 4.2][AWS Style Health Checks]Health check policies are not getting created on an upgraded setup
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sudha Ponnaganti reopened CLOUDSTACK-4113:
--
Reopening and assigning to Doc team
[Upgrade][3.0.7 to 4.2][AWS Style Health Checks]Health check policies are not
getting created on an upgraded setup
--
Key: CLOUDSTACK-4113
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4113
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Doc, Upgrade
Affects Versions: 4.2.0
Environment: Upgraded from 3.0.7 to 4.2
NS : NetScaler NS9.3: Build 63.4.nc, Date: Jul 3 2013, 14:57:34
Reporter: Abhinav Roy
Assignee: Rajesh Battala
Priority: Blocker
Fix For: 4.2.0
Attachments: CS4113.zip
Steps :
==
1. Create an advanced zone setup with Cs 3.0.7
2. Add NS device, NetScaler NS9.3: Build 63.4.nc, Date: Jul 3 2013, 14:57:34.
3. do some configurations on the setup
4. Upgrade to 4.2
5. Create a NS lb rule, attach VMs and then try to create a health check
policy for that LB rule
Expected behaviour :
=
The health check policy should be successfully created.
Observed behaviour :
The creation of health check policy fails with
(DirectAgent-113:null) Seq 5-2026438658: Processing: { Ans: , MgmtId:
7067804893289, via: 5, Ver: v1, Flags: 10,
[{com.cloud.agent.api.UnsupportedAnswer:{result:false,details:Unsupported
command issued:com.cloud.agent.api.CleanupNetworkRulesCmd. Are you sure you
got the right type of server?,wait:0}}] }
2013-08-06 22:10:24,348 DEBUG [network.resource.NetscalerResource]
(DirectAgent-209:null) Trying to bind the monitor :Cloud-Hc-10.147.47.5-22
to the service :Cloud-Service-10.0.49.39-22
2013-08-06 22:10:24,400 ERROR [network.resource.NetscalerResource]
(DirectAgent-209:null) Failed to execute LoadBalancerConfigCommand due to
com.cloud.utils.exception.ExecutionException: Failed to create new monitor
:Cloud-Hc-10.147.47.5-22 due to Invalid argument [monitor_name]
at
com.cloud.network.resource.NetscalerResource.bindServiceToMonitor(NetscalerResource.java:2447)
at
com.cloud.network.resource.NetscalerResource.execute(NetscalerResource.java:585)
at
com.cloud.network.resource.NetscalerResource.executeRequest(NetscalerResource.java:351)
at
com.cloud.network.resource.NetscalerResource.retry(NetscalerResource.java:3227)
at
com.cloud.network.resource.NetscalerResource.execute(NetscalerResource.java:692)
at
com.cloud.network.resource.NetscalerResource.executeRequest(NetscalerResource.java:351)
at
com.cloud.network.resource.NetscalerResource.retry(NetscalerResource.java:3227)
at
com.cloud.network.resource.NetscalerResource.execute(NetscalerResource.java:692)
at
com.cloud.network.resource.NetscalerResource.executeRequest(NetscalerResource.java:351)
at
com.cloud.network.resource.NetscalerResource.executeRequest(NetscalerResource.java:340)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
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.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
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:679)
2013-08-06 22:10:24,442 DEBUG [agent.transport.Request] (Timer-9:null) Seq
12-602996868: Sending { Cmd , MgmtId: 7067804893289, via: 12, Ver: v1,
Flags: 100011,
[{org.apache.cloudstack.storage.command.DownloadProgressCommand:{jobId:a6f1fe56-3f34-4669-a024-7fec6bc7f56e,request:GET_STATUS,hvm:true,description:Win8Serv,maxDownloadSizeInBytes:53687091200,id:210,resourceType:TEMPLATE,installPath:template/tmpl/1/210,_store:{com.cloud.agent.api.to.NfsTO:{_url:nfs://10.147.28.7/export/home/manasa/secondaryxen,_role:Image}},url:http://10.147.28.7/templates/Windows2012/WindowsServer2012.vhd,format:VHD,accountId:1,name:210-1-cdcf9608-7e70-3e2b-b73f-a39c1921ae79,secUrl:nfs://10.147.28.7/export/home/manasa/secondaryxen,wait:0}}]
}
2013-08-06
[jira] [Commented] (CLOUDSTACK-4056) System VMs are connected to untagged Management Port Group on ESX when a Tagged Management Port Group is created
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741382#comment-13741382 ] Sudha Ponnaganti commented on CLOUDSTACK-4056: -- closing this as invalid - if there are concerns pl reopen System VMs are connected to untagged Management Port Group on ESX when a Tagged Management Port Group is created Key: CLOUDSTACK-4056 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4056 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, VMware Affects Versions: 4.2.0 Reporter: Ahmad Emneina Assignee: Anthony Xu Priority: Critical Fix For: 4.2.0 Management Network Port group is VLAN tagged on vSwitch0. After creating an advanced Zone and enabling it CloudStack created 2 private port-groups on vSwitch0 (management vSwitch), one tagged with correct VLAN (same VLAN ID as the management network port group) and one untagged private port group without any VLAN ID..but for some reason system VM private NICs are connected to the untagged port group, which fails connect to CloudStack and the setup was staled (until we manually added the VLAN ID to the port group, which was removed later somehow). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-4056) System VMs are connected to untagged Management Port Group on ESX when a Tagged Management Port Group is created
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-4056. System VMs are connected to untagged Management Port Group on ESX when a Tagged Management Port Group is created Key: CLOUDSTACK-4056 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4056 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, VMware Affects Versions: 4.2.0 Reporter: Ahmad Emneina Assignee: Anthony Xu Priority: Critical Fix For: 4.2.0 Management Network Port group is VLAN tagged on vSwitch0. After creating an advanced Zone and enabling it CloudStack created 2 private port-groups on vSwitch0 (management vSwitch), one tagged with correct VLAN (same VLAN ID as the management network port group) and one untagged private port group without any VLAN ID..but for some reason system VM private NICs are connected to the untagged port group, which fails connect to CloudStack and the setup was staled (until we manually added the VLAN ID to the port group, which was removed later somehow). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-709) The public option should be checked when adding a zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-709. --- Closing as it is addressed in 4.2 The public option should be checked when adding a zone -- Key: CLOUDSTACK-709 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-709 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Environment: master branch browser : Chrome(v23.0.1271.97 m), Safari(v6.0.2), IE8 Reporter: Isaac Chiang Assignee: Pranav Saxena Priority: Minor Fix For: 4.2.0 The public option should be checked initially when adding a zone. This issue doesn't happen when using Firefox. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3956) vm password not set correctly with password enable template
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741398#comment-13741398 ] Sudha Ponnaganti commented on CLOUDSTACK-3956: -- Closing it as incorrect template is used vm password not set correctly with password enable template --- Key: CLOUDSTACK-3956 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3956 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Jayapal Reddy Assignee: Sheng Yang Priority: Critical Fix For: 4.2.0 1. Deploy user vm with with password enabled template. 2. Template has cloud-set-guest-password script in it. 3. observed that user vm is not able to log in with the cloudstack generated password. More observations: 1. When created 8 vms created parallelly some of the vms set password correctly some of them not. In this case rebooting vm set password correctly and logged in. 2. After the above test tried by deploy vm one after other. In this case also this issue is seen. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-2066) ssvm agent start failed on the xenserver
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-2066. ssvm agent start failed on the xenserver Key: CLOUDSTACK-2066 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2066 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Storage Controller Affects Versions: 4.1.0 Reporter: Jayapal Reddy Priority: Blocker Fix For: 4.2.0 In xenserver ssvm observed the the following. 1. ssvm came up but the templates are not downloaded. So run the ssvm-check.sh 2. host values is set to localhost instead of MS ip. I corrected it in the cmdline file in the ssvm. 3. After this ssvm-check.sh got failed due to ssvm agent is not running. 4. observed the below log in cloud.out 20:49:57,730 ERROR AgentShell:610 - Unable to start agent: Resource class not fo und: org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource due to: java.lang.ClassNotFoundException: org.apache.cloudstack.storage.resource.NfsSeco ndaryStorageResource -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-2055) [UI] Need tooltips for new overcommit fields in Add Cluster dialog
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-2055. [UI] Need tooltips for new overcommit fields in Add Cluster dialog -- Key: CLOUDSTACK-2055 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2055 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc, UI Affects Versions: 4.2.0 Reporter: Jessica Tomechak Assignee: Harikrishna Patnala Fix For: 4.2.0 Two fields have been added to the Add Cluster dialog (Infrastructure - Clusters, View All - Add Cluster). They don't have tooltip text, as the other fields in the dialog do. The fields and suggested text are: CPU overcommit ratio: Multiplier by which to increase the calculated CPU capacity for each host. 1 = no over-provisioning. RAM overcommit ratio: Multiplier by which to increase the calculated memory capacity for each host. 1 = no over-provisioning. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-3956) vm password not set correctly with password enable template
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-3956. vm password not set correctly with password enable template --- Key: CLOUDSTACK-3956 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3956 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Jayapal Reddy Assignee: Sheng Yang Priority: Critical Fix For: 4.2.0 1. Deploy user vm with with password enabled template. 2. Template has cloud-set-guest-password script in it. 3. observed that user vm is not able to log in with the cloudstack generated password. More observations: 1. When created 8 vms created parallelly some of the vms set password correctly some of them not. In this case rebooting vm set password correctly and logged in. 2. After the above test tried by deploy vm one after other. In this case also this issue is seen. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2066) ssvm agent start failed on the xenserver
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741399#comment-13741399 ] Sudha Ponnaganti commented on CLOUDSTACK-2066: -- REsolved - so closing this ssvm agent start failed on the xenserver Key: CLOUDSTACK-2066 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2066 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Storage Controller Affects Versions: 4.1.0 Reporter: Jayapal Reddy Priority: Blocker Fix For: 4.2.0 In xenserver ssvm observed the the following. 1. ssvm came up but the templates are not downloaded. So run the ssvm-check.sh 2. host values is set to localhost instead of MS ip. I corrected it in the cmdline file in the ssvm. 3. After this ssvm-check.sh got failed due to ssvm agent is not running. 4. observed the below log in cloud.out 20:49:57,730 ERROR AgentShell:610 - Unable to start agent: Resource class not fo und: org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource due to: java.lang.ClassNotFoundException: org.apache.cloudstack.storage.resource.NfsSeco ndaryStorageResource -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2055) [UI] Need tooltips for new overcommit fields in Add Cluster dialog
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741401#comment-13741401 ] Sudha Ponnaganti commented on CLOUDSTACK-2055: -- Other defects addressed removal of fields so closing this. [UI] Need tooltips for new overcommit fields in Add Cluster dialog -- Key: CLOUDSTACK-2055 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2055 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc, UI Affects Versions: 4.2.0 Reporter: Jessica Tomechak Assignee: Harikrishna Patnala Fix For: 4.2.0 Two fields have been added to the Add Cluster dialog (Infrastructure - Clusters, View All - Add Cluster). They don't have tooltip text, as the other fields in the dialog do. The fields and suggested text are: CPU overcommit ratio: Multiplier by which to increase the calculated CPU capacity for each host. 1 = no over-provisioning. RAM overcommit ratio: Multiplier by which to increase the calculated memory capacity for each host. 1 = no over-provisioning. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3630) [Storage]No option for migration of local data volume.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-3630: - Priority: Critical (was: Major) [Storage]No option for migration of local data volume. -- Key: CLOUDSTACK-3630 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3630 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Storage Controller Affects Versions: 4.2.0 Environment: latest 4.2 build Reporter: manasaveloori Assignee: Devdeep Singh Priority: Critical Fix For: 4.2.0 Attachments: storage.jpg Steps: 1.Have a CS with advanced zone with VMware hypervisor.. 2.Have 1 local and 1 cluster wide primary storages. 3.Create a Data disk using local primary storage. Observed that there is no option to migrate the created local data disk. Attached the screen shot for the same. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-1144) s\/etc\/cloud/\/etc\/cloudstack/g
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-1144. confirmed that this is not an issue so closing s\/etc\/cloud/\/etc\/cloudstack/g -- Key: CLOUDSTACK-1144 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1144 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.1.0 Reporter: David Nalley Assignee: Pradeep Soundararajan Fix For: 4.2.0 /etc/cloud is hardcoded in a number of places, which is problematic as we change package names from cloud-* to cloudstack-* to reflect the package name. (or even a variable, which would be better) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3956) vm password not set correctly with password enable template
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741398#comment-13741398 ] Sudha Ponnaganti commented on CLOUDSTACK-3956: -- Closing it as incorrect template is used vm password not set correctly with password enable template --- Key: CLOUDSTACK-3956 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3956 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Jayapal Reddy Assignee: Sheng Yang Priority: Critical Fix For: 4.2.0 1. Deploy user vm with with password enabled template. 2. Template has cloud-set-guest-password script in it. 3. observed that user vm is not able to log in with the cloudstack generated password. More observations: 1. When created 8 vms created parallelly some of the vms set password correctly some of them not. In this case rebooting vm set password correctly and logged in. 2. After the above test tried by deploy vm one after other. In this case also this issue is seen. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-4226) [Automation] copy template/iso is failing
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741406#comment-13741406
]
Sudha Ponnaganti commented on CLOUDSTACK-4226:
--
1337 has been closed without originator's approval as release has been out.
Talluri - pl review this again if you do not agree wiht the assessment
[Automation] copy template/iso is failing
-
Key: CLOUDSTACK-4226
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4226
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: ISO, Template
Affects Versions: 4.2.0
Reporter: Srikanteswararao Talluri
Assignee: Nitin Mehta
Priority: Blocker
Fix For: 4.2.0
Copy template/iso is failing with HTTP Server returned 403 (expected 200 OK)
===START=== 10.101.255.7 -- GET
command=copyTemplateid=0e0a2038-6e7b-475f-b535-af5587df6c40sourcezoneid=b2620b12-5480-4567-858b-fadaca64f71adestzoneid=78abc627-2d24-4c36-ae55-7711c6456e17response=jsonsessionkey=h6oyyTiqF%2Fzy%2BEY8Z55vGXY16YE%3D_=1376106139819
2013-08-09 20:30:26,342 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-11:null) submit async job-153 = [
5be875c8-6564-46b2-a073-e86e184b510b ], details: AsyncJobVO {id:153, userId:
2, accountId: 2, sessionKey: null, instanceType: Template, instanceId: 208,
cmd: org.apache.cloudstack.api.command.user.template.CopyTemplateCmd,
cmdOriginator: null, cmdInfo:
{response:json,id:0e0a2038-6e7b-475f-b535-af5587df6c40,sessionkey:h6oyyTiqF/zy+EY8Z55vGXY16YE\u003d,destzoneid:78abc627-2d24-4c36-ae55-7711c6456e17,cmdEventType:TEMPLATE.COPY,ctxUserId:2,httpmethod:GET,_:1376106139819,ctxAccountId:2,sourcezoneid:b2620b12-5480-4567-858b-fadaca64f71a,ctxStartEventId:668},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 112957957439171,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-08-09 20:30:26,344 DEBUG [cloud.api.ApiServlet] (catalina-exec-11:null)
===END=== 10.101.255.7 -- GET
command=copyTemplateid=0e0a2038-6e7b-475f-b535-af5587df6c40sourcezoneid=b2620b12-5480-4567-858b-fadaca64f71adestzoneid=78abc627-2d24-4c36-ae55-7711c6456e17response=jsonsessionkey=h6oyyTiqF%2Fzy%2BEY8Z55vGXY16YE%3D_=1376106139819
2013-08-09 20:30:26,345 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-139:job-153 = [ 5be875c8-6564-46b2-a073-e86e184b510b ])
Executing org.apache.cloudstack.api.command.user.template.CopyTemplateCmd for
job-153 = [ 5be875c8-6564-46b2-a073-e86e184b510b ]
2013-08-09 20:30:26,381 DEBUG [storage.image.TemplateDataFactoryImpl]
(Job-Executor-139:job-153 = [ 5be875c8-6564-46b2-a073-e86e184b510b ])
template 208 is already in store:1, type:Image
2013-08-09 20:30:26,387 DEBUG [storage.image.TemplateDataFactoryImpl]
(Job-Executor-139:job-153 = [ 5be875c8-6564-46b2-a073-e86e184b510b ])
template 208 is not in store:2, type:Image
2013-08-09 20:30:26,387 DEBUG [storage.image.TemplateServiceImpl]
(Job-Executor-139:job-153 = [ 5be875c8-6564-46b2-a073-e86e184b510b ]) Setting
source template url to
https://10-223-251-16.realhostip.com/copy/SecStorage/b9c3c370-1cb2-3bc0-8000-fa52aed0c0b2/template/tmpl/2/208/33e1050e-318d-349f-9590-78d163f778ad.vhd
2013-08-09 20:30:26,388 DEBUG [storage.image.TemplateServiceImpl]
(Job-Executor-139:job-153 = [ 5be875c8-6564-46b2-a073-e86e184b510b ]) Mark
template_store_ref entry as Creating
2013-08-09 20:30:26,413 DEBUG [storage.image.TemplateDataFactoryImpl]
(Job-Executor-139:job-153 = [ 5be875c8-6564-46b2-a073-e86e184b510b ])
template 208 is already in store:2, type:Image
2013-08-09 20:30:26,484 DEBUG [storage.image.TemplateServiceImpl]
(Job-Executor-139:job-153 = [ 5be875c8-6564-46b2-a073-e86e184b510b ]) Invoke
datastore driver createAsync to create template on destination store
2013-08-09 20:30:26,491 DEBUG [storage.image.BaseImageStoreDriverImpl]
(Job-Executor-139:job-153 = [ 5be875c8-6564-46b2-a073-e86e184b510b ])
Downloading template to data store 2
2013-08-09 20:30:26,498 DEBUG [storage.image.BaseImageStoreDriverImpl]
(Job-Executor-139:job-153 = [ 5be875c8-6564-46b2-a073-e86e184b510b ])
Performing image store createTemplate async callback
2013-08-09 20:30:26,621 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-3:null) SeqA 7-1448: Processing Seq 7-1448: { Cmd ,
MgmtId: -1, via: 7, Ver: v1, Flags: 11,
[{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:3,_loadInfo:{\n
\connections\: []\n},wait:0}}] }
2013-08-09 20:30:26,834 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-3:null) SeqA 7-1448: Sending Seq 7-1448: { Ans: ,
MgmtId: 112957957439171, via:
[jira] [Reopened] (CLOUDSTACK-3630) [Storage]No option for migration of local data volume.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti reopened CLOUDSTACK-3630: -- Devdeep, manasa has updated ticket with more details. I am reopening this. Can you review this again [Storage]No option for migration of local data volume. -- Key: CLOUDSTACK-3630 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3630 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Storage Controller Affects Versions: 4.2.0 Environment: latest 4.2 build Reporter: manasaveloori Assignee: Devdeep Singh Priority: Critical Fix For: 4.2.0 Attachments: storage.jpg Steps: 1.Have a CS with advanced zone with VMware hypervisor.. 2.Have 1 local and 1 cluster wide primary storages. 3.Create a Data disk using local primary storage. Observed that there is no option to migrate the created local data disk. Attached the screen shot for the same. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-282) Virtual Routers do not properly resolve DNS SRV Records
[ https://issues.apache.org/jira/browse/CLOUDSTACK-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-282. --- closing this as duplicate Virtual Routers do not properly resolve DNS SRV Records --- Key: CLOUDSTACK-282 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-282 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: pre-4.0.0 Environment: Cloudstack 3.02 Management Server on Centos 6.2, Xenserver 6.02 Hosts Reporter: Nik Martin Priority: Minor Fix For: 4.2.0 When using SNAT Networking, I have a VM with a Static NAT IP Assinged in Cloudstack. The Centos 6.2 VM has dhcp defined as the network protocol, and gets a private network IP, and a Static NAT Public IP. /etc/resolv.conf on the guest VM gets written out by dhclient, and has one nameserver defined: 10.1.1.1, which is the virtual router for the guest network. If doing a DIG lookup of a SRV record in the form: # dig _sip._tcp.voipstack.net SRV ; DiG 9.8.2rc1-RedHat-9.8.2-0.10.rc1.el6_3.4 _sip._tcp.voipstack.net SRV ;; global options: +cmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 576 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;_sip._tcp.voipstack.net. IN SRV ;; Query time: 1 msec ;; SERVER: 10.1.1.1#53(10.1.1.1) ;; WHEN: Sun Oct 7 13:40:43 2012 ;; MSG SIZE rcvd: 41 Nothing is returned. If I manually edit /etc/resolv.conf, and add: nameserver 8.8.8.8, and do the same query, I get: # dig _sip._tcp.voipstack.net SRV ; DiG 9.8.2rc1-RedHat-9.8.2-0.10.rc1.el6_3.4 _sip._tcp.voipstack.net SRV ;; global options: +cmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 42375 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;_sip._tcp.voipstack.net. IN SRV ;; ANSWER SECTION: _sip._tcp.voipstack.net. 1606 IN SRV 1 9 5060 as2.voipstack.net. _sip._tcp.voipstack.net. 1606 IN SRV 0 9 5060 as1.voipstack.net. ;; Query time: 36 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Sun Oct 7 13:33:39 2012 ;; MSG SIZE rcvd: 115 The virtual router should resolve all valid DNS record types -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2140) Host is still marked as being in Up state when the host is shutdown (when there are no more hosts in the cluster)
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741410#comment-13741410
]
Sudha Ponnaganti commented on CLOUDSTACK-2140:
--
Two look different scenarios to me. So leaving them as is for review by
sangeetha
Host is still marked as being in Up state when the host is shutdown (when
there are no more hosts in the cluster)
---
Key: CLOUDSTACK-2140
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2140
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Affects Versions: 4.2.0
Environment: build from master
Reporter: Sangeetha Hariharan
Assignee: Koushik Das
Fix For: 4.2.0
Attachments: management-server.rar
Host is still marked as being in Up state when the host is shutdown (when
there are no more hosts in the cluster.
Set up:
Advanced zone.
3 hosts in a cluster ( in my case host id - 7 ,8 ,9 ).
I did not have any problems when host 8 and host 9 where shutdown.
When I tried to shutdown host 7 , I see the host still being in Up state ,
even after the management server detected that it is not able to connect with
this host.
Following exception seen in management server logs:
2013-04-22 14:48:18,350 DEBUG [xen.resource.XenServerConnectionPool]
(DirectAgent-350:null) localLogout has problem Failed to read server's
response: connect timed out
2013-04-22 14:48:18,350 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-350:null) Unable to stop i-3-45-VM due to
com.cloud.utils.exception.CloudRuntimeException: Unable to reset master of
slave 10.223.59.4 to 10.223.59.2 due to org.apache.xmlrpc.XmlRpcException:
Failed to read server's response: connect timed out
at
com.cloud.hypervisor.xen.resource.XenServerConnectionPool.PoolEmergencyResetMaster(XenServerConnectionPool.java:443)
at
com.cloud.hypervisor.xen.resource.XenServerConnectionPool.connect(XenServerConnectionPool.java:661)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.getConnection(CitrixResourceBase.java:5583)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:3728)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:474)
at
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
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.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
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:679)
2013-04-22 14:48:18,364 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-350:null) Seq 9-72160431: Response Received:
2013-04-22 14:48:18,370 DEBUG [agent.transport.Request]
(DirectAgent-350:null) Seq 9-72160431: Processing: { Ans: , MgmtId:
7508777239729, via: 9, Ver: v1, Flags: 110,
[{StopAnswer:{result:false,details:Exception:
com.cloud.utils.exception.CloudRuntimeException\nMessage: Unable to reset
master of slave 10.223.59.4 to 10.223.59.2 due to
org.apache.xmlrpc.XmlRpcException: Failed to read server's response: connect
timed out\nStack: com.cloud.utils.exception.CloudRuntimeException: Unable to
reset master of slave 10.223.59.4 to 10.223.59.2 due to
org.apache.xmlrpc.XmlRpcException: Failed to read server's response: connect
timed out\n\tat
com.cloud.hypervisor.xen.resource.XenServerConnectionPool.PoolEmergencyResetMaster(XenServerConnectionPool.java:443)\n\tat
com.cloud.hypervisor.xen.resource.XenServerConnectionPool.connect(XenServerConnectionPool.java:661)\n\tat
com.cloud.hypervisor.xen.resource.CitrixResourceBase.getConnection(CitrixResourceBase.java:5583)\n\tat
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:3728)\n\tat
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:474)\n\tat
[jira] [Closed] (CLOUDSTACK-1721) Unable to create local storage volumes
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-1721. Nik - pl reopen is you see this issue again. For now I am closing this as prachi couldn't reproduce it Unable to create local storage volumes -- Key: CLOUDSTACK-1721 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1721 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Nitin Mehta Assignee: Prachi Damle Priority: Blocker Fix For: 4.2.0 Attachments: vmops.log I chose a local enable comput offering and try deploy vm and its deploying on a shared storage instead mysql select * from vm_instance where id=10\G; *** 1. row *** id: 10 name: c991a65e-342b-4753-a31b-802201ac91c7 uuid: c991a65e-342b-4753-a31b-802201ac91c7 instance_name: i-2-10-VM state: Running vm_template_id: 202 guest_os_id: 142 private_mac_address: 02:00:58:9e:00:08 private_ip_address: 10.1.1.42 pod_id: 1 data_center_id: 1 host_id: 1 last_host_id: 1 proxy_id: NULL proxy_assign_time: NULL vnc_password: edc96004be21ae86 ha_enabled: 0 limit_cpu_use: 0 update_count: 3 update_time: 2013-03-19 07:10:47 created: 2013-03-19 07:10:26 removed: NULL type: User vm_type: User account_id: 2 domain_id: 1 service_offering_id: 17 reservation_id: b5da6244-7d0e-4a75-a4b9-62813f75547a hypervisor_type: XenServer disk_offering_id: NULL cpu: NULL ram: NULL owner: 2 speed: 256 host_name: c991a65e-342b-4753-a31b-802201ac91c7 display_name: NULL desired_state: NULL 1 row in set (0.00 sec) mysql select * from disk_offering where id=17; ++---++--+--+---+-+--+-+---+-+++-+-+--+ | id | domain_id | name | uuid | display_text | disk_size | type| tags | recreatable | use_local_storage | unique_name | system_use | customized | removed | created | sort_key | ++---++--+--+---+-+--+-+---+-+++-+-+--+ | 17 | NULL | local1 | 8e5f270e-6e13-4e1c-8548-fedb19805817 | local1 | 0 | Service | NULL | 0 | 1 | NULL | 0 | 1 | NULL| 2013-03-19 07:10:05 |0 | ++---++--+--+---+-+--+-+---+-+++-+-+--+ 1 row in set (0.00 sec) mysql select * from volumes where id=10\G; *** 1. row *** id: 10 account_id: 2 domain_id: 1 pool_id: 200 last_pool_id: NULL instance_id: 10 device_id: 0 name: ROOT-10 uuid: bd643ab0-ff3e-4df1-98b9-204c1c39df3a size: 21474836480 folder: /export/home/nitin/primary path: 549f2ec8-c278-4107-a2d9-2398ec5aa51b pod_id: 1 data_center_id: 1 iscsi_name: NULL host_ip: NULL volume_type: ROOT pool_type: NetworkFilesystem disk_offering_id: 17 template_id: 202 first_snapshot_backup_uuid: NULL recreatable: 0 created: 2013-03-19 07:10:26 attached: NULL updated: 2013-03-19 07:10:40 removed: NULL state: Ready chain_info: NULL update_count: 2 disk_type: NULL 1 row in set (0.00 sec) ERROR: No query specified mysql select * from storage_pool \G; *** 1. row *** id: 200 name: ps uuid:
[jira] [Closed] (CLOUDSTACK-1721) Unable to create local storage volumes
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-1721. Nik - pl reopen is you see this issue again. For now I am closing this as prachi couldn't reproduce it Unable to create local storage volumes -- Key: CLOUDSTACK-1721 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1721 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Nitin Mehta Assignee: Prachi Damle Priority: Blocker Fix For: 4.2.0 Attachments: vmops.log I chose a local enable comput offering and try deploy vm and its deploying on a shared storage instead mysql select * from vm_instance where id=10\G; *** 1. row *** id: 10 name: c991a65e-342b-4753-a31b-802201ac91c7 uuid: c991a65e-342b-4753-a31b-802201ac91c7 instance_name: i-2-10-VM state: Running vm_template_id: 202 guest_os_id: 142 private_mac_address: 02:00:58:9e:00:08 private_ip_address: 10.1.1.42 pod_id: 1 data_center_id: 1 host_id: 1 last_host_id: 1 proxy_id: NULL proxy_assign_time: NULL vnc_password: edc96004be21ae86 ha_enabled: 0 limit_cpu_use: 0 update_count: 3 update_time: 2013-03-19 07:10:47 created: 2013-03-19 07:10:26 removed: NULL type: User vm_type: User account_id: 2 domain_id: 1 service_offering_id: 17 reservation_id: b5da6244-7d0e-4a75-a4b9-62813f75547a hypervisor_type: XenServer disk_offering_id: NULL cpu: NULL ram: NULL owner: 2 speed: 256 host_name: c991a65e-342b-4753-a31b-802201ac91c7 display_name: NULL desired_state: NULL 1 row in set (0.00 sec) mysql select * from disk_offering where id=17; ++---++--+--+---+-+--+-+---+-+++-+-+--+ | id | domain_id | name | uuid | display_text | disk_size | type| tags | recreatable | use_local_storage | unique_name | system_use | customized | removed | created | sort_key | ++---++--+--+---+-+--+-+---+-+++-+-+--+ | 17 | NULL | local1 | 8e5f270e-6e13-4e1c-8548-fedb19805817 | local1 | 0 | Service | NULL | 0 | 1 | NULL | 0 | 1 | NULL| 2013-03-19 07:10:05 |0 | ++---++--+--+---+-+--+-+---+-+++-+-+--+ 1 row in set (0.00 sec) mysql select * from volumes where id=10\G; *** 1. row *** id: 10 account_id: 2 domain_id: 1 pool_id: 200 last_pool_id: NULL instance_id: 10 device_id: 0 name: ROOT-10 uuid: bd643ab0-ff3e-4df1-98b9-204c1c39df3a size: 21474836480 folder: /export/home/nitin/primary path: 549f2ec8-c278-4107-a2d9-2398ec5aa51b pod_id: 1 data_center_id: 1 iscsi_name: NULL host_ip: NULL volume_type: ROOT pool_type: NetworkFilesystem disk_offering_id: 17 template_id: 202 first_snapshot_backup_uuid: NULL recreatable: 0 created: 2013-03-19 07:10:26 attached: NULL updated: 2013-03-19 07:10:40 removed: NULL state: Ready chain_info: NULL update_count: 2 disk_type: NULL 1 row in set (0.00 sec) ERROR: No query specified mysql select * from storage_pool \G; *** 1. row *** id: 200 name: ps uuid:
[jira] [Reopened] (CLOUDSTACK-3721) updateCluster API: mark cpuovercommitratio and memoryovercommitratio as deprecated
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti reopened CLOUDSTACK-3721: -- Hari, These need to be removed otherwise these will break backward compatibility thanks /sudha updateCluster API: mark cpuovercommitratio and memoryovercommitratio as deprecated -- Key: CLOUDSTACK-3721 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3721 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Affects Versions: 4.2.0 Reporter: Alena Prokharchyk Assignee: Harikrishna Patnala Fix For: 4.2.0 As memoryovercommitratio and cpuovercommitratio are being set using updateConfiguration generic API starting from 4.2 release, they should be marked as deprecated in updateCluster command so the customers won't use it any more. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3721) updateCluster API: mark cpuovercommitratio and memoryovercommitratio as deprecated
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-3721: - Priority: Critical (was: Major) updateCluster API: mark cpuovercommitratio and memoryovercommitratio as deprecated -- Key: CLOUDSTACK-3721 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3721 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Affects Versions: 4.2.0 Reporter: Alena Prokharchyk Assignee: Harikrishna Patnala Priority: Critical Fix For: 4.2.0 As memoryovercommitratio and cpuovercommitratio are being set using updateConfiguration generic API starting from 4.2 release, they should be marked as deprecated in updateCluster command so the customers won't use it any more. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (CLOUDSTACK-3721) updateCluster API: mark cpuovercommitratio and memoryovercommitratio as deprecated
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741462#comment-13741462 ] Sudha Ponnaganti edited comment on CLOUDSTACK-3721 at 8/15/13 9:01 PM: --- Hari, These need to be marked as deprecated otherwise these will break backward compatibility thanks /sudha was (Author: sudhap): Hari, These need to be removed otherwise these will break backward compatibility thanks /sudha updateCluster API: mark cpuovercommitratio and memoryovercommitratio as deprecated -- Key: CLOUDSTACK-3721 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3721 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Affects Versions: 4.2.0 Reporter: Alena Prokharchyk Assignee: Harikrishna Patnala Fix For: 4.2.0 As memoryovercommitratio and cpuovercommitratio are being set using updateConfiguration generic API starting from 4.2 release, they should be marked as deprecated in updateCluster command so the customers won't use it any more. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-954) QA - support multiple VLANs for KVM HV
[ https://issues.apache.org/jira/browse/CLOUDSTACK-954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-954. --- QA - support multiple VLANs for KVM HV -- Key: CLOUDSTACK-954 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-954 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.1.0 Reporter: Sudha Ponnaganti Assignee: sadhu suresh Fix For: 4.2.0 core tasks that need to be done: - review requirements/FS - upload test plan/test cases - get test cases reviewed - add automation - upload test results - review documentation -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-954) QA - support multiple VLANs for KVM HV
[ https://issues.apache.org/jira/browse/CLOUDSTACK-954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti resolved CLOUDSTACK-954. - Resolution: Fixed Already tested QA - support multiple VLANs for KVM HV -- Key: CLOUDSTACK-954 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-954 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.1.0 Reporter: Sudha Ponnaganti Assignee: sadhu suresh Fix For: 4.2.0 core tasks that need to be done: - review requirements/FS - upload test plan/test cases - get test cases reviewed - add automation - upload test results - review documentation -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-788) support multiple subnets per vlan
[ https://issues.apache.org/jira/browse/CLOUDSTACK-788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-788. --- Except automation rest of the subtasks are complete support multiple subnets per vlan - Key: CLOUDSTACK-788 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-788 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Reporter: haroon abdelrahman Assignee: Bharat Kumar Fix For: 4.2.0 Anthony, Can you provide the FS and kick off the discussion on how you propose to implement the feature? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3655) [Automation] Regression - Redundant Router test cases failed with unexpected state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-3655: - Assignee: Girish Shilamkar [Automation] Regression - Redundant Router test cases failed with unexpected state -- Key: CLOUDSTACK-3655 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3655 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.2.0 Environment: KVM regression automation Reporter: Rayees Namathponnan Assignee: Girish Shilamkar Priority: Critical Fix For: Future integration.component.test_redundant_router failed with unexpected state File /usr/local/lib/python2.7/unittest/case.py, line 318, in run testMethod() File /data/Repo2/qa/cloudstack/test/integration/component/test_redundant_router.py, line 1206, in test_stopBackupRvR Redundant state of the router should be MASTER File /usr/local/lib/python2.7/unittest/case.py, line 494, in assertEqual assertion_func(first, second, msg=msg) File /usr/local/lib/python2.7/unittest/case.py, line 487, in _baseAssertEqual raise self.failureException(msg) Redundant state of the router should be MASTER -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3655) [Automation] Regression - Redundant Router test cases failed with unexpected state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-3655: - Priority: Critical (was: Major) [Automation] Regression - Redundant Router test cases failed with unexpected state -- Key: CLOUDSTACK-3655 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3655 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.2.0 Environment: KVM regression automation Reporter: Rayees Namathponnan Priority: Critical Fix For: Future integration.component.test_redundant_router failed with unexpected state File /usr/local/lib/python2.7/unittest/case.py, line 318, in run testMethod() File /data/Repo2/qa/cloudstack/test/integration/component/test_redundant_router.py, line 1206, in test_stopBackupRvR Redundant state of the router should be MASTER File /usr/local/lib/python2.7/unittest/case.py, line 494, in assertEqual assertion_func(first, second, msg=msg) File /usr/local/lib/python2.7/unittest/case.py, line 487, in _baseAssertEqual raise self.failureException(msg) Redundant state of the router should be MASTER -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-828) QA -Test plan for Better VMware sync/DRS/HA
[ https://issues.apache.org/jira/browse/CLOUDSTACK-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13740026#comment-13740026 ] Sudha Ponnaganti commented on CLOUDSTACK-828: - Better VMSync is for future. So moving this task to future QA -Test plan for Better VMware sync/DRS/HA --- Key: CLOUDSTACK-828 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-828 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Test Reporter: David Nalley Assignee: sadhu suresh Fix For: 4.2.0 QA - Test the improved VMware sync -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-1556) QA: Ability to delete events and alerts
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-1556. QA: Ability to delete events and alerts --- Key: CLOUDSTACK-1556 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1556 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Sudha Ponnaganti Assignee: Parth Jagirdar Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-948) QA - affinity and anti affinity rules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-948. --- QA - affinity and anti affinity rules - Key: CLOUDSTACK-948 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-948 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.1.0 Reporter: Sudha Ponnaganti Assignee: Sangeetha Hariharan Fix For: 4.2.0 core tasks that need to be done: - review requirements/FS - upload test plan/test cases - get test cases reviewed - add automation - upload test results - review documentation -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-948) QA - affinity and anti affinity rules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti resolved CLOUDSTACK-948. - Resolution: Fixed QA - affinity and anti affinity rules - Key: CLOUDSTACK-948 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-948 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.1.0 Reporter: Sudha Ponnaganti Assignee: Sangeetha Hariharan Fix For: 4.2.0 core tasks that need to be done: - review requirements/FS - upload test plan/test cases - get test cases reviewed - add automation - upload test results - review documentation -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-902) QA Multiples IP's on Private LAN with Nat 1:1
[ https://issues.apache.org/jira/browse/CLOUDSTACK-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-902. --- QA Multiples IP's on Private LAN with Nat 1:1 - Key: CLOUDSTACK-902 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-902 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.1.0 Reporter: Sudha Ponnaganti Assignee: venkata swamybabu budumuru Fix For: 4.2.0 - Need to upload test plan and test results to 4.1 QA Wiki -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-888) QA volume resize feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-888. --- QA volume resize feature Key: CLOUDSTACK-888 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-888 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Test Reporter: Chip Childers Assignee: Srikanteswararao Talluri Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-888) QA volume resize feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti resolved CLOUDSTACK-888. - Resolution: Fixed QA volume resize feature Key: CLOUDSTACK-888 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-888 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Test Reporter: Chip Childers Assignee: Srikanteswararao Talluri Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-902) QA Multiples IP's on Private LAN with Nat 1:1
[ https://issues.apache.org/jira/browse/CLOUDSTACK-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti resolved CLOUDSTACK-902. - Resolution: Fixed QA Multiples IP's on Private LAN with Nat 1:1 - Key: CLOUDSTACK-902 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-902 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.1.0 Reporter: Sudha Ponnaganti Assignee: venkata swamybabu budumuru Fix For: 4.2.0 - Need to upload test plan and test results to 4.1 QA Wiki -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-907) [QA] Test the firewall functionality of the Cisco ASA 1000v
[ https://issues.apache.org/jira/browse/CLOUDSTACK-907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-907. --- [QA] Test the firewall functionality of the Cisco ASA 1000v --- Key: CLOUDSTACK-907 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-907 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Test Reporter: David Nalley Assignee: Sailaja Mada Fix For: 4.2.0 Test the firewall functionality of the Cisco ASA 1000v. 1. Review FS 2. Prepare Test Plan 3. Post the Test Plan to get it reviewed 4. Test Execution and update the test results -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-918) QA - Security Group isolation in Advaned zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-918. --- QA - Security Group isolation in Advaned zone - Key: CLOUDSTACK-918 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-918 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.1.0 Reporter: Sudha Ponnaganti Assignee: angeline shen Fix For: 4.2.0 core tasks that need to be done: - review requirements/FS - upload test plan/test cases - get test cases reviewed - add automation - upload test results - review documentation -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-907) [QA] Test the firewall functionality of the Cisco ASA 1000v
[ https://issues.apache.org/jira/browse/CLOUDSTACK-907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti resolved CLOUDSTACK-907. - Resolution: Fixed [QA] Test the firewall functionality of the Cisco ASA 1000v --- Key: CLOUDSTACK-907 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-907 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Test Reporter: David Nalley Assignee: Sailaja Mada Fix For: 4.2.0 Test the firewall functionality of the Cisco ASA 1000v. 1. Review FS 2. Prepare Test Plan 3. Post the Test Plan to get it reviewed 4. Test Execution and update the test results -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-918) QA - Security Group isolation in Advaned zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti resolved CLOUDSTACK-918. - Resolution: Fixed QA - Security Group isolation in Advaned zone - Key: CLOUDSTACK-918 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-918 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.1.0 Reporter: Sudha Ponnaganti Assignee: angeline shen Fix For: 4.2.0 core tasks that need to be done: - review requirements/FS - upload test plan/test cases - get test cases reviewed - add automation - upload test results - review documentation -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-652) High Availability: EIP enhancements
[ https://issues.apache.org/jira/browse/CLOUDSTACK-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13740059#comment-13740059 ] Sudha Ponnaganti commented on CLOUDSTACK-652: - Can this ticket me marked as resolved as implementation done for portabl IP High Availability: EIP enhancements --- Key: CLOUDSTACK-652 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-652 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.1.0 Reporter: Murali Reddy Assignee: Murali Reddy Labels: features Fix For: 4.2.0 At present CloudStack has AWS EIP like functionality available where in user can a acquire a public IP, and associate static NAT (1:1) with an instance he owns. At any time user can dis-associate the static NAT between the acquired public IP and instance, and create a new static-NAT between the public IP and any other VM instance he owns. But current EIP semantics available in CloudStack, will only let an user transfer EIP from one instance to another instance with in the same zone. In AWS, EIP [1] can be transferred across the availability zones. EIP can be used for building failover architectures on AWS. For e.g. refer to [2][3] for failover architectures with EIP. [1] http://aws.amazon.com/articles/1346 [2] http://support.rightscale.com/09-Clouds/AWS/02-Amazon_EC2/Designing_Failover_Architectures_on_EC2/00-Best_Practices_for_using_Elastic_IPs_(EIP)_and_Availability_Zones [3] http://harish11g.blogspot.in/2012/06/aws-high-availability-outage.html As part of this enhancement I would like to achieve following goals. 1. CloudStack supports EIP service only in basic zone. Enhance CloudStack, to provide EIP service in isolated/shared networks of advanced zone as well. This should bring the parity of EIP service availability in both basic and advanced zones. 2. Introduce a notion of ' Elastic IP' pool per region. User should be able to acquire an elastic IP from the pool, and establish static NAT from the EIP to any of the instances user owns in the zones under the region. 3. Elastic IP service provider in the zone, will be responsible for advertising the route for EIP to upstream router. For this RHI (Route Health Injection) functionality commonly available in ADC like NetScaler, Big IP, ADX etc will be leveraged. At the network manager framework level no specific ADC/Appliance will be assumed as Elastic IP service provider and an abstract Network Element command that achieves route health injection will need to be introduced. Finally, i would like implement EIP across zone, using NetScaler load balancer appliances. CloudStack already supports NetScaler as EIP service provider in the zone. I would like to enhance the NetScaler integration so as to provide EIP across the zones functionality. Release Planning: Dev list discussion: http://markmail.org/message/lx6tyikvmvd6wix4 Functional Spec: unknown Feature branch: unknown -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-891) QA High Availability: EIP enhancements feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti resolved CLOUDSTACK-891. - Resolution: Fixed QA High Availability: EIP enhancements feature -- Key: CLOUDSTACK-891 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-891 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Test Reporter: Chip Childers Assignee: venkata swamybabu budumuru Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-998) [QA] Test Site-to-Site VPN: Monitoring of VPN Tunnels
[ https://issues.apache.org/jira/browse/CLOUDSTACK-998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-998: Fix Version/s: (was: 4.2.0) Future [QA] Test Site-to-Site VPN: Monitoring of VPN Tunnels - Key: CLOUDSTACK-998 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-998 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Test Reporter: Sanjeev N Assignee: Sanjeev N Fix For: Future Create and execute a test plan for Monitoring of VPN Tunnels in Site-to-Site VPN -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-891) QA High Availability: EIP enhancements feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-891. --- QA High Availability: EIP enhancements feature -- Key: CLOUDSTACK-891 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-891 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Test Reporter: Chip Childers Assignee: venkata swamybabu budumuru Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-848) [QA] Test new site-to-site VPN functionality
[ https://issues.apache.org/jira/browse/CLOUDSTACK-848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-848: Fix Version/s: (was: 4.2.0) Future [QA] Test new site-to-site VPN functionality Key: CLOUDSTACK-848 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-848 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Test Reporter: David Nalley Assignee: Sanjeev N Fix For: Future Create and execute a test plan around the new Site-to-site VPN functionality. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-930) [QA] Test the Cisco VSG Integration in CloudStack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-930: Fix Version/s: (was: 4.2.0) Future [QA] Test the Cisco VSG Integration in CloudStack --- Key: CLOUDSTACK-930 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-930 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Network Devices Affects Versions: 4.1.0 Reporter: Sailaja Mada Assignee: Sailaja Mada Fix For: Future 1. Review FS 2. Prepare Test Plan 3. Post the Test Plan to get it reviewed 4. Test Execution and update the test results -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-894) QA GSLB (Global Server Load Balancing) capability for ELB service feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-894. --- QA GSLB (Global Server Load Balancing) capability for ELB service feature - Key: CLOUDSTACK-894 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-894 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Test Reporter: Chip Childers Assignee: venkata swamybabu budumuru Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-860) QA - enable L4-L7 network services in the shared network in the advanced zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13740062#comment-13740062 ] Sudha Ponnaganti commented on CLOUDSTACK-860: - Testing complete and test plan posted on cwiki ACS 4.2 QA - enable L4-L7 network services in the shared network in the advanced zone - Key: CLOUDSTACK-860 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-860 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.1.0 Reporter: Sudha Ponnaganti Assignee: venkata swamybabu budumuru Fix For: 4.2.0 - upload test cases/test results done on offline branches/ feature branch - do sanity validation on ASF CS Master branch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-860) QA - enable L4-L7 network services in the shared network in the advanced zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti resolved CLOUDSTACK-860. - Resolution: Fixed QA - enable L4-L7 network services in the shared network in the advanced zone - Key: CLOUDSTACK-860 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-860 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.1.0 Reporter: Sudha Ponnaganti Assignee: venkata swamybabu budumuru Fix For: 4.2.0 - upload test cases/test results done on offline branches/ feature branch - do sanity validation on ASF CS Master branch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-860) QA - enable L4-L7 network services in the shared network in the advanced zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-860. --- QA - enable L4-L7 network services in the shared network in the advanced zone - Key: CLOUDSTACK-860 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-860 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.1.0 Reporter: Sudha Ponnaganti Assignee: venkata swamybabu budumuru Fix For: 4.2.0 - upload test cases/test results done on offline branches/ feature branch - do sanity validation on ASF CS Master branch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-894) QA GSLB (Global Server Load Balancing) capability for ELB service feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti resolved CLOUDSTACK-894. - Resolution: Fixed QA GSLB (Global Server Load Balancing) capability for ELB service feature - Key: CLOUDSTACK-894 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-894 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Test Reporter: Chip Childers Assignee: venkata swamybabu budumuru Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-881) QA marketplace plugin
[ https://issues.apache.org/jira/browse/CLOUDSTACK-881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti resolved CLOUDSTACK-881. - Resolution: Won't Fix Assignee: Sudha Ponnaganti QA marketplace plugin - Key: CLOUDSTACK-881 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-881 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Test Reporter: Chip Childers Assignee: Sudha Ponnaganti Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-881) QA marketplace plugin
[ https://issues.apache.org/jira/browse/CLOUDSTACK-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13740065#comment-13740065 ] Sudha Ponnaganti commented on CLOUDSTACK-881: - Parent Story is marked as won't fix. This is a redundant task. Removing it from 4.2 list QA marketplace plugin - Key: CLOUDSTACK-881 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-881 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Test Reporter: Chip Childers Assignee: Sudha Ponnaganti Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-881) QA marketplace plugin
[ https://issues.apache.org/jira/browse/CLOUDSTACK-881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-881. --- QA marketplace plugin - Key: CLOUDSTACK-881 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-881 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Test Reporter: Chip Childers Assignee: Sudha Ponnaganti Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-876) QA health monitoring for HAProxy LB
[ https://issues.apache.org/jira/browse/CLOUDSTACK-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-876: Fix Version/s: (was: 4.2.0) Future QA health monitoring for HAProxy LB --- Key: CLOUDSTACK-876 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-876 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Test Reporter: Chip Childers Assignee: Abhinav Roy Fix For: Future -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-952) QA - specify egress rules on SRX
[ https://issues.apache.org/jira/browse/CLOUDSTACK-952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-952. --- Resolution: Fixed QA - specify egress rules on SRX Key: CLOUDSTACK-952 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-952 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.1.0 Reporter: Sudha Ponnaganti Assignee: angeline shen Fix For: 4.2.0 core tasks that need to be done: - review requirements/FS - upload test plan/test cases - get test cases reviewed - add automation - upload test results - review documentation -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-951) QA - Supporting kickstart for Baremetal
[ https://issues.apache.org/jira/browse/CLOUDSTACK-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-951. --- Resolution: Fixed QA - Supporting kickstart for Baremetal --- Key: CLOUDSTACK-951 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-951 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Baremetal Affects Versions: 4.1.0 Reporter: Sudha Ponnaganti Assignee: angeline shen Fix For: 4.2.0 core tasks that need to be done: - review requirements/FS - upload test plan/test cases - get test cases reviewed - add automation - upload test results - review documentation -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2841) QA: Test RBD cloning, backup and snapshotting
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-2841: - Assignee: sadhu suresh QA: Test RBD cloning, backup and snapshotting - Key: CLOUDSTACK-2841 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2841 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: KVM, Snapshot, Storage Controller, Volumes Affects Versions: 4.2.0 Reporter: Sudha Ponnaganti Assignee: sadhu suresh Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-841) [QA] Test linked clone option
[ https://issues.apache.org/jira/browse/CLOUDSTACK-841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-841. --- [QA] Test linked clone option - Key: CLOUDSTACK-841 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-841 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Test Reporter: David Nalley Assignee: prashant kumar mishra Fix For: 4.2.0 Create and execute a test plan for linked clone configuration option. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-884) QA 3rd party plugin feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-884. --- Resolution: Fixed QA 3rd party plugin feature --- Key: CLOUDSTACK-884 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-884 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Test Reporter: Chip Childers Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-884) QA 3rd party plugin feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13740072#comment-13740072 ] Sudha Ponnaganti commented on CLOUDSTACK-884: - Testing completed for this feature QA 3rd party plugin feature --- Key: CLOUDSTACK-884 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-884 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Test Reporter: Chip Childers Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-845) [QA] Test non-contiguous VLAN range support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-845. --- Resolution: Fixed testing doen and test plan posted on cwiki [QA] Test non-contiguous VLAN range support --- Key: CLOUDSTACK-845 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-845 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Test Reporter: David Nalley Assignee: Kiran Koneti Fix For: 4.2.0 Create and execute a test plan for support of non-contiguous VLAN ranges. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-941) QA - Granular Global Parameters
[ https://issues.apache.org/jira/browse/CLOUDSTACK-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-941. --- QA - Granular Global Parameters --- Key: CLOUDSTACK-941 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-941 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Reporter: Sudha Ponnaganti Assignee: prashant kumar mishra Fix For: 4.2.0 core tasks that need to be done: - review requirements/FS - upload test plan/test cases - get test cases reviewed - add automation - upload test results - review documentation -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-844) [QA] Test Load Balancing using External Provider for Shared Networks
[ https://issues.apache.org/jira/browse/CLOUDSTACK-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-844: Assignee: angeline shen [QA] Test Load Balancing using External Provider for Shared Networks Key: CLOUDSTACK-844 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-844 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Test Reporter: David Nalley Assignee: angeline shen Fix For: 4.2.0 Create and execute a test plan for Load Balancing using External Provider for Shared Networks -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-844) [QA] Test Load Balancing using External Provider for Shared Networks
[ https://issues.apache.org/jira/browse/CLOUDSTACK-844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13740077#comment-13740077 ] Sudha Ponnaganti commented on CLOUDSTACK-844: - tested and closing this issue [QA] Test Load Balancing using External Provider for Shared Networks Key: CLOUDSTACK-844 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-844 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Test Reporter: David Nalley Assignee: angeline shen Fix For: 4.2.0 Create and execute a test plan for Load Balancing using External Provider for Shared Networks -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-947) QA - Ability to manage advanced and baic zones in single instance of CS
[ https://issues.apache.org/jira/browse/CLOUDSTACK-947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-947: Fix Version/s: (was: 4.2.0) Future QA - Ability to manage advanced and baic zones in single instance of CS Key: CLOUDSTACK-947 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-947 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.1.0 Reporter: Sudha Ponnaganti Priority: Minor Fix For: Future core tasks that need to be done: - review requirements/FS - upload test plan/test cases - get test cases reviewed - add automation - upload test results - review documentation -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2263) QA : nTier Apps 2.0 Support for Netscaler as internal LB provider
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-2263: - Assignee: Abhinav Roy QA : nTier Apps 2.0 Support for Netscaler as internal LB provider - Key: CLOUDSTACK-2263 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2263 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Reporter: Sudha Ponnaganti Assignee: Abhinav Roy Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-898) QA framework for CloudStack to orchestrate virtual network appliances to provide network services
[ https://issues.apache.org/jira/browse/CLOUDSTACK-898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-898: Fix Version/s: (was: 4.2.0) Future QA framework for CloudStack to orchestrate virtual network appliances to provide network services -- Key: CLOUDSTACK-898 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-898 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Test Reporter: Chip Childers Fix For: Future -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-2263) QA : nTier Apps 2.0 Support for Netscaler as internal LB provider
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti resolved CLOUDSTACK-2263. -- Resolution: Fixed QA : nTier Apps 2.0 Support for Netscaler as internal LB provider - Key: CLOUDSTACK-2263 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2263 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Reporter: Sudha Ponnaganti Assignee: Abhinav Roy Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-844) [QA] Test Load Balancing using External Provider for Shared Networks
[ https://issues.apache.org/jira/browse/CLOUDSTACK-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-844. --- Resolution: Fixed [QA] Test Load Balancing using External Provider for Shared Networks Key: CLOUDSTACK-844 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-844 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Test Reporter: David Nalley Assignee: angeline shen Fix For: 4.2.0 Create and execute a test plan for Load Balancing using External Provider for Shared Networks -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-846) [QA] Test support for multiple IP ranges
[ https://issues.apache.org/jira/browse/CLOUDSTACK-846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-846. --- Resolution: Fixed tested and test results posted on cwiki [QA] Test support for multiple IP ranges Key: CLOUDSTACK-846 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-846 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Test Reporter: David Nalley Assignee: Sanjeev N Fix For: 4.2.0 Create and execute a test plan around support for multiple IP ranges. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-898) QA framework for CloudStack to orchestrate virtual network appliances to provide network services
[ https://issues.apache.org/jira/browse/CLOUDSTACK-898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13740080#comment-13740080 ] Sudha Ponnaganti commented on CLOUDSTACK-898: - parent ticket moved to next release QA framework for CloudStack to orchestrate virtual network appliances to provide network services -- Key: CLOUDSTACK-898 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-898 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Test Reporter: Chip Childers Fix For: Future -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-886) QA new storage subsystem
[ https://issues.apache.org/jira/browse/CLOUDSTACK-886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-886: Assignee: Sanjeev N QA new storage subsystem Key: CLOUDSTACK-886 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-886 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Test Reporter: Chip Childers Assignee: Sanjeev N Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-858) QA - Optional public IP assignment for EIP/ ELB in basic zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-858. --- Resolution: Fixed QA - Optional public IP assignment for EIP/ ELB in basic zone - Key: CLOUDSTACK-858 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-858 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.1.0 Reporter: Sudha Ponnaganti Assignee: venkata swamybabu budumuru Fix For: 4.2.0 - Upload test plan/Test cases done on feature branch/ offline - Do sanity validaiton on ASF CS Master for 41 release - Add automation for this feature -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-886) QA new storage subsystem
[ https://issues.apache.org/jira/browse/CLOUDSTACK-886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13740083#comment-13740083 ] Sudha Ponnaganti commented on CLOUDSTACK-886: - Covered as part of object storage validation QA new storage subsystem Key: CLOUDSTACK-886 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-886 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Test Reporter: Chip Childers Assignee: Sanjeev N Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-2876) QA: Validate UK, Japanese and Chinese Key board support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-2876. Resolution: Fixed testing done QA: Validate UK, Japanese and Chinese Key board support --- Key: CLOUDSTACK-2876 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2876 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: VNC Proxy Affects Versions: 4.2.0 Reporter: Sudha Ponnaganti Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-2245) QA - Egress firewall rules - Ability to change default
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-2245. Resolution: Fixed QA - Egress firewall rules - Ability to change default -- Key: CLOUDSTACK-2245 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2245 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Reporter: Sudha Ponnaganti Assignee: angeline shen Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-838) [QA] Test dedicated pod, cluster, and host functionality.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-838. --- Resolution: Fixed [QA] Test dedicated pod, cluster, and host functionality. -- Key: CLOUDSTACK-838 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-838 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Test Reporter: David Nalley Assignee: Kiran Koneti Fix For: 4.2.0 Create a test plan for testing the isolation of resources for various levels (Pod, Cluster, Host) and execute it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-905) [QA] Test networking functionality after refactoring
[ https://issues.apache.org/jira/browse/CLOUDSTACK-905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-905. --- Resolution: Fixed Automation has been run - closing this [QA] Test networking functionality after refactoring Key: CLOUDSTACK-905 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-905 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Test Reporter: David Nalley Assignee: Rayees Namathponnan Fix For: 4.2.0 Create and execute a test plan around the NetworkManager refactor. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-879) QA S3-backed Secondary Storage Feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13740090#comment-13740090 ] Sudha Ponnaganti commented on CLOUDSTACK-879: - John Can this task be closed?? thanks /sudha QA S3-backed Secondary Storage Feature -- Key: CLOUDSTACK-879 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-879 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Test Reporter: Chip Childers Assignee: John Burwell Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
