[jira] [Commented] (CLOUDSTACK-2694) [Firewall Rule] Able to configure duplicate firewall rule with protocol and no ports
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14085850#comment-14085850 ] Namita Chaudhari commented on CLOUDSTACK-2694: -- Hi Jayapal, Yes sure I will upload the patch soon to review board. Thanks, Namita [Firewall Rule] Able to configure duplicate firewall rule with protocol and no ports - Key: CLOUDSTACK-2694 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2694 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.0.0 Reporter: Jayapal Reddy 1. Configure a firewall rules with cidd 0.0.0.0/0 protocol tcp and do NOT pass ports 2. Configure the same rule again. Rule is configured successfully Expected: Should throw duplicate firewall rule error -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7245) listIsos call does not return isdynamicallyscalable in the response attributes as mentioned in API docs
Damodar Reddy T created CLOUDSTACK-7245: --- Summary: listIsos call does not return isdynamicallyscalable in the response attributes as mentioned in API docs Key: CLOUDSTACK-7245 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7245 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: API, Management Server Affects Versions: 4.2.1 Reporter: Damodar Reddy T Assignee: Damodar Reddy T Fix For: 4.5.0 There is no way to tell whether a particular iso listed is dynamically scalable or not. Even in the cloudstak UI, 'Dynamically Scalable' is listed in the template details while its not there in the ISO details. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7246) VM deployment failed due to wrong in script name createipalias.sh
Jayapal Reddy created CLOUDSTACK-7246: - Summary: VM deployment failed due to wrong in script name createipalias.sh Key: CLOUDSTACK-7246 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7246 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.5.0 Reporter: Jayapal Reddy Assignee: Jayapal Reddy Fix For: 4.5.0 1. added multiple ip range. 2. deployed vm in shared network failed. 3. createipalias failed because cloudstack referring 'createipalias.sh' but the file in VR is 'createIpAlias.sh' -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-7246) VM deployment failed due to wrong in script name createipalias.sh
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayapal Reddy resolved CLOUDSTACK-7246. --- Resolution: Fixed VM deployment failed due to wrong in script name createipalias.sh -- Key: CLOUDSTACK-7246 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7246 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.5.0 Reporter: Jayapal Reddy Assignee: Jayapal Reddy Fix For: 4.5.0 1. added multiple ip range. 2. deployed vm in shared network failed. 3. createipalias failed because cloudstack referring 'createipalias.sh' but the file in VR is 'createIpAlias.sh' -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7246) VM deployment failed due to wrong in script name createipalias.sh
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14086018#comment-14086018 ] ASF subversion and git services commented on CLOUDSTACK-7246: - Commit 912dc15bc18a2482ff78fd2f1c19bd8e46c98bf1 in cloudstack's branch refs/heads/master from Jayapal [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=912dc15 ] CLOUDSTACK-7246: corrected script name of createipalias VM deployment failed due to wrong in script name createipalias.sh -- Key: CLOUDSTACK-7246 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7246 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.5.0 Reporter: Jayapal Reddy Assignee: Jayapal Reddy Fix For: 4.5.0 1. added multiple ip range. 2. deployed vm in shared network failed. 3. createipalias failed because cloudstack referring 'createipalias.sh' but the file in VR is 'createIpAlias.sh' -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7248) [VMware]Snapshot of data volume not attached to any VM is failing to backup.
manasaveloori created CLOUDSTACK-7248: - Summary: [VMware]Snapshot of data volume not attached to any VM is failing to backup. Key: CLOUDSTACK-7248 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7248 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Snapshot, Storage Controller Affects Versions: 4.5.0 Reporter: manasaveloori Priority: Critical Fix For: 4.5.0 Attachments: management-server.rar Steps: 1. Deployed CS with ESXi5.1. 2. Deployed a VM with data disk (or)Deloy VM ,Create a volume and attach it to VM. 3. Detach the data disk from VM. 4. Take snapshot of the data disk. Observation: Snapshot is failing with following exception. 2014-08-05 14:24:13,389 DEBUG [c.c.s.s.SnapshotManagerImpl] (API-Job-Executor-48:ctx-41fc60ba job-94 ctx-11fcc509) Failed to create snapshot com.cloud.utils.exception.CloudRuntimeException: backup snapshot exception: Exception: java.lang.Exception Message: Unable to find related disk device for volume. volume path: f394364f070a411c830e295a19c5ffd6 at org.apache.cloudstack.storage.snapshot.SnapshotServiceImpl.backupSnapshot(SnapshotServiceImpl.java:282) at org.apache.cloudstack.storage.snapshot.XenserverSnapshotStrategy.backupSnapshot(XenserverSnapshotStrategy.java:137) at org.apache.cloudstack.storage.snapshot.XenserverSnapshotStrategy.takeSnapshot(XenserverSnapshotStrategy.java:300) at com.cloud.storage.snapshot.SnapshotManagerImpl.takeSnapshot(SnapshotManagerImpl.java:971) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at com.sun.proxy.$Proxy179.takeSnapshot(Unknown Source) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.takeSnapshot(VolumeServiceImpl.java:1534) at com.cloud.storage.VolumeApiServiceImpl.takeSnapshot(VolumeApiServiceImpl.java:1875) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at com.sun.proxy.$Proxy183.takeSnapshot(Unknown Source) at org.apache.cloudstack.api.command.user.snapshot.CreateSnapshotCmd.execute(CreateSnapshotCmd.java:187) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141) at com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at
[jira] [Created] (CLOUDSTACK-7247) marvin deployVirtualMachine calls default to hypervisor=XenServer
John Dilley created CLOUDSTACK-7247: --- Summary: marvin deployVirtualMachine calls default to hypervisor=XenServer Key: CLOUDSTACK-7247 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7247 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Automation, marvin Affects Versions: 4.5.0 Reporter: John Dilley Assignee: John Dilley Priority: Blocker Lots of failures in marvin since the fix for CLOUDSTACK-7194 now validates that the template hypervisor type and the deployVirtualMachine hypervisor match, or only one specifies a hypervisor. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7248) [VMware]Snapshot of data volume not attached to any VM is failing to backup.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] manasaveloori updated CLOUDSTACK-7248: -- Attachment: management-server.rar [VMware]Snapshot of data volume not attached to any VM is failing to backup. Key: CLOUDSTACK-7248 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7248 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Snapshot, Storage Controller Affects Versions: 4.5.0 Reporter: manasaveloori Priority: Critical Fix For: 4.5.0 Attachments: management-server.rar Steps: 1. Deployed CS with ESXi5.1. 2. Deployed a VM with data disk (or)Deloy VM ,Create a volume and attach it to VM. 3. Detach the data disk from VM. 4. Take snapshot of the data disk. Observation: Snapshot is failing with following exception. 2014-08-05 14:24:13,389 DEBUG [c.c.s.s.SnapshotManagerImpl] (API-Job-Executor-48:ctx-41fc60ba job-94 ctx-11fcc509) Failed to create snapshot com.cloud.utils.exception.CloudRuntimeException: backup snapshot exception: Exception: java.lang.Exception Message: Unable to find related disk device for volume. volume path: f394364f070a411c830e295a19c5ffd6 at org.apache.cloudstack.storage.snapshot.SnapshotServiceImpl.backupSnapshot(SnapshotServiceImpl.java:282) at org.apache.cloudstack.storage.snapshot.XenserverSnapshotStrategy.backupSnapshot(XenserverSnapshotStrategy.java:137) at org.apache.cloudstack.storage.snapshot.XenserverSnapshotStrategy.takeSnapshot(XenserverSnapshotStrategy.java:300) at com.cloud.storage.snapshot.SnapshotManagerImpl.takeSnapshot(SnapshotManagerImpl.java:971) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at com.sun.proxy.$Proxy179.takeSnapshot(Unknown Source) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.takeSnapshot(VolumeServiceImpl.java:1534) at com.cloud.storage.VolumeApiServiceImpl.takeSnapshot(VolumeApiServiceImpl.java:1875) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at com.sun.proxy.$Proxy183.takeSnapshot(Unknown Source) at org.apache.cloudstack.api.command.user.snapshot.CreateSnapshotCmd.execute(CreateSnapshotCmd.java:187) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141) at com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at
[jira] [Commented] (CLOUDSTACK-7246) VM deployment failed due to wrong in script name createipalias.sh
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14086032#comment-14086032 ] ASF subversion and git services commented on CLOUDSTACK-7246: - Commit 1bfb1f6503167c3de2c01894b32d287a98424dbc in cloudstack's branch refs/heads/master from Jayapal [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=1bfb1f6 ] CLOUDSTACK-7246: corrected script name of createipalias VM deployment failed due to wrong in script name createipalias.sh -- Key: CLOUDSTACK-7246 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7246 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.5.0 Reporter: Jayapal Reddy Assignee: Jayapal Reddy Fix For: 4.5.0 1. added multiple ip range. 2. deployed vm in shared network failed. 3. createipalias failed because cloudstack referring 'createipalias.sh' but the file in VR is 'createIpAlias.sh' -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7247) marvin deployVirtualMachine calls default to hypervisor=XenServer
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14086037#comment-14086037 ] John Dilley commented on CLOUDSTACK-7247: - Review at https://reviews.apache.org/r/24304/ marvin deployVirtualMachine calls default to hypervisor=XenServer - Key: CLOUDSTACK-7247 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7247 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation, marvin Affects Versions: 4.5.0 Reporter: John Dilley Assignee: John Dilley Priority: Blocker Lots of failures in marvin since the fix for CLOUDSTACK-7194 now validates that the template hypervisor type and the deployVirtualMachine hypervisor match, or only one specifies a hypervisor. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-7223) test_ssvm tests don't wait for agent to be connected before verifying System VMS
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Dilley reassigned CLOUDSTACK-7223: --- Assignee: John Dilley (was: Santhosh Kumar Edukulla) test_ssvm tests don't wait for agent to be connected before verifying System VMS Key: CLOUDSTACK-7223 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7223 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation, marvin Affects Versions: 4.5.0 Reporter: John Dilley Assignee: John Dilley I often get failures on the test_ssvm tests where the check_ssvm script fails because NFS is not mounted. This could be because although marvin waits for the System VM to be in the running state, it doesn't wait for the host object to be up (the Agent State in the UI). It's hard to prove this is the cause, but it seems like it should be fixed anyway. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-7223) test_ssvm tests don't wait for agent to be connected before verifying System VMS
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Dilley resolved CLOUDSTACK-7223. - Resolution: Fixed test_ssvm tests don't wait for agent to be connected before verifying System VMS Key: CLOUDSTACK-7223 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7223 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation, marvin Affects Versions: 4.5.0 Reporter: John Dilley Assignee: John Dilley I often get failures on the test_ssvm tests where the check_ssvm script fails because NFS is not mounted. This could be because although marvin waits for the System VM to be in the running state, it doesn't wait for the host object to be up (the Agent State in the UI). It's hard to prove this is the cause, but it seems like it should be fixed anyway. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-7192) BVT tests which don't apply to Hyper-V should be skipped
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Dilley reassigned CLOUDSTACK-7192: --- Assignee: John Dilley (was: Rayees Namathponnan) BVT tests which don't apply to Hyper-V should be skipped Key: CLOUDSTACK-7192 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7192 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Automation, marvin Affects Versions: 4.5.0 Reporter: John Dilley Assignee: John Dilley If a test is run through nose which doesn't apply to the hypervisor under test, the test should be skipped. In particular, there are many Hyper-V tests which this applies to. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7192) BVT tests which don't apply to Hyper-V should be skipped
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14086045#comment-14086045 ] John Dilley commented on CLOUDSTACK-7192: - Review in progress at https://reviews.apache.org/r/23982 BVT tests which don't apply to Hyper-V should be skipped Key: CLOUDSTACK-7192 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7192 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Automation, marvin Affects Versions: 4.5.0 Reporter: John Dilley Assignee: John Dilley If a test is run through nose which doesn't apply to the hypervisor under test, the test should be skipped. In particular, there are many Hyper-V tests which this applies to. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-2694) [Firewall Rule] Able to configure duplicate firewall rule with protocol and no ports
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14086052#comment-14086052 ] Namita Chaudhari commented on CLOUDSTACK-2694: -- I have uploaded the review patch at https://reviews.apache.org/r/24306/ [Firewall Rule] Able to configure duplicate firewall rule with protocol and no ports - Key: CLOUDSTACK-2694 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2694 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.0.0 Reporter: Jayapal Reddy 1. Configure a firewall rules with cidd 0.0.0.0/0 protocol tcp and do NOT pass ports 2. Configure the same rule again. Rule is configured successfully Expected: Should throw duplicate firewall rule error -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Issue Comment Deleted] (CLOUDSTACK-7247) marvin deployVirtualMachine calls default to hypervisor=XenServer
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Dilley updated CLOUDSTACK-7247: Comment: was deleted (was: Review at https://reviews.apache.org/r/24304/) marvin deployVirtualMachine calls default to hypervisor=XenServer - Key: CLOUDSTACK-7247 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7247 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation, marvin Affects Versions: 4.5.0 Reporter: John Dilley Assignee: John Dilley Priority: Blocker Lots of failures in marvin since the fix for CLOUDSTACK-7194 now validates that the template hypervisor type and the deployVirtualMachine hypervisor match, or only one specifies a hypervisor. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7247) marvin deployVirtualMachine calls default to hypervisor=XenServer
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14086054#comment-14086054 ] John Dilley commented on CLOUDSTACK-7247: - Gaurav's review at https://reviews.apache.org/r/24301 marvin deployVirtualMachine calls default to hypervisor=XenServer - Key: CLOUDSTACK-7247 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7247 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation, marvin Affects Versions: 4.5.0 Reporter: John Dilley Assignee: John Dilley Priority: Blocker Lots of failures in marvin since the fix for CLOUDSTACK-7194 now validates that the template hypervisor type and the deployVirtualMachine hypervisor match, or only one specifies a hypervisor. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7249) Enable Password Strength check for all users
Damodar Reddy T created CLOUDSTACK-7249: --- Summary: Enable Password Strength check for all users Key: CLOUDSTACK-7249 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7249 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.5.0 Reporter: Damodar Reddy T Assignee: Damodar Reddy T Fix For: 4.5.0 Currently we do not show the password strength of a user for his chosen password int he API response. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7250) [vCenter 5.5] SourceNAT,StaticNAT and Portfowrding is not working with Vmware DVS in vCenter 5.5
Sateesh Chodapuneedi created CLOUDSTACK-7250:
Summary: [vCenter 5.5] SourceNAT,StaticNAT and Portfowrding is not
working with Vmware DVS in vCenter 5.5
Key: CLOUDSTACK-7250
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7250
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: VMware
Affects Versions: 4.2.0, 4.2.1, 4.3.0, 4.4.0, 4.3.1
Environment: vCenter 5.5
CloudStack version 4.2 or later until 4.5
Reporter: Sateesh Chodapuneedi
Assignee: Sateesh Chodapuneedi
Fix For: 4.5.0
Cloudstack is unable to get the VIF information for the VR's and the IPASSOC
commands are failing.
I installed CloudStack 4.3 fresh (no upgrade).
The installation was finished without a problem.
SSVM and CPVM was created.
The first VM was created, but the following problems occurred.
-I can't ping internet site's IP address (for example google.com)
-An error occurs when I set StaticNAT or Portfowrding
The error is Failed to apply port forwarding rule
Also seeing following errors,
2014-08-05 08:42:58,086 INFO [vmware.resource.VmwareResource]
(DirectAgent-366:10.102.192.3) Executing resource IPAssocCommand:
{ipAddresses:[
{accountId:2,publicIp:10.102.196.147,sourceNat:true,add:true,oneToOneNat:false,firstIP:true,vlanId:100,vlanGateway:10.102.196.1,vlanNetmask:255.255.255.0,vifMacAddress:06:a5:a8:00:00:13,networkRate:200,trafficType:Public,networkName:dvSwitch0,,vmwaredvs}
],accessDetails:
{router.guest.ip:10.1.1.1,zone.network.type:Advanced,router.ip:10.102.194.139,router.name:r-4-VM}
,wait:0}
2014-08-05 08:42:58,108 DEBUG [vmware.resource.VmwareResource]
(DirectAgent-366:10.102.192.3) Use router's private IP for SSH control. IP :
10.102.194.139
2014-08-05 08:42:58,108 DEBUG [vmware.mo.HostMO] (DirectAgent-366:10.102.192.3)
find VM r-4-VM on host
2014-08-05 08:42:58,109 INFO [vmware.mo.HostMO] (DirectAgent-366:10.102.192.3)
VM r-4-VM not found in host cache
2014-08-05 08:42:58,109 DEBUG [vmware.mo.HostMO] (DirectAgent-366:10.102.192.3)
load VM cache on host
2014-08-05 08:42:58,151 DEBUG [vmware.resource.VmwareResource]
(DirectAgent-366:10.102.192.3) Find public NIC index, public network name:
cloud.public.100, index: -1
2014-08-05 08:42:58,151 DEBUG [vmware.resource.VmwareResource]
(DirectAgent-366:10.102.192.3) Plug new NIC to associate10.102.194.139 to
10.102.196.147
2014-08-05 08:42:58,199 INFO [vmware.mo.HypervisorHostHelper]
(DirectAgent-366:10.102.192.3) Found distributed vSwitch
com.vmware.vim25.ManagedObjectReference@1d30d21
2014-08-05 08:42:58,210 INFO [vmware.mo.HypervisorHostHelper]
(DirectAgent-366:10.102.192.3) Found Distributed Virtual Port group
cloud.public.100.0.1-dvSwitch0
2014-08-05 08:42:58,233 INFO [vmware.mo.HypervisorHostHelper]
(DirectAgent-366:10.102.192.3) Updating Distributed Virtual Port group
cloud.public.100.0.1-dvSwitch0
2014-08-05 08:42:58,482 DEBUG [vmware.mo.HypervisorHostHelper]
(DirectAgent-366:10.102.192.3) Added custom field : cloud.gc.dvp
2014-08-05 08:42:59,272 DEBUG [cloud.api.ApiServlet]
(20680265@qtp-27965857-15:null) ===START=== 10.140.6.50 – GET
command=queryAsyncJobResultjobId=4434d615-986a-41de-9813-65b2a10e4ea0response=jsonsessionkey=Irg0Tdoo%2Fb0rwRJrBDaHLjdhIXo%3D_=1407228207738
2014-08-05 08:42:59,306 DEBUG [cloud.api.ApiServlet]
(20680265@qtp-27965857-15:null) ===END=== 10.140.6.50 – GET
command=queryAsyncJobResultjobId=4434d615-986a-41de-9813-65b2a10e4ea0response=jsonsessionkey=Irg0Tdoo%2Fb0rwRJrBDaHLjdhIXo%3D_=1407228207738
2014-08-05 08:42:59,317 ERROR [vmware.resource.VmwareResource]
(DirectAgent-366:10.102.192.3) Failed to find DomR VIF to
associate/disassociate IP with.
2014-08-05 08:42:59,318 ERROR [vmware.resource.VmwareResource]
(DirectAgent-366:10.102.192.3) Unexpected exception:
com.cloud.exception.InternalErrorException: Failed to find DomR VIF to
associate/disassociate IP with. will shortcut rest of IPAssoc commands
com.cloud.exception.InternalErrorException: Failed to find DomR VIF to
associate/disassociate IP with.
at
com.cloud.hypervisor.vmware.resource.VmwareResource.assignPublicIpAddress(VmwareResource.java:1877)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2059)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:427)
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
[jira] [Created] (CLOUDSTACK-7251) [LXC] VM installation fails when using local storage as primary storage
shweta agarwal created CLOUDSTACK-7251:
--
Summary: [LXC] VM installation fails when using local storage as
primary storage
Key: CLOUDSTACK-7251
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7251
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: KVM
Affects Versions: 4.5.0
Reporter: shweta agarwal
Priority: Blocker
Fix For: 4.5.0
Repro steps:
Create a LXC setup with local storage enabled
create a service offering with local storage
create a VM with theta service offering
Bug:
VM creation error out
MS log shows :
2014-08-05 05:01:56,832 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-17:ctx-66f0332c job-200/job-201 ctx-1f8afb7d) Seq
1-8575416640466846714: Sending { Cmd , MgmtId: 233845177509765, via:
1(Rack1Pod1Host23), Ver: v1, Flags: 100011,
[{com.cloud.agent.api.StartCommand:{vm:{id:17,name:i-2-17-VM,type:User,cpus:1,minSpeed:128,maxSpeed:128,minRam:134217728,maxRam:134217728,arch:x86_64,os:CentOS
6.4
(64-bit),platformEmulator:Other,bootArgs:,rebootOnCrash:false,enableHA:false,limitCpuUse:false,enableDynamicallyScaleVm:false,vncPassword:f7a4e3e8e4fec4f9,params:{},uuid:5cfab85b-ceae-4df0-ac0e-a07a84bda843,disks:[{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:0b021367-8870-495f-93b0-f28e3d0e86d7,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:2bbf9d08-b442-4a87-9f26-41d39679747b,id:3,poolType:Filesystem,host:10.147.40.23,path:/var/lib/libvirt/images,port:0,url:Filesystem://10.147.40.23/var/lib/libvirt/images/?ROLE=PrimarySTOREUUID=2bbf9d08-b442-4a87-9f26-41d39679747b}},name:ROOT-17,size:0,path:0b021367-8870-495f-93b0-f28e3d0e86d7,volumeId:18,vmName:i-2-17-VM,accountId:2,provisioningType:THIN,id:18,deviceId:0,hypervisorType:LXC}},diskSeq:0,path:0b021367-8870-495f-93b0-f28e3d0e86d7,type:ROOT,_details:{managed:false,storagePort:0,storageHost:10.147.40.23,volumeSize:0}},{data:{org.apache.cloudstack.storage.to.TemplateObjectTO:{id:0,format:ISO,accountId:0,hvm:false}},diskSeq:3,type:ISO}],nics:[{deviceId:0,networkRateMbps:200,defaultNic:true,pxeDisable:false,nicUuid:065d160a-9bd8-4d34-b9ea-655014468157,uuid:675b6a8c-2ab1-4ea1-bf20-3ddd910b9ecd,ip:10.1.1.232,netmask:255.255.255.0,gateway:10.1.1.1,mac:02:00:4a:e1:00:0b,dns1:10.140.50.6,dns2:,broadcastType:Vlan,type:Guest,broadcastUri:vlan://1046,isolationUri:vlan://1046,isSecurityGroupEnabled:false}]},hostIp:10.147.40.23,executeInSequence:false,wait:0}}]
}
2014-08-05 05:01:57,272 DEBUG [c.c.a.ApiServlet]
(catalina-exec-21:ctx-3c782bac) ===START=== 10.146.0.131 -- GET
command=queryAsyncJobResultjobId=80f71511-b142-4d46-8108-697905b62179response=jsonsessionkey=X745JY%2BC0rOgkt4Sbx3muCB1eJQ%3D_=1407229318792
2014-08-05 05:01:57,332 DEBUG [c.c.a.ApiServlet] (catalina-exec-21:ctx-3c782bac
ctx-2802cc3d) ===END=== 10.146.0.131 -- GET
command=queryAsyncJobResultjobId=80f71511-b142-4d46-8108-697905b62179response=jsonsessionkey=X745JY%2BC0rOgkt4Sbx3muCB1eJQ%3D_=1407229318792
2014-08-05 05:01:57,355 DEBUG [c.c.s.StatsCollector]
(StatsCollector-1:ctx-a0a21868) HostStatsCollector is running...
2014-08-05 05:01:57,361 WARN [o.a.c.f.j.AsyncJobExecutionContext]
(StatsCollector-1:ctx-a0a21868) Job is executed without a context, setup psudo
job for the executing thread
2014-08-05 05:01:58,006 DEBUG [c.c.a.t.Request] (StatsCollector-1:ctx-a0a21868)
Seq 1-8575416640466846715: Received: { Ans: , MgmtId: 233845177509765, via: 1,
Ver: v1, Flags: 10, { GetHostStatsAnswer } }
2014-08-05 05:01:58,059 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
Timer:ctx-599ebf73) Resetting hosts suitable for reconnect
2014-08-05 05:01:58,060 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
Timer:ctx-599ebf73) Completed resetting hosts suitable for reconnect
2014-08-05 05:01:58,060 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
Timer:ctx-599ebf73) Acquiring hosts for clusters already owned by this
management server
2014-08-05 05:01:58,061 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
Timer:ctx-599ebf73) Completed acquiring hosts for clusters already owned by
this management server
2014-08-05 05:01:58,061 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
Timer:ctx-599ebf73) Acquiring hosts for clusters not owned by any management
server
2014-08-05 05:01:58,061 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
Timer:ctx-599ebf73) Completed acquiring hosts for clusters not owned by any
management server
2014-08-05 05:01:58,454 DEBUG [c.c.a.ApiServlet]
(catalina-exec-22:ctx-c32fe384) ===START=== 10.146.0.131 -- GET
command=queryAsyncJobResultjobId=89d5fe9f-9df3-4c03-b945-e6e2f6c1972fresponse=jsonsessionkey=X745JY%2BC0rOgkt4Sbx3muCB1eJQ%3D_=1407229319989
2014-08-05 05:01:58,516 DEBUG [c.c.a.ApiServlet] (catalina-exec-22:ctx-c32fe384
ctx-a02236b5) ===END===
[jira] [Resolved] (CLOUDSTACK-7250) [vCenter 5.5] SourceNAT,StaticNAT and Portfowrding is not working with Vmware DVS in vCenter 5.5
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sateesh Chodapuneedi resolved CLOUDSTACK-7250.
--
Resolution: Fixed
[vCenter 5.5] SourceNAT,StaticNAT and Portfowrding is not working with Vmware
DVS in vCenter 5.5
Key: CLOUDSTACK-7250
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7250
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: VMware
Affects Versions: 4.2.0, 4.2.1, 4.3.0, 4.4.0, 4.3.1
Environment: vCenter 5.5
CloudStack version 4.2 or later until 4.5
Reporter: Sateesh Chodapuneedi
Assignee: Sateesh Chodapuneedi
Fix For: 4.5.0
Cloudstack is unable to get the VIF information for the VR's and the IPASSOC
commands are failing.
I installed CloudStack 4.3 fresh (no upgrade).
The installation was finished without a problem.
SSVM and CPVM was created.
The first VM was created, but the following problems occurred.
-I can't ping internet site's IP address (for example google.com)
-An error occurs when I set StaticNAT or Portfowrding
The error is Failed to apply port forwarding rule
Also seeing following errors,
2014-08-05 08:42:58,086 INFO [vmware.resource.VmwareResource]
(DirectAgent-366:10.102.192.3) Executing resource IPAssocCommand:
{ipAddresses:[
{accountId:2,publicIp:10.102.196.147,sourceNat:true,add:true,oneToOneNat:false,firstIP:true,vlanId:100,vlanGateway:10.102.196.1,vlanNetmask:255.255.255.0,vifMacAddress:06:a5:a8:00:00:13,networkRate:200,trafficType:Public,networkName:dvSwitch0,,vmwaredvs}
],accessDetails:
{router.guest.ip:10.1.1.1,zone.network.type:Advanced,router.ip:10.102.194.139,router.name:r-4-VM}
,wait:0}
2014-08-05 08:42:58,108 DEBUG [vmware.resource.VmwareResource]
(DirectAgent-366:10.102.192.3) Use router's private IP for SSH control. IP :
10.102.194.139
2014-08-05 08:42:58,108 DEBUG [vmware.mo.HostMO]
(DirectAgent-366:10.102.192.3) find VM r-4-VM on host
2014-08-05 08:42:58,109 INFO [vmware.mo.HostMO]
(DirectAgent-366:10.102.192.3) VM r-4-VM not found in host cache
2014-08-05 08:42:58,109 DEBUG [vmware.mo.HostMO]
(DirectAgent-366:10.102.192.3) load VM cache on host
2014-08-05 08:42:58,151 DEBUG [vmware.resource.VmwareResource]
(DirectAgent-366:10.102.192.3) Find public NIC index, public network name:
cloud.public.100, index: -1
2014-08-05 08:42:58,151 DEBUG [vmware.resource.VmwareResource]
(DirectAgent-366:10.102.192.3) Plug new NIC to associate10.102.194.139 to
10.102.196.147
2014-08-05 08:42:58,199 INFO [vmware.mo.HypervisorHostHelper]
(DirectAgent-366:10.102.192.3) Found distributed vSwitch
com.vmware.vim25.ManagedObjectReference@1d30d21
2014-08-05 08:42:58,210 INFO [vmware.mo.HypervisorHostHelper]
(DirectAgent-366:10.102.192.3) Found Distributed Virtual Port group
cloud.public.100.0.1-dvSwitch0
2014-08-05 08:42:58,233 INFO [vmware.mo.HypervisorHostHelper]
(DirectAgent-366:10.102.192.3) Updating Distributed Virtual Port group
cloud.public.100.0.1-dvSwitch0
2014-08-05 08:42:58,482 DEBUG [vmware.mo.HypervisorHostHelper]
(DirectAgent-366:10.102.192.3) Added custom field : cloud.gc.dvp
2014-08-05 08:42:59,272 DEBUG [cloud.api.ApiServlet]
(20680265@qtp-27965857-15:null) ===START=== 10.140.6.50 – GET
command=queryAsyncJobResultjobId=4434d615-986a-41de-9813-65b2a10e4ea0response=jsonsessionkey=Irg0Tdoo%2Fb0rwRJrBDaHLjdhIXo%3D_=1407228207738
2014-08-05 08:42:59,306 DEBUG [cloud.api.ApiServlet]
(20680265@qtp-27965857-15:null) ===END=== 10.140.6.50 – GET
command=queryAsyncJobResultjobId=4434d615-986a-41de-9813-65b2a10e4ea0response=jsonsessionkey=Irg0Tdoo%2Fb0rwRJrBDaHLjdhIXo%3D_=1407228207738
2014-08-05 08:42:59,317 ERROR [vmware.resource.VmwareResource]
(DirectAgent-366:10.102.192.3) Failed to find DomR VIF to
associate/disassociate IP with.
2014-08-05 08:42:59,318 ERROR [vmware.resource.VmwareResource]
(DirectAgent-366:10.102.192.3) Unexpected exception:
com.cloud.exception.InternalErrorException: Failed to find DomR VIF to
associate/disassociate IP with. will shortcut rest of IPAssoc commands
com.cloud.exception.InternalErrorException: Failed to find DomR VIF to
associate/disassociate IP with.
at
com.cloud.hypervisor.vmware.resource.VmwareResource.assignPublicIpAddress(VmwareResource.java:1877)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2059)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:427)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at
[jira] [Commented] (CLOUDSTACK-7250) [vCenter 5.5] SourceNAT,StaticNAT and Portfowrding is not working with Vmware DVS in vCenter 5.5
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14086075#comment-14086075
]
Sateesh Chodapuneedi commented on CLOUDSTACK-7250:
--
CLOUDSTACK-7250 [vCenter 5.5] SourceNAT,StaticNAT and Portfowrding is not
working with Vmware DVS in vCenter 5.5
Change in vCenter 5.5 API from prior versions forced code change in CloudStack.
Update property value of property VirtualE1000.deviceInfo.summary is
accommodated now.
Signed-off-by: Sateesh Chodapuneedi sate...@apache.org
Project: http://git-wip-us.apache.org/repos/asf/cloudstack/repo
Commit: http://git-wip-us.apache.org/repos/asf/cloudstack/commit/dfa607fb
Tree: http://git-wip-us.apache.org/repos/asf/cloudstack/tree/dfa607fb
Diff: http://git-wip-us.apache.org/repos/asf/cloudstack/diff/dfa607fb
Branch: refs/heads/master
Commit: dfa607fb443cbd0c3f2c264c2abfa9f1844a16ce
Parents: cc725e5
Author: Sateesh Chodapuneedi sate...@apache.org
Authored: Tue Aug 5 10:00:00 2014 +0530
Committer: Sateesh Chodapuneedi sate...@apache.org
Committed: Tue Aug 5 10:00:00 2014 +0530
[vCenter 5.5] SourceNAT,StaticNAT and Portfowrding is not working with Vmware
DVS in vCenter 5.5
Key: CLOUDSTACK-7250
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7250
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: VMware
Affects Versions: 4.2.0, 4.2.1, 4.3.0, 4.4.0, 4.3.1
Environment: vCenter 5.5
CloudStack version 4.2 or later until 4.5
Reporter: Sateesh Chodapuneedi
Assignee: Sateesh Chodapuneedi
Fix For: 4.5.0
Cloudstack is unable to get the VIF information for the VR's and the IPASSOC
commands are failing.
I installed CloudStack 4.3 fresh (no upgrade).
The installation was finished without a problem.
SSVM and CPVM was created.
The first VM was created, but the following problems occurred.
-I can't ping internet site's IP address (for example google.com)
-An error occurs when I set StaticNAT or Portfowrding
The error is Failed to apply port forwarding rule
Also seeing following errors,
2014-08-05 08:42:58,086 INFO [vmware.resource.VmwareResource]
(DirectAgent-366:10.102.192.3) Executing resource IPAssocCommand:
{ipAddresses:[
{accountId:2,publicIp:10.102.196.147,sourceNat:true,add:true,oneToOneNat:false,firstIP:true,vlanId:100,vlanGateway:10.102.196.1,vlanNetmask:255.255.255.0,vifMacAddress:06:a5:a8:00:00:13,networkRate:200,trafficType:Public,networkName:dvSwitch0,,vmwaredvs}
],accessDetails:
{router.guest.ip:10.1.1.1,zone.network.type:Advanced,router.ip:10.102.194.139,router.name:r-4-VM}
,wait:0}
2014-08-05 08:42:58,108 DEBUG [vmware.resource.VmwareResource]
(DirectAgent-366:10.102.192.3) Use router's private IP for SSH control. IP :
10.102.194.139
2014-08-05 08:42:58,108 DEBUG [vmware.mo.HostMO]
(DirectAgent-366:10.102.192.3) find VM r-4-VM on host
2014-08-05 08:42:58,109 INFO [vmware.mo.HostMO]
(DirectAgent-366:10.102.192.3) VM r-4-VM not found in host cache
2014-08-05 08:42:58,109 DEBUG [vmware.mo.HostMO]
(DirectAgent-366:10.102.192.3) load VM cache on host
2014-08-05 08:42:58,151 DEBUG [vmware.resource.VmwareResource]
(DirectAgent-366:10.102.192.3) Find public NIC index, public network name:
cloud.public.100, index: -1
2014-08-05 08:42:58,151 DEBUG [vmware.resource.VmwareResource]
(DirectAgent-366:10.102.192.3) Plug new NIC to associate10.102.194.139 to
10.102.196.147
2014-08-05 08:42:58,199 INFO [vmware.mo.HypervisorHostHelper]
(DirectAgent-366:10.102.192.3) Found distributed vSwitch
com.vmware.vim25.ManagedObjectReference@1d30d21
2014-08-05 08:42:58,210 INFO [vmware.mo.HypervisorHostHelper]
(DirectAgent-366:10.102.192.3) Found Distributed Virtual Port group
cloud.public.100.0.1-dvSwitch0
2014-08-05 08:42:58,233 INFO [vmware.mo.HypervisorHostHelper]
(DirectAgent-366:10.102.192.3) Updating Distributed Virtual Port group
cloud.public.100.0.1-dvSwitch0
2014-08-05 08:42:58,482 DEBUG [vmware.mo.HypervisorHostHelper]
(DirectAgent-366:10.102.192.3) Added custom field : cloud.gc.dvp
2014-08-05 08:42:59,272 DEBUG [cloud.api.ApiServlet]
(20680265@qtp-27965857-15:null) ===START=== 10.140.6.50 – GET
command=queryAsyncJobResultjobId=4434d615-986a-41de-9813-65b2a10e4ea0response=jsonsessionkey=Irg0Tdoo%2Fb0rwRJrBDaHLjdhIXo%3D_=1407228207738
2014-08-05 08:42:59,306 DEBUG [cloud.api.ApiServlet]
(20680265@qtp-27965857-15:null) ===END=== 10.140.6.50 – GET
command=queryAsyncJobResultjobId=4434d615-986a-41de-9813-65b2a10e4ea0response=jsonsessionkey=Irg0Tdoo%2Fb0rwRJrBDaHLjdhIXo%3D_=1407228207738
2014-08-05 08:42:59,317 ERROR [vmware.resource.VmwareResource]
[jira] [Updated] (CLOUDSTACK-4819) Created template within a project not shows up.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Turner updated CLOUDSTACK-4819: --- Component/s: (was: Management Server) UI Created template within a project not shows up. --- Key: CLOUDSTACK-4819 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4819 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Environment: CS 4.2 KVM Hypervisor Reporter: Andi Daniawan The template I've created in a project did not appear both in project's template lists and default view template list. I've checked in the vm_template table on account_id column, it refers to Acct-Test account. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7250) [vCenter 5.5] SourceNAT,StaticNAT and Portfowrding is not working with Vmware DVS in vCenter 5.5
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14086073#comment-14086073
]
ASF subversion and git services commented on CLOUDSTACK-7250:
-
Commit dfa607fb443cbd0c3f2c264c2abfa9f1844a16ce in cloudstack's branch
refs/heads/master from [~sateeshc]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=dfa607f ]
CLOUDSTACK-7250 [vCenter 5.5] SourceNAT,StaticNAT and Portfowrding is not
working with Vmware DVS in vCenter 5.5
Change in vCenter 5.5 API from prior versions forced code change in CloudStack.
Update property value of property VirtualE1000.deviceInfo.summary is
accommodated now.
Signed-off-by: Sateesh Chodapuneedi sate...@apache.org
[vCenter 5.5] SourceNAT,StaticNAT and Portfowrding is not working with Vmware
DVS in vCenter 5.5
Key: CLOUDSTACK-7250
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7250
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: VMware
Affects Versions: 4.2.0, 4.2.1, 4.3.0, 4.4.0, 4.3.1
Environment: vCenter 5.5
CloudStack version 4.2 or later until 4.5
Reporter: Sateesh Chodapuneedi
Assignee: Sateesh Chodapuneedi
Fix For: 4.5.0
Cloudstack is unable to get the VIF information for the VR's and the IPASSOC
commands are failing.
I installed CloudStack 4.3 fresh (no upgrade).
The installation was finished without a problem.
SSVM and CPVM was created.
The first VM was created, but the following problems occurred.
-I can't ping internet site's IP address (for example google.com)
-An error occurs when I set StaticNAT or Portfowrding
The error is Failed to apply port forwarding rule
Also seeing following errors,
2014-08-05 08:42:58,086 INFO [vmware.resource.VmwareResource]
(DirectAgent-366:10.102.192.3) Executing resource IPAssocCommand:
{ipAddresses:[
{accountId:2,publicIp:10.102.196.147,sourceNat:true,add:true,oneToOneNat:false,firstIP:true,vlanId:100,vlanGateway:10.102.196.1,vlanNetmask:255.255.255.0,vifMacAddress:06:a5:a8:00:00:13,networkRate:200,trafficType:Public,networkName:dvSwitch0,,vmwaredvs}
],accessDetails:
{router.guest.ip:10.1.1.1,zone.network.type:Advanced,router.ip:10.102.194.139,router.name:r-4-VM}
,wait:0}
2014-08-05 08:42:58,108 DEBUG [vmware.resource.VmwareResource]
(DirectAgent-366:10.102.192.3) Use router's private IP for SSH control. IP :
10.102.194.139
2014-08-05 08:42:58,108 DEBUG [vmware.mo.HostMO]
(DirectAgent-366:10.102.192.3) find VM r-4-VM on host
2014-08-05 08:42:58,109 INFO [vmware.mo.HostMO]
(DirectAgent-366:10.102.192.3) VM r-4-VM not found in host cache
2014-08-05 08:42:58,109 DEBUG [vmware.mo.HostMO]
(DirectAgent-366:10.102.192.3) load VM cache on host
2014-08-05 08:42:58,151 DEBUG [vmware.resource.VmwareResource]
(DirectAgent-366:10.102.192.3) Find public NIC index, public network name:
cloud.public.100, index: -1
2014-08-05 08:42:58,151 DEBUG [vmware.resource.VmwareResource]
(DirectAgent-366:10.102.192.3) Plug new NIC to associate10.102.194.139 to
10.102.196.147
2014-08-05 08:42:58,199 INFO [vmware.mo.HypervisorHostHelper]
(DirectAgent-366:10.102.192.3) Found distributed vSwitch
com.vmware.vim25.ManagedObjectReference@1d30d21
2014-08-05 08:42:58,210 INFO [vmware.mo.HypervisorHostHelper]
(DirectAgent-366:10.102.192.3) Found Distributed Virtual Port group
cloud.public.100.0.1-dvSwitch0
2014-08-05 08:42:58,233 INFO [vmware.mo.HypervisorHostHelper]
(DirectAgent-366:10.102.192.3) Updating Distributed Virtual Port group
cloud.public.100.0.1-dvSwitch0
2014-08-05 08:42:58,482 DEBUG [vmware.mo.HypervisorHostHelper]
(DirectAgent-366:10.102.192.3) Added custom field : cloud.gc.dvp
2014-08-05 08:42:59,272 DEBUG [cloud.api.ApiServlet]
(20680265@qtp-27965857-15:null) ===START=== 10.140.6.50 – GET
command=queryAsyncJobResultjobId=4434d615-986a-41de-9813-65b2a10e4ea0response=jsonsessionkey=Irg0Tdoo%2Fb0rwRJrBDaHLjdhIXo%3D_=1407228207738
2014-08-05 08:42:59,306 DEBUG [cloud.api.ApiServlet]
(20680265@qtp-27965857-15:null) ===END=== 10.140.6.50 – GET
command=queryAsyncJobResultjobId=4434d615-986a-41de-9813-65b2a10e4ea0response=jsonsessionkey=Irg0Tdoo%2Fb0rwRJrBDaHLjdhIXo%3D_=1407228207738
2014-08-05 08:42:59,317 ERROR [vmware.resource.VmwareResource]
(DirectAgent-366:10.102.192.3) Failed to find DomR VIF to
associate/disassociate IP with.
2014-08-05 08:42:59,318 ERROR [vmware.resource.VmwareResource]
(DirectAgent-366:10.102.192.3) Unexpected exception:
com.cloud.exception.InternalErrorException: Failed to find DomR VIF to
associate/disassociate IP with. will shortcut rest of IPAssoc commands
[jira] [Commented] (CLOUDSTACK-4819) Created template within a project not shows up.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14086077#comment-14086077 ] Stephen Turner commented on CLOUDSTACK-4819: Thanks, I've updated the component. Created template within a project not shows up. --- Key: CLOUDSTACK-4819 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4819 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Environment: CS 4.2 KVM Hypervisor Reporter: Andi Daniawan The template I've created in a project did not appear both in project's template lists and default view template list. I've checked in the vm_template table on account_id column, it refers to Acct-Test account. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7087) [VR] [VPN] Downgrade openswan to previous version for VPN services to fix OSX client
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14086084#comment-14086084 ] ASF subversion and git services commented on CLOUDSTACK-7087: - Commit 2dfd278625a5d569a5cce2fec5ccb0d7c515c9e8 in cloudstack's branch refs/heads/master from [~harikrishna.patnala] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2dfd278 ] CLOUDSTACK-7087: Latest OS X VPN client not working Downgrading openswan version to 1:2.6.37-3 Reviewed-by: Abhinandan Signed-off-by: Sheng Yang [VR] [VPN] Downgrade openswan to previous version for VPN services to fix OSX client Key: CLOUDSTACK-7087 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7087 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Virtual Router Affects Versions: 4.2.0, 4.3.0 Reporter: Sheng Yang Assignee: Harikrishna Patnala Fix For: 4.2.1, 4.3.1 Latest OpenSwan fail to work with OSX/IOS after latest Debian security update(Mar 2014, https://www.debian.org/security/2014/dsa-2893 ). And why Debian didn’t fix it officially, is because Debian decided to drop the support for OpenSwan(since nobody is maintaining it and it hasn’t been updated for 2 years before this security fix). We would need to move to other VPN software in the future. Here is the Debian bugzilla for the issue. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744717 So far, downgrade openswan is only an intermediate solution. We need to move to other VPN software(e.g. StrongSwan) which is still maintained by Debain in the near future. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7245) listIsos call does not return isdynamicallyscalable in the response attributes as mentioned in API docs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14086086#comment-14086086 ] ASF subversion and git services commented on CLOUDSTACK-7245: - Commit 221c118b4fcfb73f77d21c8e33783d3456bd6c35 in cloudstack's branch refs/heads/master from [~damoder.reddy] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=221c118 ] CLOUDSTACK-7245: listIsos call does not return isdynamicallyscalable in the response attributes as mentioned in API docs. listIsos call does not return isdynamicallyscalable in the response attributes as mentioned in API docs --- Key: CLOUDSTACK-7245 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7245 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, Management Server Affects Versions: 4.2.1 Reporter: Damodar Reddy T Assignee: Damodar Reddy T Fix For: 4.5.0 There is no way to tell whether a particular iso listed is dynamically scalable or not. Even in the cloudstak UI, 'Dynamically Scalable' is listed in the template details while its not there in the ISO details. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7251) [LXC] VM installation fails when using local storage as primary storage
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shweta agarwal updated CLOUDSTACK-7251:
---
Assignee: Kishan Kavala
[LXC] VM installation fails when using local storage as primary storage
---
Key: CLOUDSTACK-7251
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7251
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: KVM
Affects Versions: 4.5.0
Reporter: shweta agarwal
Assignee: Kishan Kavala
Priority: Blocker
Fix For: 4.5.0
Repro steps:
Create a LXC setup with local storage enabled
create a service offering with local storage
create a VM with theta service offering
Bug:
VM creation error out
MS log shows :
2014-08-05 05:01:56,832 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-17:ctx-66f0332c job-200/job-201 ctx-1f8afb7d) Seq
1-8575416640466846714: Sending { Cmd , MgmtId: 233845177509765, via:
1(Rack1Pod1Host23), Ver: v1, Flags: 100011,
[{com.cloud.agent.api.StartCommand:{vm:{id:17,name:i-2-17-VM,type:User,cpus:1,minSpeed:128,maxSpeed:128,minRam:134217728,maxRam:134217728,arch:x86_64,os:CentOS
6.4
(64-bit),platformEmulator:Other,bootArgs:,rebootOnCrash:false,enableHA:false,limitCpuUse:false,enableDynamicallyScaleVm:false,vncPassword:f7a4e3e8e4fec4f9,params:{},uuid:5cfab85b-ceae-4df0-ac0e-a07a84bda843,disks:[{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:0b021367-8870-495f-93b0-f28e3d0e86d7,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:2bbf9d08-b442-4a87-9f26-41d39679747b,id:3,poolType:Filesystem,host:10.147.40.23,path:/var/lib/libvirt/images,port:0,url:Filesystem://10.147.40.23/var/lib/libvirt/images/?ROLE=PrimarySTOREUUID=2bbf9d08-b442-4a87-9f26-41d39679747b}},name:ROOT-17,size:0,path:0b021367-8870-495f-93b0-f28e3d0e86d7,volumeId:18,vmName:i-2-17-VM,accountId:2,provisioningType:THIN,id:18,deviceId:0,hypervisorType:LXC}},diskSeq:0,path:0b021367-8870-495f-93b0-f28e3d0e86d7,type:ROOT,_details:{managed:false,storagePort:0,storageHost:10.147.40.23,volumeSize:0}},{data:{org.apache.cloudstack.storage.to.TemplateObjectTO:{id:0,format:ISO,accountId:0,hvm:false}},diskSeq:3,type:ISO}],nics:[{deviceId:0,networkRateMbps:200,defaultNic:true,pxeDisable:false,nicUuid:065d160a-9bd8-4d34-b9ea-655014468157,uuid:675b6a8c-2ab1-4ea1-bf20-3ddd910b9ecd,ip:10.1.1.232,netmask:255.255.255.0,gateway:10.1.1.1,mac:02:00:4a:e1:00:0b,dns1:10.140.50.6,dns2:,broadcastType:Vlan,type:Guest,broadcastUri:vlan://1046,isolationUri:vlan://1046,isSecurityGroupEnabled:false}]},hostIp:10.147.40.23,executeInSequence:false,wait:0}}]
}
2014-08-05 05:01:57,272 DEBUG [c.c.a.ApiServlet]
(catalina-exec-21:ctx-3c782bac) ===START=== 10.146.0.131 -- GET
command=queryAsyncJobResultjobId=80f71511-b142-4d46-8108-697905b62179response=jsonsessionkey=X745JY%2BC0rOgkt4Sbx3muCB1eJQ%3D_=1407229318792
2014-08-05 05:01:57,332 DEBUG [c.c.a.ApiServlet]
(catalina-exec-21:ctx-3c782bac ctx-2802cc3d) ===END=== 10.146.0.131 -- GET
command=queryAsyncJobResultjobId=80f71511-b142-4d46-8108-697905b62179response=jsonsessionkey=X745JY%2BC0rOgkt4Sbx3muCB1eJQ%3D_=1407229318792
2014-08-05 05:01:57,355 DEBUG [c.c.s.StatsCollector]
(StatsCollector-1:ctx-a0a21868) HostStatsCollector is running...
2014-08-05 05:01:57,361 WARN [o.a.c.f.j.AsyncJobExecutionContext]
(StatsCollector-1:ctx-a0a21868) Job is executed without a context, setup
psudo job for the executing thread
2014-08-05 05:01:58,006 DEBUG [c.c.a.t.Request]
(StatsCollector-1:ctx-a0a21868) Seq 1-8575416640466846715: Received: { Ans:
, MgmtId: 233845177509765, via: 1, Ver: v1, Flags: 10, { GetHostStatsAnswer }
}
2014-08-05 05:01:58,059 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
Timer:ctx-599ebf73) Resetting hosts suitable for reconnect
2014-08-05 05:01:58,060 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
Timer:ctx-599ebf73) Completed resetting hosts suitable for reconnect
2014-08-05 05:01:58,060 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
Timer:ctx-599ebf73) Acquiring hosts for clusters already owned by this
management server
2014-08-05 05:01:58,061 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
Timer:ctx-599ebf73) Completed acquiring hosts for clusters already owned by
this management server
2014-08-05 05:01:58,061 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
Timer:ctx-599ebf73) Acquiring hosts for clusters not owned by any management
server
2014-08-05 05:01:58,061 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
Timer:ctx-599ebf73) Completed acquiring hosts for clusters not owned by any
management server
2014-08-05 05:01:58,454 DEBUG [c.c.a.ApiServlet]
[jira] [Created] (CLOUDSTACK-7252) [LXC] VM not starting for first time
shweta agarwal created CLOUDSTACK-7252: -- Summary: [LXC] VM not starting for first time Key: CLOUDSTACK-7252 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7252 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.5.0 Reporter: shweta agarwal Assignee: Kishan Kavala Priority: Critical Fix For: 4.5.0 Repro steps: Create a LXC zone using LXC host on rhel 6.x register a LXC template Create a VM when VM is running try accessing vm console using virsh Bug : console view shows : Connected to domain i-2-15-VM Escape character is ^] Welcome to CentOS Starting udev: /bin/mknod: `/dev/loop0': Operation not permitted /bin/chown: cannot access `/dev/loop0': No such file or directory /bin/mknod: `/dev/loop1': Operation not permitted /bin/chown: cannot access `/dev/loop1': No such file or directory /bin/mknod: `/dev/loop2': Operation not permitted /bin/chown: cannot access `/dev/loop2': No such file or directory /bin/mknod: `/dev/loop3': Operation not permitted /bin/chown: cannot access `/dev/loop3': No such file or directory /bin/mknod: `/dev/loop4': Operation not permitted /bin/chown: cannot access `/dev/loop4': No such file or directory /bin/mknod: `/dev/loop5': Operation not permitted /bin/chown: cannot access `/dev/loop5': No such file or directory /bin/mknod: `/dev/loop6': Operation not permitted /bin/chown: cannot access `/dev/loop6': No such file or directory /bin/mknod: `/dev/loop7': Operation not permitted /bin/chown: cannot access `/dev/loop7': No such file or directory /bin/mknod: `/dev/lp0': Operation not permitted /bin/chown: cannot access `/dev/lp0': No such file or directory /bin/mknod: `/dev/lp1': Operation not permitted /bin/chown: cannot access `/dev/lp1': No such file or directory /bin/mknod: `/dev/lp2': Operation not permitted /bin/chown: cannot access `/dev/lp2': No such file or directory /bin/mknod: `/dev/lp3': Operation not permitted /bin/chown: cannot access `/dev/lp3': No such file or directory /bin/mknod: `/dev/net/tun': Operation not permitted /bin/mknod: `/dev/ppp': Operation not permitted /bin/mknod: `/dev/fuse': Operation not permitted /sbin/start_udev: line 269: /proc/sys/kernel/hotplug: Read-only file system /sbin/start_udev: line 299: /etc/sysconfig/network: No such file or directory [ OK ] Setting hostname Rack1Pod1Host23: [ OK ] Checking filesystems WARNING: couldn't open /etc/fstab: No such file or directory [ OK ] warning: can't open /etc/fstab: No such file or directory mount: can't find / in /etc/fstab or /etc/mtab Mounting local filesystems: warning: can't open /etc/fstab: No such file or directory [ OK ] Enabling /etc/fstab swaps: swapon: /etc/fstab: open failed: No such file or directory [FAILED] Additional info : do a stop /start of VM and VM starts correctly -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7253) [LXC]getting java NPE server internal error on accessing console view of VM
shweta agarwal created CLOUDSTACK-7253:
--
Summary: [LXC]getting java NPE server internal error on accessing
console view of VM
Key: CLOUDSTACK-7253
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7253
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: KVM
Affects Versions: 4.5.0
Reporter: shweta agarwal
Assignee: Kishan Kavala
Priority: Critical
Fix For: 4.5.0
Repro step:
createa LXC VM and try accessing its console
Bug:
gets internal server error
MS log shows:
014-08-05 06:46:25,902 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-13:null) Ping from 3
2014-08-05 06:46:26,487 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-10:null) SeqA 2-46206: Processing Seq 2-46206: { Cmd ,
MgmtId: -1, via: 2, Ver: v1, Flags: 11,
[{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:1,_loadInfo:{\n
\connections\: []\n},wait:0}}] }
2014-08-05 06:46:26,599 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-10:null) SeqA 2-46206: Sending Seq 2-46206: { Ans: ,
MgmtId: 233845177509765, via: 2, Ver: v1, Flags: 100010,
[{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
2014-08-05 06:46:27,652 WARN [o.a.c.f.j.AsyncJobExecutionContext]
(catalina-exec-6:null) Job is executed without a context, setup psudo job for
the executing thread
2014-08-05 06:46:27,718 DEBUG [c.c.a.t.Request] (catalina-exec-6:ctx-857528e3)
Seq 1-8575416640466847185: Sending { Cmd , MgmtId: 233845177509765, via:
1(Rack1Pod1Host23), Ver: v1, Flags: 100011,
[{com.cloud.agent.api.GetVncPortCommand:{id:16,name:i-2-16-VM,wait:0}}]
}
2014-08-05 06:46:27,769 DEBUG [c.c.a.t.Request] (AgentManager-Handler-9:null)
Seq 1-8575416640466847185: Processing: { Ans: , MgmtId: 233845177509765, via:
1, Ver: v1, Flags: 10,
[{com.cloud.agent.api.Answer:{result:false,details:java.lang.NullPointerException\n\tat
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:2861)\n\tat
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1296)\n\tat
com.cloud.agent.Agent.processRequest(Agent.java:501)\n\tat
com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)\n\tat
com.cloud.utils.nio.Task.run(Task.java:84)\n\tat
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)\n\tat
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)\n\tat
java.lang.Thread.run(Thread.java:722)\n,wait:0}}] }
2014-08-05 06:46:27,769 DEBUG [c.c.a.t.Request] (catalina-exec-6:ctx-857528e3)
Seq 1-8575416640466847185: Received: { Ans: , MgmtId: 233845177509765, via: 1,
Ver: v1, Flags: 10, { Answer } }
2014-08-05 06:46:27,769 DEBUG [c.c.a.m.AgentManagerImpl]
(catalina-exec-6:ctx-857528e3) Details from executing class
com.cloud.agent.api.GetVncPortCommand: java.lang.NullPointerException
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:2861)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1296)
at com.cloud.agent.Agent.processRequest(Agent.java:501)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)
at com.cloud.utils.nio.Task.run(Task.java:84)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
2014-08-05 06:46:27,769 ERROR [c.c.s.ConsoleProxyServlet]
(catalina-exec-6:ctx-857528e3) Unexepected exception in ConsoleProxyServlet
java.lang.ClassCastException: com.cloud.agent.api.Answer cannot be cast to
com.cloud.agent.api.GetVncPortAnswer
at
com.cloud.server.ManagementServerImpl.getVncPort(ManagementServerImpl.java:2206)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
at
[jira] [Assigned] (CLOUDSTACK-7240) [Automation] VM destroy not handled properly in test_persistent_networks
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Aradhye reassigned CLOUDSTACK-7240:
--
Assignee: Gaurav Aradhye
[Automation] VM destroy not handled properly in test_persistent_networks
--
Key: CLOUDSTACK-7240
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7240
Project: CloudStack
Issue Type: Test
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation
Affects Versions: 4.5.0
Environment: KVM
Reporter: Rayees Namathponnan
Assignee: Gaurav Aradhye
Priority: Critical
Fix For: 4.5.0
Test cases from
integration.component.test_persistent_networks.TestPersistentNetworks failing
while deleting VMs
Failed to delete VM: 000c4121-d76d-4a51-9644-2109f444ce54 with error Job
failed: {jobprocstatus : 0, created : u'2014-08-03T23:02:29-0700', jobresult
: {errorcode : 530, errortext : u'Unable to find a virtual machine with
specified vmId'}, cmd :
u'org.apache.cloudstack.api.command.admin.vm.DestroyVMCmdByAdmin', userid :
u'e613082a-1a74-11e4-b040-1a6f7bb0d0a8', jobstatus : 2, jobid :
u'4adaf404-083f-4285-afd4-c2a04ef84cf2', jobresultcode : 530, jobinstanceid :
u'000c4121-d76d-4a51-9644-2109f444ce54', jobresulttype : u'object', job
If you look the test case, test case trying to delete the same VM twice
921 # Delete VM
922 virtual_machine.delete(self.api_client, expunge=True)
923
924 # Verify VM is expunged
925 self.verifyVmExpungement(virtual_machine)
- Method verifyExpungment also trying to delete the VM
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-7245) listIsos call does not return isdynamicallyscalable in the response attributes as mentioned in API docs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T resolved CLOUDSTACK-7245. - Resolution: Fixed Currently UI is not capturing isdynamicallyscalable parameter while registering a template and is not displaying while listing ISOs listIsos call does not return isdynamicallyscalable in the response attributes as mentioned in API docs --- Key: CLOUDSTACK-7245 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7245 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, Management Server Affects Versions: 4.2.1 Reporter: Damodar Reddy T Assignee: Damodar Reddy T Fix For: 4.5.0 There is no way to tell whether a particular iso listed is dynamically scalable or not. Even in the cloudstak UI, 'Dynamically Scalable' is listed in the template details while its not there in the ISO details. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7240) [Automation] VM destroy not handled properly in test_persistent_networks
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14086111#comment-14086111
]
Gaurav Aradhye commented on CLOUDSTACK-7240:
Added patch:
https://reviews.apache.org/r/24305/
[Automation] VM destroy not handled properly in test_persistent_networks
--
Key: CLOUDSTACK-7240
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7240
Project: CloudStack
Issue Type: Test
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation
Affects Versions: 4.5.0
Environment: KVM
Reporter: Rayees Namathponnan
Assignee: Gaurav Aradhye
Priority: Critical
Fix For: 4.5.0
Test cases from
integration.component.test_persistent_networks.TestPersistentNetworks failing
while deleting VMs
Failed to delete VM: 000c4121-d76d-4a51-9644-2109f444ce54 with error Job
failed: {jobprocstatus : 0, created : u'2014-08-03T23:02:29-0700', jobresult
: {errorcode : 530, errortext : u'Unable to find a virtual machine with
specified vmId'}, cmd :
u'org.apache.cloudstack.api.command.admin.vm.DestroyVMCmdByAdmin', userid :
u'e613082a-1a74-11e4-b040-1a6f7bb0d0a8', jobstatus : 2, jobid :
u'4adaf404-083f-4285-afd4-c2a04ef84cf2', jobresultcode : 530, jobinstanceid :
u'000c4121-d76d-4a51-9644-2109f444ce54', jobresulttype : u'object', job
If you look the test case, test case trying to delete the same VM twice
921 # Delete VM
922 virtual_machine.delete(self.api_client, expunge=True)
923
924 # Verify VM is expunged
925 self.verifyVmExpungement(virtual_machine)
- Method verifyExpungment also trying to delete the VM
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7233) [Automation] test_deploy_vm test case failing simulator run
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14086115#comment-14086115 ] Gaurav Aradhye commented on CLOUDSTACK-7233: Added a patch for this. https://reviews.apache.org/r/24298/ [Automation] test_deploy_vm test case failing simulator run --- Key: CLOUDSTACK-7233 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7233 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.5.0 Environment: Simulator Reporter: Rayees Namathponnan Assignee: Gaurav Aradhye Priority: Blocker Fix For: 4.5.0 Run the suite integration.smoke.test_deploy_vm from simulator Below test cases failing below error integration.smoke.test_deploy_vm.TestDeployVMVolumeCreationFailure.test_deploy_vm_volume_creation_failure integration.smoke.test_deploy_vm.TestDeployVMStartFailure.test_deploy_vm_start_failure Test cases failed with below error Error Message Start failure mock not executed begin captured stdout - === TestName: test_deploy_vm_start_failure | Status : FAILED === - end captured stdout -- begin captured logging -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7240) [Automation] VM destroy not handled properly in test_persistent_networks
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14086160#comment-14086160
]
ASF subversion and git services commented on CLOUDSTACK-7240:
-
Commit c76302cdd8a70498a792db5d7fbe82ad43b7f8b5 in cloudstack's branch
refs/heads/master from [~gauravaradhye]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c76302c ]
CLOUDSTACK-7240: Fixed expunge VM issue in test_persistent_networks.py
Signed-off-by: Santhosh Edukulla santhosh.eduku...@gmail.com
[Automation] VM destroy not handled properly in test_persistent_networks
--
Key: CLOUDSTACK-7240
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7240
Project: CloudStack
Issue Type: Test
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation
Affects Versions: 4.5.0
Environment: KVM
Reporter: Rayees Namathponnan
Assignee: Gaurav Aradhye
Priority: Critical
Fix For: 4.5.0
Test cases from
integration.component.test_persistent_networks.TestPersistentNetworks failing
while deleting VMs
Failed to delete VM: 000c4121-d76d-4a51-9644-2109f444ce54 with error Job
failed: {jobprocstatus : 0, created : u'2014-08-03T23:02:29-0700', jobresult
: {errorcode : 530, errortext : u'Unable to find a virtual machine with
specified vmId'}, cmd :
u'org.apache.cloudstack.api.command.admin.vm.DestroyVMCmdByAdmin', userid :
u'e613082a-1a74-11e4-b040-1a6f7bb0d0a8', jobstatus : 2, jobid :
u'4adaf404-083f-4285-afd4-c2a04ef84cf2', jobresultcode : 530, jobinstanceid :
u'000c4121-d76d-4a51-9644-2109f444ce54', jobresulttype : u'object', job
If you look the test case, test case trying to delete the same VM twice
921 # Delete VM
922 virtual_machine.delete(self.api_client, expunge=True)
923
924 # Verify VM is expunged
925 self.verifyVmExpungement(virtual_machine)
- Method verifyExpungment also trying to delete the VM
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (CLOUDSTACK-7254) Cloudstack support of MariaDB
Keerthiraja created CLOUDSTACK-7254: --- Summary: Cloudstack support of MariaDB Key: CLOUDSTACK-7254 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7254 Project: CloudStack Issue Type: New Feature Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.5.0 Environment: Database Reporter: Keerthiraja Hi I would like to suggest while installing cloudstack user should have choice to choose either MySQL or MariaDB. Instead of MYSQL I hope we should consider to move to MariaDB. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7247) marvin deployVirtualMachine calls default to hypervisor=XenServer
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-7247: - Fix Version/s: 4.5.0 marvin deployVirtualMachine calls default to hypervisor=XenServer - Key: CLOUDSTACK-7247 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7247 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation, marvin Affects Versions: 4.5.0 Reporter: John Dilley Assignee: John Dilley Priority: Blocker Fix For: 4.5.0 Lots of failures in marvin since the fix for CLOUDSTACK-7194 now validates that the template hypervisor type and the deployVirtualMachine hypervisor match, or only one specifies a hypervisor. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-2694) [Firewall Rule] Able to configure duplicate firewall rule with protocol and no ports
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namita Chaudhari resolved CLOUDSTACK-2694. -- Resolution: Fixed Assignee: Namita Chaudhari [Firewall Rule] Able to configure duplicate firewall rule with protocol and no ports - Key: CLOUDSTACK-2694 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2694 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.0.0 Reporter: Jayapal Reddy Assignee: Namita Chaudhari 1. Configure a firewall rules with cidd 0.0.0.0/0 protocol tcp and do NOT pass ports 2. Configure the same rule again. Rule is configured successfully Expected: Should throw duplicate firewall rule error -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-2694) [Firewall Rule] Able to configure duplicate firewall rule with protocol and no ports
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14086191#comment-14086191 ] ASF subversion and git services commented on CLOUDSTACK-2694: - Commit fce2880b9f20a372dd0a005c4575ffab526bac0b in cloudstack's branch refs/heads/master from [~namita.chaudh...@sungard.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=fce2880 ] CLOUDSTACK-2694: Able to configure duplicate firewall rule with protocol and no ports Signed-off-by: Jayapal jaya...@apache.org [Firewall Rule] Able to configure duplicate firewall rule with protocol and no ports - Key: CLOUDSTACK-2694 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2694 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.0.0 Reporter: Jayapal Reddy 1. Configure a firewall rules with cidd 0.0.0.0/0 protocol tcp and do NOT pass ports 2. Configure the same rule again. Rule is configured successfully Expected: Should throw duplicate firewall rule error -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-2694) [Firewall Rule] Able to configure duplicate firewall rule with protocol and no ports
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14086193#comment-14086193 ] Namita Chaudhari commented on CLOUDSTACK-2694: -- The patch is applied on master and hence closing the ticket. [Firewall Rule] Able to configure duplicate firewall rule with protocol and no ports - Key: CLOUDSTACK-2694 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2694 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.0.0 Reporter: Jayapal Reddy Assignee: Namita Chaudhari 1. Configure a firewall rules with cidd 0.0.0.0/0 protocol tcp and do NOT pass ports 2. Configure the same rule again. Rule is configured successfully Expected: Should throw duplicate firewall rule error -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-2694) [Firewall Rule] Able to configure duplicate firewall rule with protocol and no ports
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namita Chaudhari closed CLOUDSTACK-2694. [Firewall Rule] Able to configure duplicate firewall rule with protocol and no ports - Key: CLOUDSTACK-2694 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2694 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.0.0 Reporter: Jayapal Reddy Assignee: Namita Chaudhari 1. Configure a firewall rules with cidd 0.0.0.0/0 protocol tcp and do NOT pass ports 2. Configure the same rule again. Rule is configured successfully Expected: Should throw duplicate firewall rule error -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7254) Cloudstack support of MariaDB
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14086209#comment-14086209 ] Rohit Yadav commented on CLOUDSTACK-7254: - Hi, I've been using MariaDB 10.0.x with CloudStack management server with no issues for past one month. The 10.0.x is a stable release and is a drop in replacement for MySQL so it's up to the user/admin to decide what to use, CloudStack simply needs the host IP, user and passport on default port 3306. Cloudstack support of MariaDB - Key: CLOUDSTACK-7254 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7254 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.5.0 Environment: Database Reporter: Keerthiraja Hi I would like to suggest while installing cloudstack user should have choice to choose either MySQL or MariaDB. Instead of MYSQL I hope we should consider to move to MariaDB. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-7254) Cloudstack support of MariaDB
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Yadav resolved CLOUDSTACK-7254. - Resolution: Not a Problem Resolving it as not a problem. The fine QA folks can help test it rigorously and close it. Cloudstack support of MariaDB - Key: CLOUDSTACK-7254 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7254 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.5.0 Environment: Database Reporter: Keerthiraja Hi I would like to suggest while installing cloudstack user should have choice to choose either MySQL or MariaDB. Instead of MYSQL I hope we should consider to move to MariaDB. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7255) Account username which is already greater than 99 chars don't get appended with random string, this results in Entity already exists error while creating account t
Gaurav Aradhye created CLOUDSTACK-7255: -- Summary: Account username which is already greater than 99 chars don't get appended with random string, this results in Entity already exists error while creating account through same test case if previous account is not cleaned up Key: CLOUDSTACK-7255 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7255 Project: CloudStack Issue Type: Test Security Level: Public (Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.5.0 Reporter: Gaurav Aradhye Assignee: Gaurav Aradhye Fix For: 4.5.0 The account username should be trimmed to 92 characters before appending the 7 char random string, because in case the random string is appended and then it is trimmed, then the strings will be same if original string was greater than 99 chars. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-6695) UI should allow uploading chained SSL certificates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mihaela Stoica reassigned CLOUDSTACK-6695: -- Assignee: Mihaela Stoica UI should allow uploading chained SSL certificates --- Key: CLOUDSTACK-6695 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6695 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.3.0, 4.4.0 Reporter: Amogh Vasekar Assignee: Mihaela Stoica Priority: Critical Fix For: Future, 4.4.0 Currently, to upload chained certificates into CloudStack for SSVM / CPVM requires making API calls with right id and alias parameter. The UI only supports adding the server certificate, and should be enhanced to support adding the whole chain. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7083) Implement SAML 2.0 plugin
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14086349#comment-14086349 ] ASF subversion and git services commented on CLOUDSTACK-7083: - Commit 6cf63f2f081603cb659fa5c2a5ee4dea9191af76 in cloudstack's branch refs/heads/feature/saml2 from [~bhaisaab] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6cf63f2 ] CLOUDSTACK-7083: Add SAML2 SSO plugin skeleton and stub Signed-off-by: Rohit Yadav rohit.ya...@shapeblue.com Implement SAML 2.0 plugin - Key: CLOUDSTACK-7083 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7083 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, Cloudmonkey, IAM, UI Reporter: Rohit Yadav Assignee: Rohit Yadav Labels: features Fix For: 4.5.0 FS: https://cwiki.apache.org/confluence/display/CLOUDSTACK/SAML+2.0+Plugin -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7253) [LXC]getting java NPE server internal error on accessing console view of VM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14086352#comment-14086352
]
Kishan Kavala commented on CLOUDSTACK-7253:
---
Console view is not supported for LXC
https://issues.apache.org/jira/browse/CLOUDSTACK-4990
Instead of NPE, proper error should be returned saying Console view is not
supported
[LXC]getting java NPE server internal error on accessing console view of VM
---
Key: CLOUDSTACK-7253
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7253
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: KVM
Affects Versions: 4.5.0
Reporter: shweta agarwal
Assignee: Kishan Kavala
Priority: Critical
Fix For: 4.5.0
Repro step:
createa LXC VM and try accessing its console
Bug:
gets internal server error
MS log shows:
014-08-05 06:46:25,902 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-13:null) Ping from 3
2014-08-05 06:46:26,487 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-10:null) SeqA 2-46206: Processing Seq 2-46206: { Cmd ,
MgmtId: -1, via: 2, Ver: v1, Flags: 11,
[{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:1,_loadInfo:{\n
\connections\: []\n},wait:0}}] }
2014-08-05 06:46:26,599 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-10:null) SeqA 2-46206: Sending Seq 2-46206: { Ans: ,
MgmtId: 233845177509765, via: 2, Ver: v1, Flags: 100010,
[{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
2014-08-05 06:46:27,652 WARN [o.a.c.f.j.AsyncJobExecutionContext]
(catalina-exec-6:null) Job is executed without a context, setup psudo job for
the executing thread
2014-08-05 06:46:27,718 DEBUG [c.c.a.t.Request]
(catalina-exec-6:ctx-857528e3) Seq 1-8575416640466847185: Sending { Cmd ,
MgmtId: 233845177509765, via: 1(Rack1Pod1Host23), Ver: v1, Flags: 100011,
[{com.cloud.agent.api.GetVncPortCommand:{id:16,name:i-2-16-VM,wait:0}}]
}
2014-08-05 06:46:27,769 DEBUG [c.c.a.t.Request] (AgentManager-Handler-9:null)
Seq 1-8575416640466847185: Processing: { Ans: , MgmtId: 233845177509765,
via: 1, Ver: v1, Flags: 10,
[{com.cloud.agent.api.Answer:{result:false,details:java.lang.NullPointerException\n\tat
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:2861)\n\tat
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1296)\n\tat
com.cloud.agent.Agent.processRequest(Agent.java:501)\n\tat
com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)\n\tat
com.cloud.utils.nio.Task.run(Task.java:84)\n\tat
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)\n\tat
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)\n\tat
java.lang.Thread.run(Thread.java:722)\n,wait:0}}] }
2014-08-05 06:46:27,769 DEBUG [c.c.a.t.Request]
(catalina-exec-6:ctx-857528e3) Seq 1-8575416640466847185: Received: { Ans: ,
MgmtId: 233845177509765, via: 1, Ver: v1, Flags: 10, { Answer } }
2014-08-05 06:46:27,769 DEBUG [c.c.a.m.AgentManagerImpl]
(catalina-exec-6:ctx-857528e3) Details from executing class
com.cloud.agent.api.GetVncPortCommand: java.lang.NullPointerException
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:2861)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1296)
at com.cloud.agent.Agent.processRequest(Agent.java:501)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)
at com.cloud.utils.nio.Task.run(Task.java:84)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
2014-08-05 06:46:27,769 ERROR [c.c.s.ConsoleProxyServlet]
(catalina-exec-6:ctx-857528e3) Unexepected exception in ConsoleProxyServlet
java.lang.ClassCastException: com.cloud.agent.api.Answer cannot be cast to
com.cloud.agent.api.GetVncPortAnswer
at
com.cloud.server.ManagementServerImpl.getVncPort(ManagementServerImpl.java:2206)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
[jira] [Commented] (CLOUDSTACK-7251) [LXC] VM installation fails when using local storage as primary storage
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14086360#comment-14086360
]
Kishan Kavala commented on CLOUDSTACK-7251:
---
It is working fine on RHEl7. Probably libvirt issue in RHEL6
https://www.redhat.com/archives/libvirt-users/2012-October/msg00095.html
[LXC] VM installation fails when using local storage as primary storage
---
Key: CLOUDSTACK-7251
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7251
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: KVM
Affects Versions: 4.5.0
Reporter: shweta agarwal
Assignee: Kishan Kavala
Priority: Blocker
Fix For: 4.5.0
Repro steps:
Create a LXC setup with local storage enabled
create a service offering with local storage
create a VM with theta service offering
Bug:
VM creation error out
MS log shows :
2014-08-05 05:01:56,832 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-17:ctx-66f0332c job-200/job-201 ctx-1f8afb7d) Seq
1-8575416640466846714: Sending { Cmd , MgmtId: 233845177509765, via:
1(Rack1Pod1Host23), Ver: v1, Flags: 100011,
[{com.cloud.agent.api.StartCommand:{vm:{id:17,name:i-2-17-VM,type:User,cpus:1,minSpeed:128,maxSpeed:128,minRam:134217728,maxRam:134217728,arch:x86_64,os:CentOS
6.4
(64-bit),platformEmulator:Other,bootArgs:,rebootOnCrash:false,enableHA:false,limitCpuUse:false,enableDynamicallyScaleVm:false,vncPassword:f7a4e3e8e4fec4f9,params:{},uuid:5cfab85b-ceae-4df0-ac0e-a07a84bda843,disks:[{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:0b021367-8870-495f-93b0-f28e3d0e86d7,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:2bbf9d08-b442-4a87-9f26-41d39679747b,id:3,poolType:Filesystem,host:10.147.40.23,path:/var/lib/libvirt/images,port:0,url:Filesystem://10.147.40.23/var/lib/libvirt/images/?ROLE=PrimarySTOREUUID=2bbf9d08-b442-4a87-9f26-41d39679747b}},name:ROOT-17,size:0,path:0b021367-8870-495f-93b0-f28e3d0e86d7,volumeId:18,vmName:i-2-17-VM,accountId:2,provisioningType:THIN,id:18,deviceId:0,hypervisorType:LXC}},diskSeq:0,path:0b021367-8870-495f-93b0-f28e3d0e86d7,type:ROOT,_details:{managed:false,storagePort:0,storageHost:10.147.40.23,volumeSize:0}},{data:{org.apache.cloudstack.storage.to.TemplateObjectTO:{id:0,format:ISO,accountId:0,hvm:false}},diskSeq:3,type:ISO}],nics:[{deviceId:0,networkRateMbps:200,defaultNic:true,pxeDisable:false,nicUuid:065d160a-9bd8-4d34-b9ea-655014468157,uuid:675b6a8c-2ab1-4ea1-bf20-3ddd910b9ecd,ip:10.1.1.232,netmask:255.255.255.0,gateway:10.1.1.1,mac:02:00:4a:e1:00:0b,dns1:10.140.50.6,dns2:,broadcastType:Vlan,type:Guest,broadcastUri:vlan://1046,isolationUri:vlan://1046,isSecurityGroupEnabled:false}]},hostIp:10.147.40.23,executeInSequence:false,wait:0}}]
}
2014-08-05 05:01:57,272 DEBUG [c.c.a.ApiServlet]
(catalina-exec-21:ctx-3c782bac) ===START=== 10.146.0.131 -- GET
command=queryAsyncJobResultjobId=80f71511-b142-4d46-8108-697905b62179response=jsonsessionkey=X745JY%2BC0rOgkt4Sbx3muCB1eJQ%3D_=1407229318792
2014-08-05 05:01:57,332 DEBUG [c.c.a.ApiServlet]
(catalina-exec-21:ctx-3c782bac ctx-2802cc3d) ===END=== 10.146.0.131 -- GET
command=queryAsyncJobResultjobId=80f71511-b142-4d46-8108-697905b62179response=jsonsessionkey=X745JY%2BC0rOgkt4Sbx3muCB1eJQ%3D_=1407229318792
2014-08-05 05:01:57,355 DEBUG [c.c.s.StatsCollector]
(StatsCollector-1:ctx-a0a21868) HostStatsCollector is running...
2014-08-05 05:01:57,361 WARN [o.a.c.f.j.AsyncJobExecutionContext]
(StatsCollector-1:ctx-a0a21868) Job is executed without a context, setup
psudo job for the executing thread
2014-08-05 05:01:58,006 DEBUG [c.c.a.t.Request]
(StatsCollector-1:ctx-a0a21868) Seq 1-8575416640466846715: Received: { Ans:
, MgmtId: 233845177509765, via: 1, Ver: v1, Flags: 10, { GetHostStatsAnswer }
}
2014-08-05 05:01:58,059 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
Timer:ctx-599ebf73) Resetting hosts suitable for reconnect
2014-08-05 05:01:58,060 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
Timer:ctx-599ebf73) Completed resetting hosts suitable for reconnect
2014-08-05 05:01:58,060 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
Timer:ctx-599ebf73) Acquiring hosts for clusters already owned by this
management server
2014-08-05 05:01:58,061 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
Timer:ctx-599ebf73) Completed acquiring hosts for clusters already owned by
this management server
2014-08-05 05:01:58,061 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
Timer:ctx-599ebf73) Acquiring hosts for clusters not owned by any management
server
2014-08-05 05:01:58,061 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
[jira] [Created] (CLOUDSTACK-7256) test_06_destroy_vm smoke test failing due to incorrect expunge parameter
Doug Clark created CLOUDSTACK-7256: -- Summary: test_06_destroy_vm smoke test failing due to incorrect expunge parameter Key: CLOUDSTACK-7256 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7256 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: marvin Affects Versions: Future, 4.5.0 Reporter: Doug Clark Assignee: Doug Clark Priority: Blocker Fix For: Future, 4.5.0 test_06_destroy_vm smoke test fails because the test expunges the VM. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7256) test_06_destroy_vm smoke test failing due to incorrect expunge parameter
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Clark updated CLOUDSTACK-7256: --- https://reviews.apache.org/r/23986/ test_06_destroy_vm smoke test failing due to incorrect expunge parameter Key: CLOUDSTACK-7256 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7256 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: marvin Affects Versions: Future, 4.5.0 Reporter: Doug Clark Assignee: Doug Clark Priority: Blocker Fix For: Future, 4.5.0 Original Estimate: 2.4h Remaining Estimate: 2.4h test_06_destroy_vm smoke test fails because the test expunges the VM. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7159) Add state parameter to the listPublicIpAddresses API call
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14086456#comment-14086456
]
ASF subversion and git services commented on CLOUDSTACK-7159:
-
Commit 07f916dfc6fb30dc928b258beeaa761253e43ab9 in cloudstack's branch
refs/heads/master from [~svscorp]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=07f916d ]
CLOUDSTACK-7159 Added state parameter to the listPublicIpAddresses API call
Signed-off-by: Ilia Shakitko i.shaki...@tech.leaseweb.com
Signed-off-by: Rohit Yadav rohit.ya...@shapeblue.com
Add state parameter to the listPublicIpAddresses API call
-
Key: CLOUDSTACK-7159
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7159
Project: CloudStack
Issue Type: Improvement
Security Level: Public(Anyone can view this level - this is the
default.)
Components: API, Management Server
Reporter: Ilia Shakitko
Priority: Minor
Fix For: Future, 4.5.0
Few times we've faced an impedemence of having a list of Free
publicIpAddresses. You have to go thru all the IPs with (allocatedonly =
false) and filter out the Free once. It's not a big deal, but it's an extra
time and traffic between CloudStack and an API consumer.
It would be useful to have state parameter. In this case you can query API
like this:
{code}
list publicipaddresses forvirtualnetwork=false state=free
{code}
and have a list of Free publicIpAddresses.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-7211) system VM not coming up in LXC zone for rhel 6.x
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amogh Vasekar resolved CLOUDSTACK-7211. --- Resolution: Fixed system VM not coming up in LXC zone for rhel 6.x -- Key: CLOUDSTACK-7211 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7211 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.5.0 Reporter: shweta agarwal Assignee: Amogh Vasekar Priority: Blocker Fix For: 4.5.0 Attachments: MS.tar.gz, agent.tar.gz created a zone with LXC hypervisor on rhel 6.3 host Pre seeded the KVM template as LXC On enabling zone Syemt VMs are not coming up Agent log shows : ttempting to create storage pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,260 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create storage pool 4032a858-88b0-3c03-8477-8984eb6b390b (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,417 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create volume 1c123c1a-1873-11e4-87de-4524e40b898e (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,052 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to remove storage pool 4032a858-88b0-3c03-8477-8984eb6b390b from libvirt 2014-07-31 04:57:14,388 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Creating volume 75d88b46-1b93-4065-a348-460b8d3911fb from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:14,389 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Attempting to create volume 75d88b46-1b93-4065-a348-460b8d3911fb (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,948 WARN [cloud.agent.Agent] (agentRequest-Handler-3:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) 2014-07-31 04:57:15,700 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Creating volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:15,701 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Attempting to create volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:16,262 WARN [cloud.agent.Agent] (agentRequest-Handler-1:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7257) CLONE - system VM not coming up in LXC zone for rhel 6.x
Amogh Vasekar created CLOUDSTACK-7257: - Summary: CLONE - system VM not coming up in LXC zone for rhel 6.x Key: CLOUDSTACK-7257 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7257 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.5.0 Reporter: Amogh Vasekar Assignee: Amogh Vasekar Priority: Blocker Fix For: 4.5.0 created a zone with LXC hypervisor on rhel 6.3 host Pre seeded the KVM template as LXC On enabling zone Syemt VMs are not coming up Agent log shows : ttempting to create storage pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,260 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create storage pool 4032a858-88b0-3c03-8477-8984eb6b390b (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,417 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create volume 1c123c1a-1873-11e4-87de-4524e40b898e (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,052 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to remove storage pool 4032a858-88b0-3c03-8477-8984eb6b390b from libvirt 2014-07-31 04:57:14,388 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Creating volume 75d88b46-1b93-4065-a348-460b8d3911fb from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:14,389 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Attempting to create volume 75d88b46-1b93-4065-a348-460b8d3911fb (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,948 WARN [cloud.agent.Agent] (agentRequest-Handler-3:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) 2014-07-31 04:57:15,700 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Creating volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:15,701 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Attempting to create volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:16,262 WARN [cloud.agent.Agent] (agentRequest-Handler-1:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7257) CLONE - system VM not coming up in LXC zone for rhel 6.x
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amogh Vasekar updated CLOUDSTACK-7257: -- Affects Version/s: (was: 4.5.0) 4.4.0 CLONE - system VM not coming up in LXC zone for rhel 6.x -- Key: CLOUDSTACK-7257 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7257 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.4.0 Reporter: Amogh Vasekar Assignee: Amogh Vasekar Priority: Blocker Fix For: 4.4.1 created a zone with LXC hypervisor on rhel 6.3 host Pre seeded the KVM template as LXC On enabling zone Syemt VMs are not coming up Agent log shows : ttempting to create storage pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,260 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create storage pool 4032a858-88b0-3c03-8477-8984eb6b390b (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,417 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create volume 1c123c1a-1873-11e4-87de-4524e40b898e (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,052 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to remove storage pool 4032a858-88b0-3c03-8477-8984eb6b390b from libvirt 2014-07-31 04:57:14,388 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Creating volume 75d88b46-1b93-4065-a348-460b8d3911fb from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:14,389 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Attempting to create volume 75d88b46-1b93-4065-a348-460b8d3911fb (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,948 WARN [cloud.agent.Agent] (agentRequest-Handler-3:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) 2014-07-31 04:57:15,700 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Creating volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:15,701 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Attempting to create volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:16,262 WARN [cloud.agent.Agent] (agentRequest-Handler-1:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7257) CLONE - system VM not coming up in LXC zone for rhel 6.x
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amogh Vasekar updated CLOUDSTACK-7257: -- Fix Version/s: (was: 4.5.0) 4.4.1 CLONE - system VM not coming up in LXC zone for rhel 6.x -- Key: CLOUDSTACK-7257 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7257 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.4.0 Reporter: Amogh Vasekar Assignee: Amogh Vasekar Priority: Blocker Fix For: 4.4.1 created a zone with LXC hypervisor on rhel 6.3 host Pre seeded the KVM template as LXC On enabling zone Syemt VMs are not coming up Agent log shows : ttempting to create storage pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,260 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create storage pool 4032a858-88b0-3c03-8477-8984eb6b390b (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,417 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create volume 1c123c1a-1873-11e4-87de-4524e40b898e (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,052 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to remove storage pool 4032a858-88b0-3c03-8477-8984eb6b390b from libvirt 2014-07-31 04:57:14,388 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Creating volume 75d88b46-1b93-4065-a348-460b8d3911fb from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:14,389 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Attempting to create volume 75d88b46-1b93-4065-a348-460b8d3911fb (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,948 WARN [cloud.agent.Agent] (agentRequest-Handler-3:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) 2014-07-31 04:57:15,700 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Creating volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:15,701 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Attempting to create volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:16,262 WARN [cloud.agent.Agent] (agentRequest-Handler-1:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7257) CLONE - system VM not coming up in LXC zone for rhel 6.x
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14086471#comment-14086471 ] ASF subversion and git services commented on CLOUDSTACK-7257: - Commit e73e7c3939b0d5f427521df982c7b0c46bae3e0a in cloudstack's branch refs/heads/hotfix/4.4-7257 from [~amogh.vasekar] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e73e7c3 ] CLOUDSTACK-7257: Missing LXC mappings, reuse KVM mappings CLONE - system VM not coming up in LXC zone for rhel 6.x -- Key: CLOUDSTACK-7257 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7257 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.4.0 Reporter: Amogh Vasekar Assignee: Amogh Vasekar Priority: Blocker Fix For: 4.4.1 created a zone with LXC hypervisor on rhel 6.3 host Pre seeded the KVM template as LXC On enabling zone Syemt VMs are not coming up Agent log shows : ttempting to create storage pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,260 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create storage pool 4032a858-88b0-3c03-8477-8984eb6b390b (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,417 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create volume 1c123c1a-1873-11e4-87de-4524e40b898e (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,052 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to remove storage pool 4032a858-88b0-3c03-8477-8984eb6b390b from libvirt 2014-07-31 04:57:14,388 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Creating volume 75d88b46-1b93-4065-a348-460b8d3911fb from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:14,389 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Attempting to create volume 75d88b46-1b93-4065-a348-460b8d3911fb (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,948 WARN [cloud.agent.Agent] (agentRequest-Handler-3:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) 2014-07-31 04:57:15,700 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Creating volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:15,701 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Attempting to create volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:16,262 WARN [cloud.agent.Agent] (agentRequest-Handler-1:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at
[jira] [Commented] (CLOUDSTACK-7257) CLONE - system VM not coming up in LXC zone for rhel 6.x
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14086503#comment-14086503 ] ASF subversion and git services commented on CLOUDSTACK-7257: - Commit c02892a21c0266fda7b527b129bc2f8d33301812 in cloudstack's branch refs/heads/hotfix/4.4-7257b from [~amogh.vasekar] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c02892a ] CLOUDSTACK-7257: Missing LXC mappings, reuse KVM mappings CLONE - system VM not coming up in LXC zone for rhel 6.x -- Key: CLOUDSTACK-7257 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7257 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.4.0 Reporter: Amogh Vasekar Assignee: Amogh Vasekar Priority: Blocker Fix For: 4.4.1 created a zone with LXC hypervisor on rhel 6.3 host Pre seeded the KVM template as LXC On enabling zone Syemt VMs are not coming up Agent log shows : ttempting to create storage pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,260 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create storage pool 4032a858-88b0-3c03-8477-8984eb6b390b (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,417 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create volume 1c123c1a-1873-11e4-87de-4524e40b898e (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,052 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to remove storage pool 4032a858-88b0-3c03-8477-8984eb6b390b from libvirt 2014-07-31 04:57:14,388 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Creating volume 75d88b46-1b93-4065-a348-460b8d3911fb from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:14,389 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Attempting to create volume 75d88b46-1b93-4065-a348-460b8d3911fb (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,948 WARN [cloud.agent.Agent] (agentRequest-Handler-3:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) 2014-07-31 04:57:15,700 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Creating volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:15,701 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Attempting to create volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:16,262 WARN [cloud.agent.Agent] (agentRequest-Handler-1:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at
[jira] [Resolved] (CLOUDSTACK-7247) marvin deployVirtualMachine calls default to hypervisor=XenServer
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alena Prokharchyk resolved CLOUDSTACK-7247. --- Resolution: Fixed Should be fixed with: commit 2109418469e7434bfc13fce0a20d5464d0b7862f Author: Gaurav Aradhye gaurav.arad...@clogeny.com Date: Tue Aug 5 14:04:19 2014 +0530 Fixed Marvin Issue: Hypervisor value was hardcoded to XenServer while deploying VM if not specified Signed-off-by: Santhosh Edukulla santhosh.eduku...@gmail.com marvin deployVirtualMachine calls default to hypervisor=XenServer - Key: CLOUDSTACK-7247 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7247 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation, marvin Affects Versions: 4.5.0 Reporter: John Dilley Assignee: John Dilley Priority: Blocker Fix For: 4.5.0 Lots of failures in marvin since the fix for CLOUDSTACK-7194 now validates that the template hypervisor type and the deployVirtualMachine hypervisor match, or only one specifies a hypervisor. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-7257) CLONE - system VM not coming up in LXC zone for rhel 6.x
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amogh Vasekar resolved CLOUDSTACK-7257. --- Resolution: Fixed CLONE - system VM not coming up in LXC zone for rhel 6.x -- Key: CLOUDSTACK-7257 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7257 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.4.0 Reporter: Amogh Vasekar Assignee: Amogh Vasekar Priority: Blocker Fix For: 4.4.1 created a zone with LXC hypervisor on rhel 6.3 host Pre seeded the KVM template as LXC On enabling zone Syemt VMs are not coming up Agent log shows : ttempting to create storage pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,260 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create storage pool 4032a858-88b0-3c03-8477-8984eb6b390b (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,417 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create volume 1c123c1a-1873-11e4-87de-4524e40b898e (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,052 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to remove storage pool 4032a858-88b0-3c03-8477-8984eb6b390b from libvirt 2014-07-31 04:57:14,388 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Creating volume 75d88b46-1b93-4065-a348-460b8d3911fb from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:14,389 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Attempting to create volume 75d88b46-1b93-4065-a348-460b8d3911fb (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,948 WARN [cloud.agent.Agent] (agentRequest-Handler-3:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) 2014-07-31 04:57:15,700 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Creating volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:15,701 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Attempting to create volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:16,262 WARN [cloud.agent.Agent] (agentRequest-Handler-1:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7237) template sync unable to find already downloaded template after restarting MS
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14086517#comment-14086517
]
Alena Prokharchyk commented on CLOUDSTACK-7237:
---
Shweta, can you please attach management server log file to the bug?
template sync unable to find already downloaded template after restarting MS
-
Key: CLOUDSTACK-7237
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7237
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Template
Affects Versions: 4.5.0
Reporter: shweta agarwal
Assignee: Kishan Kavala
Priority: Blocker
Fix For: 4.5.0
Repro steps:
1. created an advance zone
2. Register a template
3. Wait till download is complete and template in ready state
4. Restart MS
5. wait for template sync to happen
Bug:
template sync says Template Sync did not find
206-2-832d2ef8-9355-3958-9331-0847b502ad2a on image store 1, may request
download based on available hypervisor types
MS log to show template 206-2-832d2ef8-9355-3958-9331-0847b502ad2a was
downloaded successfully before restarting MS
2014-08-04 08:02:50,676 DEBUG [o.a.c.s.i.TemplateDataFactoryImpl]
(Work-Job-Executor-1:ctx-2494f7c7 job-121/job-122 ctx-7f2fe1fe) template 206
is already in store:1, type:Primary
2014-08-04 08:02:50,677 DEBUG [o.a.c.s.v.VolumeServiceImpl]
(Work-Job-Executor-1:ctx-2494f7c7 job-121/job-122 ctx-7f2fe1fe) Found
template 206-2-832d2ef8-9355-3958-9331-0847b502ad2a in storage pool 1 with
VMTemplateStoragePool id: 7
2014-08-04 08:02:50,686 DEBUG [o.a.c.s.v.VolumeServiceImpl]
(Work-Job-Executor-1:ctx-2494f7c7 job-121/job-122 ctx-7f2fe1fe) Acquire lock
on VMTemplateStoragePool 7 with timeout 3600 seconds
2014-08-04 08:02:50,688 INFO [o.a.c.s.v.VolumeServiceImpl]
(Work-Job-Executor-1:ctx-2494f7c7 job-121/job-122 ctx-7f2fe1fe) lock is
acquired for VMTemplateStoragePool 7
2014-08-04 08:02:50,776 DEBUG [o.a.c.s.m.AncientDataMotionStrategy]
(Work-Job-Executor-1:ctx-2494f7c7 job-121/job-122 ctx-7f2fe1fe) copyAsync
inspecting src type TEMPLATE copyAsync inspecting dest type TEMPLATE
2014-08-04 08:02:50,790 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-1:ctx-2494f7c7 job-121/job-122 ctx-7f2fe1fe) Seq
1-7372392590005502037: Sending { Cmd , MgmtId: 233845177509765, via:
1(Rack1Pod1Host23), Ver: v1, Flags: 100011,
[{org.apache.cloudstack.storage.command.CopyCommand:{srcTO:{org.apache.cloudstack.storage.to.TemplateObjectTO:{path:template/tmpl/2/206/2dd5a66f-96a8-3871-bce4-748777aa6529.tar,origUrl:http://10.147.28.7/templates/lxc-templates/debian.tar.gz,uuid:005df498-a1fe-4f69-ac27-53a762891389,id:206,format:TAR,accountId:2,checksum:6d2578f600440f302425839978220b32,hvm:false,displayText:deb-final,imageDataStore:{com.cloud.agent.api.to.NfsTO:{_url:nfs://10.147.28.7/export/home/shweta/goleta.lxc.secondary,_role:Image}},name:206-2-832d2ef8-9355-3958-9331-0847b502ad2a,hypervisorType:LXC}},destTO:{org.apache.cloudstack.storage.to.TemplateObjectTO:{origUrl:http://10.147.28.7/templates/lxc-templates/debian.tar.gz,uuid:005df498-a1fe-4f69-ac27-53a762891389,id:206,format:TAR,accountId:2,checksum:6d2578f600440f302425839978220b32,hvm:false,displayText:deb-final,imageDataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:dfa2ec3c-d133-3284-8583-0a0845aa4424,id:1,poolType:NetworkFilesystem,host:10.147.28.7,path:/export/home/shweta/goleta.lxc.primary,port:2049,url:NetworkFilesystem://10.147.28.7/export/home/shweta/goleta.lxc.primary/?ROLE=PrimarySTOREUUID=dfa2ec3c-d133-3284-8583-0a0845aa4424}},name:206-2-832d2ef8-9355-3958-9331-0847b502ad2a,hypervisorType:LXC}},executeInSequence:false,options:{},wait:10800}}]
}
2014-08-04 08:02:51,092 DEBUG [c.c.a.t.Request] (AgentManager-Handler-1:null)
Seq 1-7372392590005502037: Processing: { Ans: , MgmtId: 233845177509765,
via: 1, Ver: v1, Flags: 10,
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{newData:{org.apache.cloudstack.storage.to.TemplateObjectTO:{path:005df498-a1fe-4f69-ac27
.
.
.
.
.
after restart MS log shows
2014-08-04 08:07:20,606 INFO [o.a.c.s.i.TemplateServiceImpl]
(AgentConnectTaskPool-6:ctx-5d641ba5) Template Sync did not find routing-8 on
image store 1, may request download based on available hypervisor types
2014-08-04 08:07:20,606 INFO [o.a.c.s.i.TemplateServiceImpl]
(AgentConnectTaskPool-6:ctx-5d641ba5) Template Sync did not find routing-9 on
image store 1, may request download based on available hypervisor types
2014-08-04 08:07:20,607 INFO [o.a.c.s.i.TemplateServiceImpl]
(AgentConnectTaskPool-6:ctx-5d641ba5) Template Sync found routing-10 already
in the image store
2014-08-04 08:07:20,694
[jira] [Assigned] (CLOUDSTACK-7238) [Automation] SQL exceptions seen in the runs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alena Prokharchyk reassigned CLOUDSTACK-7238: - Assignee: Alena Prokharchyk [Automation] SQL exceptions seen in the runs Key: CLOUDSTACK-7238 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7238 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.5.0 Reporter: Raja Pullela Assignee: Alena Prokharchyk Priority: Critical Attachments: simu_mgmt_log.txt Following SQL exceptions are seen the management server log: 2014-08-01 20:04:35,194 DEBUG [c.c.s.d.VMTemplateDaoImpl] (main:null) Found parameter routing unique name null 2014-08-01 20:04:35,194 DEBUG [c.c.s.d.VMTemplateDaoImpl] (main:null) Use console proxy template : routing 2014-08-01 20:04:35,229 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Caught exception when inserting system account: Duplicate entry '1' for key 'PRIMARY' 2014-08-01 20:04:35,231 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Caught SQLException when inserting system user: Duplicate entry '1' for key 'PRIMARY' 2014-08-01 20:04:35,231 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Caught SQLException when creating admin account: Duplicate entry '2' for key 'PRIMARY' 2014-08-01 20:04:35,232 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Caught SQLException when inserting admin user: Duplicate entry '2' for key 'PRIMARY' 2014-08-01 20:04:35,233 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Caught (SQL?)Exception: no network_group Table 'cloud.network_group' doesn't exist 2014-08-01 20:04:35,238 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) ConfigurationServer is saving default values to the database. 2014-08-01 20:04:36,808 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) ConfigurationServer made secondary storage vm required. 2014-08-01 20:04:36,811 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) ConfigurationServer made secondary storage copy encrypt set to false. 2014-08-01 20:04:36,818 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) ConfigurationServer made secondary storage copy use realhostip. 2014-08-01 20:04:36,909 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) ConfigurationServer saved /mnt as mount.parent. 2014-08-01 20:04:36,915 DEBUG [c.c.u.s.Script] (main:null) Executing: /bin/bash -c /sbin/route | grep default 2014-08-01 20:04:36,955 DEBUG [c.c.u.s.Script] (main:null) Execution is successful. 2014-08-01 20:04:36,967 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) ConfigurationServer saved 172.16.88.23 as host. 2014-08-01 20:04:37,612 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) resource_count table has records missing for some domains...going to insert them 2014-08-01 20:04:37,624 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Inserting resource count of type user_vm for domain id=1 2014-08-01 20:04:37,626 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Inserting resource count of type public_ip for domain id=1 2014-08-01 20:04:37,627 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Inserting resource count of type -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-7238) [Automation] SQL exceptions seen in the runs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alena Prokharchyk resolved CLOUDSTACK-7238. --- Resolution: Duplicate [Automation] SQL exceptions seen in the runs Key: CLOUDSTACK-7238 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7238 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.5.0 Reporter: Raja Pullela Assignee: Alena Prokharchyk Priority: Critical Attachments: simu_mgmt_log.txt Following SQL exceptions are seen the management server log: 2014-08-01 20:04:35,194 DEBUG [c.c.s.d.VMTemplateDaoImpl] (main:null) Found parameter routing unique name null 2014-08-01 20:04:35,194 DEBUG [c.c.s.d.VMTemplateDaoImpl] (main:null) Use console proxy template : routing 2014-08-01 20:04:35,229 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Caught exception when inserting system account: Duplicate entry '1' for key 'PRIMARY' 2014-08-01 20:04:35,231 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Caught SQLException when inserting system user: Duplicate entry '1' for key 'PRIMARY' 2014-08-01 20:04:35,231 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Caught SQLException when creating admin account: Duplicate entry '2' for key 'PRIMARY' 2014-08-01 20:04:35,232 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Caught SQLException when inserting admin user: Duplicate entry '2' for key 'PRIMARY' 2014-08-01 20:04:35,233 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Caught (SQL?)Exception: no network_group Table 'cloud.network_group' doesn't exist 2014-08-01 20:04:35,238 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) ConfigurationServer is saving default values to the database. 2014-08-01 20:04:36,808 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) ConfigurationServer made secondary storage vm required. 2014-08-01 20:04:36,811 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) ConfigurationServer made secondary storage copy encrypt set to false. 2014-08-01 20:04:36,818 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) ConfigurationServer made secondary storage copy use realhostip. 2014-08-01 20:04:36,909 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) ConfigurationServer saved /mnt as mount.parent. 2014-08-01 20:04:36,915 DEBUG [c.c.u.s.Script] (main:null) Executing: /bin/bash -c /sbin/route | grep default 2014-08-01 20:04:36,955 DEBUG [c.c.u.s.Script] (main:null) Execution is successful. 2014-08-01 20:04:36,967 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) ConfigurationServer saved 172.16.88.23 as host. 2014-08-01 20:04:37,612 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) resource_count table has records missing for some domains...going to insert them 2014-08-01 20:04:37,624 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Inserting resource count of type user_vm for domain id=1 2014-08-01 20:04:37,626 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Inserting resource count of type public_ip for domain id=1 2014-08-01 20:04:37,627 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Inserting resource count of type -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7258) System accounts/users are tried to be inserted twice on RPM setup
Alena Prokharchyk created CLOUDSTACK-7258: - Summary: System accounts/users are tried to be inserted twice on RPM setup Key: CLOUDSTACK-7258 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7258 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.5.0 Reporter: Alena Prokharchyk Fix For: Future In the developer setup, initial CS configuration - inserting system/admin user, account - is done in ConfigurationServerImpl class - on the MS startup. As opposed to that, in RPM setup (the one that QA and customers use), the initial setup is first done by calling cloud-setup-databases before the MS start, which in turn calls DataBaseConfig.java. DataBaseConfig.java inserts system users. Then when MS starts, ConfigurationServerImpl code tries to insert the same system/admin users again - and it fails as those users are already inserted. Currently we handle it by simply catching and logging mysql exceptions in DEBUG mode. We should fix the installation process so the user is inserted only once; and change the logic in ConfigurationServer - instead of logging the exception, we should throw the RuntimeException indicating that essential CS configuration failed, and that exception should fail MS startup. That would be a big change that has to be well tested through. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7259) KVM mappings for CentOS 6.x and RHEL 6.x
Amogh Vasekar created CLOUDSTACK-7259: - Summary: KVM mappings for CentOS 6.x and RHEL 6.x Key: CLOUDSTACK-7259 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7259 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.4.0, 4.5.0 Reporter: Amogh Vasekar Assignee: Amogh Vasekar Priority: Blocker Fix For: 4.4.0, 4.5.0 Add missing KVM mappings for CentOS 6 and RHEL 6 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-7259) KVM mappings for CentOS 6.x and RHEL 6.x
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amogh Vasekar resolved CLOUDSTACK-7259. --- Resolution: Fixed KVM mappings for CentOS 6.x and RHEL 6.x Key: CLOUDSTACK-7259 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7259 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.4.0, 4.5.0 Reporter: Amogh Vasekar Assignee: Amogh Vasekar Priority: Blocker Fix For: 4.4.0, 4.5.0 Add missing KVM mappings for CentOS 6 and RHEL 6 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7218) [Automation] NPE observed while deleting account in automation run
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14086533#comment-14086533 ] Animesh Chaturvedi commented on CLOUDSTACK-7218: Jayapal what is the ETA on fix? [Automation] NPE observed while deleting account in automation run -- Key: CLOUDSTACK-7218 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7218 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.5.0 Environment: KVM (RHEL 6.3) Reporter: Rayees Namathponnan Assignee: Jayapal Reddy Priority: Critical Fix For: 4.5.0 This issue is observed in automation log, NPE thrown while deleting account 2014-07-31 02:20:56,102 DEBUG [c.c.n.r.RulesManagerImpl] (API-Job-Executor-2:ctx-523291d6 job-5302 ctx-28b51397) There are no static nat rules to apply for ip id=28 2014-07-31 02:20:56,105 WARN [c.c.u.AccountManagerImpl] (API-Job-Executor-2:ctx-523291d6 job-5302 ctx-28b51397) Failed to cleanup accou nt Acct[b1cf2381-ab36-4ebc-90ff-f08acaf5e02d-test-account-TestVmNetworkOperations-test_add_static_nat_rule_1_ISOLATED-YI0OCS] due to java.lang.NullPointerException at com.cloud.network.rules.RulesManagerImpl.createStaticNatForIp(RulesManagerImpl.java:1391) at com.cloud.network.rules.RulesManagerImpl.applyStaticNatForIp(RulesManagerImpl.java:1321) at com.cloud.network.rules.RulesManagerImpl.revokeAllPFAndStaticNatRulesForIp(RulesManagerImpl.java:1104) at sun.reflect.GeneratedMethodAccessor524.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at com.sun.proxy.$Proxy105.revokeAllPFAndStaticNatRulesForIp(Unknown Source) at com.cloud.network.IpAddressManagerImpl.cleanupIpResources(IpAddressManagerImpl.java:540) at com.cloud.network.IpAddressManagerImpl.applyIpAssociations(IpAddressManagerImpl.java:936) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.cleanupNetworkResources(NetworkOrchestrator.java:2650) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.destroyNetwork(NetworkOrchestrator.java:2196) at com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:793) at com.cloud.user.AccountManagerImpl.deleteAccount(AccountManagerImpl.java:667) at com.cloud.user.AccountManagerImpl.deleteUserAccount(AccountManagerImpl.java:1441) at sun.reflect.GeneratedMethodAccessor542.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at
[jira] [Commented] (CLOUDSTACK-7259) KVM mappings for CentOS 6.x and RHEL 6.x
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14086546#comment-14086546 ] Amogh Vasekar commented on CLOUDSTACK-7259: --- Fixed in cfcc4a076dd740d6deed48084132946a55ed08d1 in master Fixed in d3e0ecd130dbdd196e71be1eb32f92d4be6fdd2e in 4.4 Thanks Amogh KVM mappings for CentOS 6.x and RHEL 6.x Key: CLOUDSTACK-7259 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7259 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.4.0, 4.5.0 Reporter: Amogh Vasekar Assignee: Amogh Vasekar Priority: Blocker Fix For: 4.4.0, 4.5.0 Add missing KVM mappings for CentOS 6 and RHEL 6 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6717) [OVS][UI]VPC network creation page does not display custom network offering created for vpc
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14086554#comment-14086554
]
Alena Prokharchyk commented on CLOUDSTACK-6717:
---
This is the call that UI makes to grab all the network offerings for display.
http://localhost:8080/client/api?command=listNetworkOfferingsresponse=jsonsessionkey=3WUlDxr5xt3AeoHACIEz1nMtOxI%3Dforvpc=trueguestiptype=IsolatedsupportedServices=SourceNatstate=Enabled_=1407261327743
Note that special parameters are passed to the call:
1) guestIpType=Isolated
2) supportedServices=SourceNat
3) forVpc=true
First and second parameters are defined on the network offering itself, so it
should be easy to check if your offering satisfies this criteria.
Third parameter triggers following check in the java code:
@Override
public boolean isOfferingForVpc(NetworkOffering offering) {
boolean vpcProvider =
_ntwkOffServiceMapDao.isProviderForNetworkOffering(offering.getId(),
Provider.VPCVirtualRouter) ||
_ntwkOffServiceMapDao.isProviderForNetworkOffering(offering.getId(),
Provider.JuniperContrailVpcRouter) ||
_ntwkOffServiceMapDao.getDistinctProviders(offering.getId()).contains(Provider.NuageVsp.getName());
return vpcProvider;
}
If your offering has the providers within this list, then it can be used in the
VPC.
[OVS][UI]VPC network creation page does not display custom network offering
created for vpc
---
Key: CLOUDSTACK-6717
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6717
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: UI
Affects Versions: 4.4.0
Environment: Latest build from 4.4 branch with commit
e6961fd21bb6d793302c234d0f409f66dc498072
Reporter: Sanjeev N
Assignee: Sanjeev N
Priority: Critical
Fix For: 4.4.0
Attachments: vpc_tier.PNG
[SDN][UI]VPC network creation page does not display custom network offering
created for vpc
Steps to Reproduce:
1.Bring up CS in advanced zone with xen cluster
2.Create physical network with GRE isolation
3.Create Region level vpc
4.Create isolated network offering for vpc with virtualnetworking service and
ovs as the service provider
5.Enable the network offering
6.In region level vpc try to create tier with above created network offering
Result:
==
Add tier in VPC page does not display the custom vpc offering created with
ovs provider. It only shows the default vpc offerings in the drop down list.
Attaching screen shot to describe the issue.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7218) [Automation] NPE observed while deleting account in automation run
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14086564#comment-14086564 ] Alena Prokharchyk commented on CLOUDSTACK-7218: --- Jayapal, note that we shoudln't just fix the cleanup part, but do the following: Fix all the places where we expect vm to have just one static nat rule enabled: * either by replacing all findByAssociatedVmId() Dao method with findByAssociatedVmIdAndVmIp. And getting rid of findByAssociatedVmId() method returning just one entry or * by changing the findByAssociatedVmId() to return the array of the ips rather than single ip [Automation] NPE observed while deleting account in automation run -- Key: CLOUDSTACK-7218 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7218 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.5.0 Environment: KVM (RHEL 6.3) Reporter: Rayees Namathponnan Assignee: Jayapal Reddy Priority: Critical Fix For: 4.5.0 This issue is observed in automation log, NPE thrown while deleting account 2014-07-31 02:20:56,102 DEBUG [c.c.n.r.RulesManagerImpl] (API-Job-Executor-2:ctx-523291d6 job-5302 ctx-28b51397) There are no static nat rules to apply for ip id=28 2014-07-31 02:20:56,105 WARN [c.c.u.AccountManagerImpl] (API-Job-Executor-2:ctx-523291d6 job-5302 ctx-28b51397) Failed to cleanup accou nt Acct[b1cf2381-ab36-4ebc-90ff-f08acaf5e02d-test-account-TestVmNetworkOperations-test_add_static_nat_rule_1_ISOLATED-YI0OCS] due to java.lang.NullPointerException at com.cloud.network.rules.RulesManagerImpl.createStaticNatForIp(RulesManagerImpl.java:1391) at com.cloud.network.rules.RulesManagerImpl.applyStaticNatForIp(RulesManagerImpl.java:1321) at com.cloud.network.rules.RulesManagerImpl.revokeAllPFAndStaticNatRulesForIp(RulesManagerImpl.java:1104) at sun.reflect.GeneratedMethodAccessor524.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at com.sun.proxy.$Proxy105.revokeAllPFAndStaticNatRulesForIp(Unknown Source) at com.cloud.network.IpAddressManagerImpl.cleanupIpResources(IpAddressManagerImpl.java:540) at com.cloud.network.IpAddressManagerImpl.applyIpAssociations(IpAddressManagerImpl.java:936) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.cleanupNetworkResources(NetworkOrchestrator.java:2650) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.destroyNetwork(NetworkOrchestrator.java:2196) at com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:793) at com.cloud.user.AccountManagerImpl.deleteAccount(AccountManagerImpl.java:667) at com.cloud.user.AccountManagerImpl.deleteUserAccount(AccountManagerImpl.java:1441) at sun.reflect.GeneratedMethodAccessor542.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51) at
[jira] [Commented] (CLOUDSTACK-6278) Baremetal Advanced Networking support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14086568#comment-14086568 ] ASF subversion and git services commented on CLOUDSTACK-6278: - Commit 12ad254069c067761b0132ad6ca76dd90c81b0ce in cloudstack's branch refs/heads/master from [~frank.zhang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=12ad254 ] CLOUDSTACK-6278 Baremetal Advanced Networking support add missing license header Baremetal Advanced Networking support - Key: CLOUDSTACK-6278 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6278 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: Baremetal Affects Versions: 4.5.0 Reporter: frank zhang Assignee: frank zhang Fix For: 4.5.0 functional spec link: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Baremetal+Advanced+Networking+Support -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7012) [Atomation] Vcenter Hang during 4.4 automation runs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14086583#comment-14086583 ] Rayees Namathponnan commented on CLOUDSTACK-7012: - Logs https://citrix.sharefile.com/d/s179784729e94ca88 [Atomation] Vcenter Hang during 4.4 automation runs --- Key: CLOUDSTACK-7012 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7012 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.4.0, 4.5.0 Environment: VCenter 5.0 Exi 5.0 Reporter: Rayees Namathponnan Assignee: Sateesh Chodapuneedi Priority: Blocker Fix For: 4.5.0 Attachments: catalina.rar This issue observed with 4.4 automation run with Vcenter 5.0, during BVT run VM deployment fail, if you try to connect VCenter from console gets below error Call ServiceInstance.RetrieveContent for object ServiceInstance on Server 10.223.52.12 failed. I was using same VCenter more 1.5 year, i never faced this issue earlier, then i tried to run automation with 4.2 and 4.3 build last week i didnt observe this issue, i think some of the changes in CS 4.4 causing VCenter to hang Observed below error in MS Log INFO [c.c.h.v.u.VmwareContext] (DirectAgentCronJob-455:ctx-71dce779) New VmwareContext object, current outstanding count: 451 INFO [c.c.h.v.r.VmwareResource] (DirectAgentCronJob-455:ctx-71dce779) Scan hung worker VM to recycle INFO [c.c.h.v.u.VmwareContext] (DirectAgent-17:ctx-d197a13b 10.223.250.131) New VmwareContext object, current outstanding count: 452 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6695) UI should allow uploading chained SSL certificates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-6695: Fix Version/s: (was: Future) 4.5.0 UI should allow uploading chained SSL certificates --- Key: CLOUDSTACK-6695 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6695 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.3.0, 4.4.0 Reporter: Amogh Vasekar Assignee: Mihaela Stoica Priority: Critical Fix For: 4.4.0, 4.5.0 Currently, to upload chained certificates into CloudStack for SSVM / CPVM requires making API calls with right id and alias parameter. The UI only supports adding the server certificate, and should be enhanced to support adding the whole chain. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7261) CLONE UI - listSystemVMs API and listRouters API fail to return hypervisor property
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-7261: Component/s: (was: API) UI CLONE UI - listSystemVMs API and listRouters API fail to return hypervisor property Key: CLOUDSTACK-7261 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7261 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Reporter: Nitin Mehta Assignee: Nitin Mehta Priority: Critical Fix For: 4.5.0 listSystemVMs API and listRouters API doesn't return hypervisor property and this is important for scalevm operation, since its not implemented for all the hypervisors -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7261) CLONE UI - listSystemVMs API and listRouters API fail to return hypervisor property
Nitin Mehta created CLOUDSTACK-7261: --- Summary: CLONE UI - listSystemVMs API and listRouters API fail to return hypervisor property Key: CLOUDSTACK-7261 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7261 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: Nitin Mehta Assignee: Nitin Mehta Priority: Critical Fix For: 4.5.0 listSystemVMs API and listRouters API doesn't return hypervisor property and this is important for scalevm operation, since its not implemented for all the hypervisors -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-4200) listSystemVMs API and listRouters API fail to return hypervisor property
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta resolved CLOUDSTACK-4200. - Resolution: Fixed listSystemVMs API and listRouters API fail to return hypervisor property - Key: CLOUDSTACK-4200 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4200 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: Nitin Mehta Assignee: Nitin Mehta Priority: Critical Fix For: 4.5.0 listSystemVMs API and listRouters API doesn't return hypervisor property and this is important for scalevm operation, since its not implemented for all the hypervisors -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7261) CLONE UI - listSystemVMs API and listRouters API fail to return hypervisor property
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-7261: Assignee: Jessica Wang (was: Nitin Mehta) CLONE UI - listSystemVMs API and listRouters API fail to return hypervisor property Key: CLOUDSTACK-7261 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7261 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Reporter: Nitin Mehta Assignee: Jessica Wang Priority: Critical Fix For: 4.5.0 listSystemVMs API and listRouters API doesn't return hypervisor property and this is important for scalevm operation, since its not implemented for all the hypervisors -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-4200) listSystemVMs API and listRouters API fail to return hypervisor property
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14087026#comment-14087026 ] ASF subversion and git services commented on CLOUDSTACK-4200: - Commit b9d834e83854009483f6d061f9996e5ffaa9b883 in cloudstack's branch refs/heads/master from [~nitinme] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b9d834e ] CLOUDSTACK-4200: listSystemVMs API and listRouters API should return hypervisor property since dynamic scaling is not enabled for all the hypervisors and that action can be showed only for the hypervisors that support it. listSystemVMs API and listRouters API fail to return hypervisor property - Key: CLOUDSTACK-4200 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4200 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: Nitin Mehta Assignee: Nitin Mehta Priority: Critical Fix For: 4.5.0 listSystemVMs API and listRouters API doesn't return hypervisor property and this is important for scalevm operation, since its not implemented for all the hypervisors -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7261) CLONE UI - listSystemVMs API and listRouters API fail to return hypervisor property
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14087028#comment-14087028 ] Nitin Mehta commented on CLOUDSTACK-7261: - Based on CLOUDSTACK-4200 assigning this to Jessica. CLONE UI - listSystemVMs API and listRouters API fail to return hypervisor property Key: CLOUDSTACK-7261 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7261 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Reporter: Nitin Mehta Assignee: Nitin Mehta Priority: Critical Fix For: 4.5.0 listSystemVMs API and listRouters API doesn't return hypervisor property and this is important for scalevm operation, since its not implemented for all the hypervisors -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7260) Management server not responding after some time for Vmware due to Oom (cannot create native thread)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14087033#comment-14087033 ] ASF subversion and git services commented on CLOUDSTACK-7260: - Commit 9866c648eb5e6ce6ded1b6dcadbb77240fe0e683 in cloudstack's branch refs/heads/master from [~minchen07] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9866c64 ] CLOUDSTACK-7260: Management server not responding after some time for Vmware due to Oom (cannot create native thread). Management server not responding after some time for Vmware due to Oom (cannot create native thread) Key: CLOUDSTACK-7260 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7260 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.2.0 Reporter: Min Chen Assignee: Min Chen Priority: Blocker Fix For: 4.5.0 For a deployment with many hosts, 1 hour after starting management server is not responding well (very slow) and UI also hung. User is unable to deploy VM. In the MS log, we can see this happening: 2014-07-27 00:47:32,139 ERROR [o.a.c.f.j.i.AsyncJobManagerImpl] (AsyncJobMgr-Heartbeat-1:ctx-06c59569) Unexpected exception when trying to execute queue item, java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-7260) Management server not responding after some time for Vmware due to Oom (cannot create native thread)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Min Chen resolved CLOUDSTACK-7260. -- Resolution: Fixed Management server not responding after some time for Vmware due to Oom (cannot create native thread) Key: CLOUDSTACK-7260 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7260 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.2.0 Reporter: Min Chen Assignee: Min Chen Priority: Blocker Fix For: 4.5.0 For a deployment with many hosts, 1 hour after starting management server is not responding well (very slow) and UI also hung. User is unable to deploy VM. In the MS log, we can see this happening: 2014-07-27 00:47:32,139 ERROR [o.a.c.f.j.i.AsyncJobManagerImpl] (AsyncJobMgr-Heartbeat-1:ctx-06c59569) Unexpected exception when trying to execute queue item, java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6933) [Automation] Registering an iso fails in KVM deployment.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] frank zhang resolved CLOUDSTACK-6933. - Resolution: Won't Fix [Automation] Registering an iso fails in KVM deployment. Key: CLOUDSTACK-6933 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6933 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.4.0 Environment: KVM advanced network Reporter: Bharat Kumar Assignee: frank zhang Fix For: 4.4.0 registing an iso fails with the connection refused error in KVM deployment. below are the iptable rules on the relevant SSVM in the env. Chain INPUT (policy DROP 28 packets, 1340 bytes) pkts bytes target prot opt in out source destination 0 0 ACCEPT tcp -- eth2 * 0.0.0.0/00.0.0.0/0 state NEW tcp dpt:443 0 0 ACCEPT tcp -- eth2 * 0.0.0.0/00.0.0.0/0 state NEW tcp dpt:80 0 0 ACCEPT tcp -- eth1 * 0.0.0.0/00.0.0.0/0 state NEW tcp dpt:3922 172 13277 ACCEPT all -- eth0 * 0.0.0.0/00.0.0.0/0 state RELATED,ESTABLISHED 4122 469K ACCEPT all -- eth1 * 0.0.0.0/00.0.0.0/0 state RELATED,ESTABLISHED 196 10976 ACCEPT all -- eth2 * 0.0.0.0/00.0.0.0/0 state RELATED,ESTABLISHED 0 0 ACCEPT all -- eth3 * 0.0.0.0/00.0.0.0/0 state RELATED,ESTABLISHED 0 0 ACCEPT all -- lo * 0.0.0.0/00.0.0.0/0 0 0 DROP icmp -- * * 0.0.0.0/00.0.0.0/0 icmptype 13 0 0 ACCEPT icmp -- * * 0.0.0.0/00.0.0.0/0 3 180 ACCEPT tcp -- eth0 * 0.0.0.0/00.0.0.0/0 state NEW tcp dpt:3922 Chain FORWARD (policy DROP 0 packets, 0 bytes) pkts bytes target prot opt in out source destination Chain OUTPUT (policy ACCEPT 511 packets, 81586 bytes) pkts bytes target prot opt in out source destination 0 0 ACCEPT tcp -- * eth10.0.0.0/0 172.16.88.0/24 state NEW tcp 2576 155K ACCEPT tcp -- * eth10.0.0.0/0 172.16.88.0/24 state NEW tcp 0 0 REJECT tcp -- * eth10.0.0.0/00.0.0.0/0 state NEW tcp dpt:80 reject-with icmp-port-unreachable 0 0 REJECT tcp -- * eth10.0.0.0/00.0.0.0/0 state NEW tcp dpt:443 reject-with icmp-port-unreachable Chain HTTP (0 references) pkts bytes target prot opt in out source destination root@s-54-QA:~# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 172.16.171.10.0.0.0 UG0 00 eth2 169.254.0.0 0.0.0.0 255.255.0.0 U 0 00 eth0 172.16.88.0 0.0.0.0 255.255.255.0 U 0 00 eth1 172.16.88.0 0.0.0.0 255.255.255.0 U 0 00 eth3 172.16.171.00.0.0.0 255.255.255.0 U 0 00 eth2 As per the above config when a packet is sent to 172.16.88.x/24 subnet we are routing it via interface eth1. but we also have a reject rule in the OUTPUT chain for the packets leaving from eth1. as a result the packets get dropped. if we interchange the routes i.e. if the route related to eth3 is hit before hitting the eth1 route the register iso is successful. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6933) [Automation] Registering an iso fails in KVM deployment.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14087034#comment-14087034 ] frank zhang commented on CLOUDSTACK-6933: - This is a corner case in storage network. The storage network is designed to have a separate subnet from management subnet, however, we also allow mgmt network and storage network to be the same subnet in case customer only has one network for both purpose. In this case, you must set global setting secstorage.allowed.internal.sites to a smaller CIDR than mgmt network CIDR. The best practice is to set it to ip to secondary storage. By doing so, the routing issue is solved because Linux routing use most specific match. [Automation] Registering an iso fails in KVM deployment. Key: CLOUDSTACK-6933 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6933 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.4.0 Environment: KVM advanced network Reporter: Bharat Kumar Assignee: frank zhang Fix For: 4.4.0 registing an iso fails with the connection refused error in KVM deployment. below are the iptable rules on the relevant SSVM in the env. Chain INPUT (policy DROP 28 packets, 1340 bytes) pkts bytes target prot opt in out source destination 0 0 ACCEPT tcp -- eth2 * 0.0.0.0/00.0.0.0/0 state NEW tcp dpt:443 0 0 ACCEPT tcp -- eth2 * 0.0.0.0/00.0.0.0/0 state NEW tcp dpt:80 0 0 ACCEPT tcp -- eth1 * 0.0.0.0/00.0.0.0/0 state NEW tcp dpt:3922 172 13277 ACCEPT all -- eth0 * 0.0.0.0/00.0.0.0/0 state RELATED,ESTABLISHED 4122 469K ACCEPT all -- eth1 * 0.0.0.0/00.0.0.0/0 state RELATED,ESTABLISHED 196 10976 ACCEPT all -- eth2 * 0.0.0.0/00.0.0.0/0 state RELATED,ESTABLISHED 0 0 ACCEPT all -- eth3 * 0.0.0.0/00.0.0.0/0 state RELATED,ESTABLISHED 0 0 ACCEPT all -- lo * 0.0.0.0/00.0.0.0/0 0 0 DROP icmp -- * * 0.0.0.0/00.0.0.0/0 icmptype 13 0 0 ACCEPT icmp -- * * 0.0.0.0/00.0.0.0/0 3 180 ACCEPT tcp -- eth0 * 0.0.0.0/00.0.0.0/0 state NEW tcp dpt:3922 Chain FORWARD (policy DROP 0 packets, 0 bytes) pkts bytes target prot opt in out source destination Chain OUTPUT (policy ACCEPT 511 packets, 81586 bytes) pkts bytes target prot opt in out source destination 0 0 ACCEPT tcp -- * eth10.0.0.0/0 172.16.88.0/24 state NEW tcp 2576 155K ACCEPT tcp -- * eth10.0.0.0/0 172.16.88.0/24 state NEW tcp 0 0 REJECT tcp -- * eth10.0.0.0/00.0.0.0/0 state NEW tcp dpt:80 reject-with icmp-port-unreachable 0 0 REJECT tcp -- * eth10.0.0.0/00.0.0.0/0 state NEW tcp dpt:443 reject-with icmp-port-unreachable Chain HTTP (0 references) pkts bytes target prot opt in out source destination root@s-54-QA:~# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 172.16.171.10.0.0.0 UG0 00 eth2 169.254.0.0 0.0.0.0 255.255.0.0 U 0 00 eth0 172.16.88.0 0.0.0.0 255.255.255.0 U 0 00 eth1 172.16.88.0 0.0.0.0 255.255.255.0 U 0 00 eth3 172.16.171.00.0.0.0 255.255.255.0 U 0 00 eth2 As per the above config when a packet is sent to 172.16.88.x/24 subnet we are routing it via interface eth1. but we also have a reject rule in the OUTPUT chain for the packets leaving from eth1. as a result the packets get dropped. if we interchange the routes i.e. if the route related to eth3 is hit before hitting the eth1 route the register iso is successful. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7262) Affinity Groups UI Icon is wrong
Tanner Danzey created CLOUDSTACK-7262: - Summary: Affinity Groups UI Icon is wrong Key: CLOUDSTACK-7262 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7262 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server, UI Affects Versions: 4.4.0 Environment: Chrome 35, Ubuntu Server 14.04 LTS Reporter: Tanner Danzey Priority: Trivial Attachments: 2014-08-05 23_09_53-CloudStack.png, 2014-08-05 23_11_10-CloudStack.png The hover icon for Affinity Groups is the one for Instances. Additionally, the non-hover icon has a white border around it, which none of the other icons have. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7262) Affinity Groups UI Icon is wrong
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanner Danzey updated CLOUDSTACK-7262: -- Attachment: 2014-08-05 23_11_10-CloudStack.png 2014-08-05 23_09_53-CloudStack.png Affinity Groups UI Icon is wrong Key: CLOUDSTACK-7262 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7262 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, UI Affects Versions: 4.4.0 Environment: Chrome 35, Ubuntu Server 14.04 LTS Reporter: Tanner Danzey Priority: Trivial Labels: icons, interface, ui Attachments: 2014-08-05 23_09_53-CloudStack.png, 2014-08-05 23_11_10-CloudStack.png The hover icon for Affinity Groups is the one for Instances. Additionally, the non-hover icon has a white border around it, which none of the other icons have. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7262) Affinity Groups UI Icon is wrong
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14087220#comment-14087220 ] Tanner Danzey commented on CLOUDSTACK-7262: --- If anyone sees this, please assign the issue to me. I will be working on a patch as soon as I get my dev environment up. Affinity Groups UI Icon is wrong Key: CLOUDSTACK-7262 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7262 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, UI Affects Versions: 4.4.0 Environment: Chrome 35, Ubuntu Server 14.04 LTS Reporter: Tanner Danzey Priority: Trivial Labels: icons, interface, ui Attachments: 2014-08-05 23_09_53-CloudStack.png, 2014-08-05 23_11_10-CloudStack.png The hover icon for Affinity Groups is the one for Instances. Additionally, the non-hover icon has a white border around it, which none of the other icons have. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-7187) Virtual Router page has numerous unresolved content ID i.e. label.no.grouping
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanner Danzey resolved CLOUDSTACK-7187. --- Resolution: Cannot Reproduce Fix Version/s: 4.4.0 I can't find this particular issue in the tarball source released on the ACS website. It does, however, exist in the deb packages. Virtual Router page has numerous unresolved content ID i.e. label.no.grouping --- Key: CLOUDSTACK-7187 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7187 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0 Environment: Google Chrome 35 Reporter: Tanner Danzey Priority: Trivial Labels: management, ui Fix For: 4.4.0 Attachments: ss1.png, ss2.png, ss3.png See screenshots attached. Issue persists after full browser data wipe. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7257) CLONE - system VM not coming up in LXC zone for rhel 6.x
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14087279#comment-14087279 ] ASF subversion and git services commented on CLOUDSTACK-7257: - Commit e73e7c3939b0d5f427521df982c7b0c46bae3e0a in cloudstack's branch refs/heads/4.4 from [~amogh.vasekar] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e73e7c3 ] CLOUDSTACK-7257: Missing LXC mappings, reuse KVM mappings CLONE - system VM not coming up in LXC zone for rhel 6.x -- Key: CLOUDSTACK-7257 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7257 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.4.0 Reporter: Amogh Vasekar Assignee: Amogh Vasekar Priority: Blocker Fix For: 4.4.1 created a zone with LXC hypervisor on rhel 6.3 host Pre seeded the KVM template as LXC On enabling zone Syemt VMs are not coming up Agent log shows : ttempting to create storage pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,260 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create storage pool 4032a858-88b0-3c03-8477-8984eb6b390b (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,417 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create volume 1c123c1a-1873-11e4-87de-4524e40b898e (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,052 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to remove storage pool 4032a858-88b0-3c03-8477-8984eb6b390b from libvirt 2014-07-31 04:57:14,388 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Creating volume 75d88b46-1b93-4065-a348-460b8d3911fb from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:14,389 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Attempting to create volume 75d88b46-1b93-4065-a348-460b8d3911fb (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,948 WARN [cloud.agent.Agent] (agentRequest-Handler-3:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) 2014-07-31 04:57:15,700 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Creating volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:15,701 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Attempting to create volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:16,262 WARN [cloud.agent.Agent] (agentRequest-Handler-1:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at
