date:20140826

shweta agarwal created CLOUDSTACK-7428:
--

 Summary: [LXC] advance zone with security group is disable for LXC 
hypervisor
 Key: CLOUDSTACK-7428
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7428
 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:

1. Create a advance zone with SG
2. Add a Lxc cluster to it



Bug:
cluster addition will fail stating LXC is not supported hypervisor type for SG 
enabled zone



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

[jira] [Created] (CLOUDSTACK-7429) [LXC][UI] hypervisor dropdown in advance zone with SG is not showing LXC hypervisor

shweta agarwal created CLOUDSTACK-7429:
--

 Summary: [LXC][UI] hypervisor dropdown in advance zone with SG is 
not showing LXC hypervisor
 Key: CLOUDSTACK-7429
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7429
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: UI
Affects Versions: 4.5.0
Reporter: shweta agarwal
Priority: Critical
 Fix For: 4.5.0
 Attachments: lxc-sg.png

Repro Steps :

Try creating a SG enabled advance zone with LXC hypervisor. 

Bug:
Hypervisor dropdown is not showing LXC hypervisor



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

[jira] [Updated] (CLOUDSTACK-7429) [LXC][UI] hypervisor dropdown in advance zone with SG is not showing LXC hypervisor


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

shweta agarwal updated CLOUDSTACK-7429:
---

Attachment: lxc-sg.png

 [LXC][UI] hypervisor dropdown in advance zone with SG is not showing LXC 
 hypervisor
 ---

 Key: CLOUDSTACK-7429
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7429
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.5.0
Reporter: shweta agarwal
Priority: Critical
 Fix For: 4.5.0

 Attachments: lxc-sg.png


 Repro Steps :
 Try creating a SG enabled advance zone with LXC hypervisor. 
 Bug:
 Hypervisor dropdown is not showing LXC hypervisor



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

[jira] [Created] (CLOUDSTACK-7430) [UI] no option to remove /delete host in maintenance from UI

shweta agarwal created CLOUDSTACK-7430:
--

 Summary: [UI] no option to remove /delete host in maintenance from 
UI
 Key: CLOUDSTACK-7430
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7430
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: UI
Affects Versions: 4.5.0
Reporter: shweta agarwal
 Fix For: 4.5.0


Repro steps:
1. Create a Zone
2. Put host to maintenance 
3. when host is in maintenance try to remove/delete host from cluster via Ui

Bug:
No option to delete host 


attaching snapshot



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

[jira] [Updated] (CLOUDSTACK-7430) [UI] no option to remove /delete host from cluster from UI


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

shweta agarwal updated CLOUDSTACK-7430:
---

Summary: [UI] no option to remove /delete host from cluster from UI  (was: 
[UI] no option to remove /delete host in maintenance from UI)

 [UI] no option to remove /delete host from cluster from UI
 --

 Key: CLOUDSTACK-7430
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7430
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.5.0
Reporter: shweta agarwal
 Fix For: 4.5.0

 Attachments: delete-host.png


 Repro steps:
 1. Create a Zone
 2. Put host to maintenance 
 3. when host is in maintenance try to remove/delete host from cluster via Ui
 Bug:
 No option to delete host 
 attaching snapshot



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

[jira] [Updated] (CLOUDSTACK-7430) [UI] no option to remove /delete host from cluster from UI


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

shweta agarwal updated CLOUDSTACK-7430:
---

Attachment: delete-host.png

 [UI] no option to remove /delete host from cluster from UI
 --

 Key: CLOUDSTACK-7430
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7430
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.5.0
Reporter: shweta agarwal
 Fix For: 4.5.0

 Attachments: delete-host.png


 Repro steps:
 1. Create a Zone
 2. Put host to maintenance 
 3. when host is in maintenance try to remove/delete host from cluster via Ui
 Bug:
 No option to delete host 
 attaching snapshot



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

[jira] [Updated] (CLOUDSTACK-7429) [LXC][UI] hypervisor dropdown in advance zone with SG is not showing LXC hypervisor


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

shweta agarwal updated CLOUDSTACK-7429:
---

Priority: Blocker  (was: Critical)

 [LXC][UI] hypervisor dropdown in advance zone with SG is not showing LXC 
 hypervisor
 ---

 Key: CLOUDSTACK-7429
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7429
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.5.0
Reporter: shweta agarwal
Priority: Blocker
 Fix For: 4.5.0

 Attachments: lxc-sg.png


 Repro Steps :
 Try creating a SG enabled advance zone with LXC hypervisor. 
 Bug:
 Hypervisor dropdown is not showing LXC hypervisor



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

[jira] [Updated] (CLOUDSTACK-7382) [LXC] [UI] remove non linux based os from dropdown of register templates


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

shweta agarwal updated CLOUDSTACK-7382:
---

Priority: Blocker  (was: Major)

 [LXC] [UI] remove non linux based os from dropdown of register templates
 

 Key: CLOUDSTACK-7382
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7382
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM, UI
Affects Versions: 4.5.0
Reporter: shweta agarwal
Priority: Blocker
 Fix For: 4.5.0


 Repro steps
 Try to register  rhel 7 template on rhel 7 LXC setup .
 Bug:
 OS types rhel 7 nos shown in UI in dropdown
 We should also remove other non Linux based OS from this list in case of LXC



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

[jira] [Updated] (CLOUDSTACK-7382) [LXC] [UI] add rhel 7 in OS type dropdown of register templates


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

shweta agarwal updated CLOUDSTACK-7382:
---

Summary: [LXC] [UI] add rhel 7 in OS type dropdown of register templates  
(was: [LXC] [UI] remove non linux based os from dropdown of register templates)

 [LXC] [UI] add rhel 7 in OS type dropdown of register templates
 ---

 Key: CLOUDSTACK-7382
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7382
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM, UI
Affects Versions: 4.5.0
Reporter: shweta agarwal
Priority: Blocker
 Fix For: 4.5.0


 Repro steps
 Try to register  rhel 7 template on rhel 7 LXC setup .
 Bug:
 OS types rhel 7 not shown in UI in drop down
 We should also remove other non Linux based OS from this list in case of LXC



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

[jira] [Updated] (CLOUDSTACK-7382) [LXC] [UI] remove non linux based os from dropdown of register templates

2014-08-26 Thread ASF subversion and git services (JIRA)


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

shweta agarwal updated CLOUDSTACK-7382:
---

Description: 
Repro steps
Try to register  rhel 7 template on rhel 7 LXC setup .

Bug:
OS types rhel 7 not shown in UI in drop down

We should also remove other non Linux based OS from this list in case of LXC


  was:
Repro steps
Try to register  rhel 7 template on rhel 7 LXC setup .

Bug:
OS types rhel 7 nos shown in UI in dropdown

We should also remove other non Linux based OS from this list in case of LXC



 [LXC] [UI] remove non linux based os from dropdown of register templates
 

 Key: CLOUDSTACK-7382
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7382
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM, UI
Affects Versions: 4.5.0
Reporter: shweta agarwal
Priority: Blocker
 Fix For: 4.5.0


 Repro steps
 Try to register  rhel 7 template on rhel 7 LXC setup .
 Bug:
 OS types rhel 7 not shown in UI in drop down
 We should also remove other non Linux based OS from this list in case of LXC



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

[jira] [Resolved] (CLOUDSTACK-7315) [LXC] libvirt Exception when deleting volume as a part of expunge VM

2014-08-26 Thread Kishan Kavala (JIRA)


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

Kishan Kavala resolved CLOUDSTACK-7315.
---

Resolution: Fixed

StorageVol.delete doesn't work for volumes in DIR format.
Use rm command to delete folder

 [LXC] libvirt Exception when deleting volume as a part of expunge VM
 

 Key: CLOUDSTACK-7315
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7315
 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

 Attachments: agent.log


 Repro steps:
 Create a LXC VM
 Destroy the VM  with expunge=true :
 Agent log shows following exception :
 Instructing libvirt to remove volume c24ecda3-128f-4e3e-bec9-04aca09cdeb1 
 from pool dfa2ec3c-d133-3284-8583-0a0845aa4424
 2014-08-12 04:38:37,759 DEBUG [kvm.storage.KVMStorageProcessor] 
 (agentRequest-Handler-3:null) Failed to delete volume:
 com.cloud.utils.exception.CloudRuntimeException: 
 org.libvirt.LibvirtException: cannot remove directory 
 '/mnt/dfa2ec3c-d133-3284-8583-0a0845aa4424/c24ecda3-128f-4e3e-bec9-04aca09cdeb1':
  Directory not empty
 at 
 com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.deletePhysicalDisk(LibvirtStorageAdaptor.java:856)
 at 
 com.cloud.hypervisor.kvm.storage.LibvirtStoragePool.deletePhysicalDisk(LibvirtStoragePool.java:175)
 at 
 com.cloud.hypervisor.kvm.storage.KVMStorageProcessor.deleteVolume(KVMStorageProcessor.java:1203)
 at 
 com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:124)
 at 
 com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:57)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1356)
 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-12 04:38:37,759 DEBUG [cloud.agent.Agent] 
 (agentRequest-Handler-3:null) Seq 1-4558487247829097659:  { Ans: , MgmtId: 
 233845177509765, via: 1, Ver: v1, Flags: 10, 
 [{com.cloud.agent.api.Answer:{result:false,details:com.cloud.utils.exception.CloudRuntimeException:
  org.libvirt.LibvirtException: cannot remove directory 
 '/mnt/dfa2ec3c-d133-3284-8583-0a0845aa4424/c24ecda3-128f-4e3e-bec9-04aca09cdeb1':
  Directory not empty,wait:0}}] }
 2014-08-12 04:38:38,321 DEBUG [cloud.agent.Agent] 
 (agentRequest-Handler-1:null) Processing command: 
 com.cloud.agent.api.GetStorageStatsCommand
 2014-08-12 04:38:38,321 DEBUG [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-1:null) 



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

[jira] [Commented] (CLOUDSTACK-7315) [LXC] libvirt Exception when deleting volume as a part of expunge VM


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110494#comment-14110494
 ] 

ASF subversion and git services commented on CLOUDSTACK-7315:
-

Commit 30ecf935e8f49c4b403113c45249896c859b7927 in cloudstack's branch 
refs/heads/master from [~kishan]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=30ecf93 ]

CLOUDSTACK-7315: Set LXC volumes format as DIR. Use rm command to delete LXC 
volumes. Libvirt delete volume does not handle directories


 [LXC] libvirt Exception when deleting volume as a part of expunge VM
 

 Key: CLOUDSTACK-7315
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7315
 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

 Attachments: agent.log


 Repro steps:
 Create a LXC VM
 Destroy the VM  with expunge=true :
 Agent log shows following exception :
 Instructing libvirt to remove volume c24ecda3-128f-4e3e-bec9-04aca09cdeb1 
 from pool dfa2ec3c-d133-3284-8583-0a0845aa4424
 2014-08-12 04:38:37,759 DEBUG [kvm.storage.KVMStorageProcessor] 
 (agentRequest-Handler-3:null) Failed to delete volume:
 com.cloud.utils.exception.CloudRuntimeException: 
 org.libvirt.LibvirtException: cannot remove directory 
 '/mnt/dfa2ec3c-d133-3284-8583-0a0845aa4424/c24ecda3-128f-4e3e-bec9-04aca09cdeb1':
  Directory not empty
 at 
 com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.deletePhysicalDisk(LibvirtStorageAdaptor.java:856)
 at 
 com.cloud.hypervisor.kvm.storage.LibvirtStoragePool.deletePhysicalDisk(LibvirtStoragePool.java:175)
 at 
 com.cloud.hypervisor.kvm.storage.KVMStorageProcessor.deleteVolume(KVMStorageProcessor.java:1203)
 at 
 com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:124)
 at 
 com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:57)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1356)
 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-12 04:38:37,759 DEBUG [cloud.agent.Agent] 
 (agentRequest-Handler-3:null) Seq 1-4558487247829097659:  { Ans: , MgmtId: 
 233845177509765, via: 1, Ver: v1, Flags: 10, 
 [{com.cloud.agent.api.Answer:{result:false,details:com.cloud.utils.exception.CloudRuntimeException:
  org.libvirt.LibvirtException: cannot remove directory 
 '/mnt/dfa2ec3c-d133-3284-8583-0a0845aa4424/c24ecda3-128f-4e3e-bec9-04aca09cdeb1':
  Directory not empty,wait:0}}] }
 2014-08-12 04:38:38,321 DEBUG [cloud.agent.Agent] 
 (agentRequest-Handler-1:null) Processing command: 
 com.cloud.agent.api.GetStorageStatsCommand
 2014-08-12 04:38:38,321 DEBUG [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-1:null) 



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

[jira] [Commented] (CLOUDSTACK-7218) [Automation] NPE observed while deleting account in automation run

2014-08-26 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110513#comment-14110513
 ] 

ASF subversion and git services commented on CLOUDSTACK-7218:
-

Commit 384025f258b454726be2556ed10c7e13a241f088 in cloudstack's branch 
refs/heads/master from Jayapal
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=384025f ]

CLOUDSTACK-7218: Remvoing all static nat associated with vm in case of 
secondary ips

In vm secondary ips case static nat configured to vm primary/secondary ips
IP1--vm1Ip1, IP2--vm1Ip2
While destroying vm deleting all static nats associated with the vm


 [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-7405) ec2 metadata service requires trailing / for listing items

2014-08-26 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110520#comment-14110520
 ] 

ASF subversion and git services commented on CLOUDSTACK-7405:
-

Commit b3bfe21cf1e3c73ebdc6b597f32558b63b2fe519 in cloudstack's branch 
refs/heads/4.3 from [~webern]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b3bfe21 ]

CLOUDSTACK-7405: Allow all VR urls to be accessed without trailing slash

Signed-off-by: Erik Weber terbol...@gmail.com
Signed-off-by: Sebastien Goasguen run...@gmail.com


 ec2 metadata service requires trailing / for listing items
 --

 Key: CLOUDSTACK-7405
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7405
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: AWSAPI
Reporter: Scott Moser
Priority: Minor

 This came to me through bug reports to cloud-init:
  https://bugs.launchpad.net/cloud-init/+bug/1356855
 and
  https://bugs.launchpad.net/cloud-init/+bug/1311107
 Apparently, the EC2 metadata service that cloudstack provides returns a 404 
 for dictionary entries that do not have a trailing /.
 Example (as reported to me, i have no first hand experience).
 $ wget http://169.254.169.254/latest/meta-data ;
 404
 $ wget http://169.254.169.254/latest/meta-data/
 $ cat index.html ; echo
 ami-id
 ami-launch-index
 ami-manifest-path
 block-device-mapping/
 hostname
 instance-action
 instance-id
 instance-type
 local-hostname
 local-ipv4
 mac
 metrics/
 network/
 placement/
 profile
 public-hostname
 public-ipv4
 public-keys/
 reservation-id
 security-groups
 services/
   



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

[jira] [Resolved] (CLOUDSTACK-7218) [Automation] NPE observed while deleting account in automation run

2014-08-26 Thread Jayapal Reddy (JIRA)


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

Jayapal Reddy resolved CLOUDSTACK-7218.
---

Resolution: Fixed

 [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 com.sun.proxy.$Proxy102.deleteUserAccount(Unknown Source)
 at

[jira] [Commented] (CLOUDSTACK-300) Creation of compute offering allow combination of local storage + HA

2014-08-26 Thread Saksham Srivastava (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110569#comment-14110569
 ] 

Saksham Srivastava commented on CLOUDSTACK-300:
---

API throws exception now if trying to create SO with both HA and Local Storage. 
Resolving.


 Creation of  compute offering allow   combination of local storage + HA
 ---

 Key: CLOUDSTACK-300
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-300
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: pre-4.0.0
 Environment: Git Revision: fb88d2e9de795528e8b9f7e16d8a89eacc5a7e12
 Git URL: https://git-wip-us.apache.org/repos/asf/incubator-cloudstack.git
Reporter: prashant kumar mishra
Assignee: Saksham Srivastava
Priority: Minor
 Fix For: 4.4.0


 HA is not supported for local storage, but crate compute offering allow user 
 to create a compute offering with a combination of Local storage and HA 
 together.  we should have a check for this combination to make sure  that it 
 should not allowed on UI/API level.



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

[jira] [Resolved] (CLOUDSTACK-300) Creation of compute offering allow combination of local storage + HA

2014-08-26 Thread Saksham Srivastava (JIRA)


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

Saksham Srivastava resolved CLOUDSTACK-300.
---

Resolution: Fixed

 Creation of  compute offering allow   combination of local storage + HA
 ---

 Key: CLOUDSTACK-300
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-300
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: pre-4.0.0
 Environment: Git Revision: fb88d2e9de795528e8b9f7e16d8a89eacc5a7e12
 Git URL: https://git-wip-us.apache.org/repos/asf/incubator-cloudstack.git
Reporter: prashant kumar mishra
Assignee: Saksham Srivastava
Priority: Minor
 Fix For: 4.4.0


 HA is not supported for local storage, but crate compute offering allow user 
 to create a compute offering with a combination of Local storage and HA 
 together.  we should have a check for this combination to make sure  that it 
 should not allowed on UI/API level.



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

[jira] [Assigned] (CLOUDSTACK-7106) RPM build failing with RHEL7

2014-08-26 Thread Damodar Reddy T (JIRA)


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

Damodar Reddy T reassigned CLOUDSTACK-7106:
---

Assignee: Damodar Reddy T  (was: Hugo Trippaers)

 RPM build failing with RHEL7
 

 Key: CLOUDSTACK-7106
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7106
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Install and Setup
Affects Versions: 4.5.0
 Environment: RHEL7
Reporter: Rayees Namathponnan
Assignee: Damodar Reddy T
Priority: Critical
 Fix For: 4.5.0


 RPM build failing with RHEL7, since there are dependency with tomcat, we need 
 to create sperate spec.file for RHEL7 or re write existing spec file to 
 support both RHE6 and 7



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

[jira] [Resolved] (CLOUDSTACK-7106) RPM build failing with RHEL7

2014-08-26 Thread Damodar Reddy T (JIRA)


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

Damodar Reddy T resolved CLOUDSTACK-7106.
-

Resolution: Fixed

 RPM build failing with RHEL7
 

 Key: CLOUDSTACK-7106
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7106
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Install and Setup
Affects Versions: 4.5.0
 Environment: RHEL7
Reporter: Rayees Namathponnan
Assignee: Damodar Reddy T
Priority: Critical
 Fix For: 4.5.0


 RPM build failing with RHEL7, since there are dependency with tomcat, we need 
 to create sperate spec.file for RHEL7 or re write existing spec file to 
 support both RHE6 and 7



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

[jira] [Commented] (CLOUDSTACK-7392) [Automation] NPE thrown during Migration of VM

2014-08-26 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110679#comment-14110679
 ] 

ASF subversion and git services commented on CLOUDSTACK-7392:
-

Commit e3c0815a0c8ea65b24f8050e0e870773412604ab in cloudstack's branch 
refs/heads/master from [~koushikd]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e3c0815 ]

CLOUDSTACK-7392: [Automation] NPE thrown during Migration of VM
NPE is thrown as invalid hostId (corresponding to SSVM) is passed as paramater.
Added validation to check that the host is of type 'Routing'


 [Automation] NPE thrown during Migration of VM
 --

 Key: CLOUDSTACK-7392
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7392
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Koushik Das
Priority: Critical
 Fix For: 4.5.0


 ===
 *NullPointerException:*
 ===
 2014-08-20 14:08:47,538 INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
 (API-Job-Executor-60:ctx-3bfb9e76 job-8131) Add job-8131 into job monitoring
 2014-08-20 14:08:47,538 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (API-Job-Executor-60:ctx-3bfb9e76 job-8131) Executing AsyncJobVO {id:8131, 
 userId: 2, accountId: 2, instanceType: None, instanceId: null, cmd: 
 org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdInfo: 
 {response:json,ctxDetails:{\com.cloud.vm.VirtualMachine\:\cae46088-5aec-4305-ab43-bd71e740f1d2\,\com.cloud.host.Host\:\bb004159-d510-42b4-bfd5-878140a11f78\},virtualmachineid:cae46088-5aec-4305-ab43-bd71e740f1d2,cmdEventType:VM.MIGRATE,hostid:bb004159-d510-42b4-bfd5-878140a11f78,ctxUserId:2,httpmethod:GET,ctxAccountId:2,ctxStartEventId:32647,apiKey:NpffyWZkfwK7gPcNpx28Ohv6K56ftl57A409SyokqHjJ2ZNe3AvvF3F0teTETeIIqrtlcWpQOooM3cQyPveGXw,signature:ynKin/CRvRLp9JqWtSd1xbWhyxk\u003d},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 231707544610094, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2014-08-20 14:08:47,545 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (catalina-exec-24:ctx-0f778c79 ctx-cc81cab0 ctx-375c2462) submit async 
 job-8131, details: AsyncJobVO {id:8131, userId: 2, accountId: 2, 
 instanceType: None, instanceId: null, cmd: 
 org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdInfo: 
 {response:json,ctxDetails:{\com.cloud.vm.VirtualMachine\:\cae46088-5aec-4305-ab43-bd71e740f1d2\,\com.cloud.host.Host\:\bb004159-d510-42b4-bfd5-878140a11f78\},virtualmachineid:cae46088-5aec-4305-ab43-bd71e740f1d2,cmdEventType:VM.MIGRATE,hostid:bb004159-d510-42b4-bfd5-878140a11f78,ctxUserId:2,httpmethod:GET,ctxAccountId:2,ctxStartEventId:32647,apiKey:NpffyWZkfwK7gPcNpx28Ohv6K56ftl57A409SyokqHjJ2ZNe3AvvF3F0teTETeIIqrtlcWpQOooM3cQyPveGXw,signature:ynKin/CRvRLp9JqWtSd1xbWhyxk\u003d},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 231707544610094, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2014-08-20 14:08:47,547 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-24:ctx-0f778c79 ctx-cc81cab0 ctx-375c2462) ===END===  
 10.220.135.48 -- GET  
 hostid=bb004159-d510-42b4-bfd5-878140a11f78virtualmachineid=cae46088-5aec-4305-ab43-bd71e740f1d2apiKey=NpffyWZkfwK7gPcNpx28Ohv6K56ftl57A409SyokqHjJ2ZNe3AvvF3F0teTETeIIqrtlcWpQOooM3cQyPveGXwcommand=migrateVirtualMachinesignature=ynKin%2FCRvRLp9JqWtSd1xbWhyxk%3Dresponse=json
 2014-08-20 14:08:47,551 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-21:ctx-b8261333) ===START===  10.220.135.48 -- GET  
 jobid=dd179539-d888-47b6-8a9e-3c264ee23df4apiKey=NpffyWZkfwK7gPcNpx28Ohv6K56ftl57A409SyokqHjJ2ZNe3AvvF3F0teTETeIIqrtlcWpQOooM3cQyPveGXwcommand=queryAsyncJobResultresponse=jsonsignature=wjUpMS7U0V4T8bdiCPgLnglOAdE%3D
 2014-08-20 14:08:47,599 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-21:ctx-b8261333 ctx-ef6ec76a ctx-b6cbec9c) ===END===  
 10.220.135.48 -- GET  
 jobid=dd179539-d888-47b6-8a9e-3c264ee23df4apiKey=NpffyWZkfwK7gPcNpx28Ohv6K56ftl57A409SyokqHjJ2ZNe3AvvF3F0teTETeIIqrtlcWpQOooM3cQyPveGXwcommand=queryAsyncJobResultresponse=jsonsignature=wjUpMS7U0V4T8bdiCPgLnglOAdE%3D
 2014-08-20 14:08:47,614 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (API-Job-Executor-60:ctx-3bfb9e76 job-8131 ctx-aba0d6fb) Sync job-8132 
 execution on object VmWorkJobQueue.1142
 2014-08-20 14:08:47,616 WARN  [c.c.u.d.Merovingian2] 
 (API-Job-Executor-60:ctx-3bfb9e76 job-8131 ctx-aba0d6fb) Was unable to find 
 lock for the key vm_instance1142 and thread id 474572326
 2014-08-20 14:08:49,187 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (AsyncJobMgr-Heartbeat-1:ctx-77b6882f)

[jira] [Resolved] (CLOUDSTACK-7392) [Automation] NPE thrown during Migration of VM

2014-08-26 Thread Koushik Das (JIRA)


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

Koushik Das resolved CLOUDSTACK-7392.
-

Resolution: Fixed

Chandan,

The following needs to be addressed:
- The automation test that caused the failure needs to be fixed to pass correct 
host id parameter
- Add a negative test case for checking that hostId validation is working

 [Automation] NPE thrown during Migration of VM
 --

 Key: CLOUDSTACK-7392
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7392
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Koushik Das
Priority: Critical
 Fix For: 4.5.0


 ===
 *NullPointerException:*
 ===
 2014-08-20 14:08:47,538 INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
 (API-Job-Executor-60:ctx-3bfb9e76 job-8131) Add job-8131 into job monitoring
 2014-08-20 14:08:47,538 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (API-Job-Executor-60:ctx-3bfb9e76 job-8131) Executing AsyncJobVO {id:8131, 
 userId: 2, accountId: 2, instanceType: None, instanceId: null, cmd: 
 org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdInfo: 
 {response:json,ctxDetails:{\com.cloud.vm.VirtualMachine\:\cae46088-5aec-4305-ab43-bd71e740f1d2\,\com.cloud.host.Host\:\bb004159-d510-42b4-bfd5-878140a11f78\},virtualmachineid:cae46088-5aec-4305-ab43-bd71e740f1d2,cmdEventType:VM.MIGRATE,hostid:bb004159-d510-42b4-bfd5-878140a11f78,ctxUserId:2,httpmethod:GET,ctxAccountId:2,ctxStartEventId:32647,apiKey:NpffyWZkfwK7gPcNpx28Ohv6K56ftl57A409SyokqHjJ2ZNe3AvvF3F0teTETeIIqrtlcWpQOooM3cQyPveGXw,signature:ynKin/CRvRLp9JqWtSd1xbWhyxk\u003d},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 231707544610094, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2014-08-20 14:08:47,545 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (catalina-exec-24:ctx-0f778c79 ctx-cc81cab0 ctx-375c2462) submit async 
 job-8131, details: AsyncJobVO {id:8131, userId: 2, accountId: 2, 
 instanceType: None, instanceId: null, cmd: 
 org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdInfo: 
 {response:json,ctxDetails:{\com.cloud.vm.VirtualMachine\:\cae46088-5aec-4305-ab43-bd71e740f1d2\,\com.cloud.host.Host\:\bb004159-d510-42b4-bfd5-878140a11f78\},virtualmachineid:cae46088-5aec-4305-ab43-bd71e740f1d2,cmdEventType:VM.MIGRATE,hostid:bb004159-d510-42b4-bfd5-878140a11f78,ctxUserId:2,httpmethod:GET,ctxAccountId:2,ctxStartEventId:32647,apiKey:NpffyWZkfwK7gPcNpx28Ohv6K56ftl57A409SyokqHjJ2ZNe3AvvF3F0teTETeIIqrtlcWpQOooM3cQyPveGXw,signature:ynKin/CRvRLp9JqWtSd1xbWhyxk\u003d},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 231707544610094, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2014-08-20 14:08:47,547 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-24:ctx-0f778c79 ctx-cc81cab0 ctx-375c2462) ===END===  
 10.220.135.48 -- GET  
 hostid=bb004159-d510-42b4-bfd5-878140a11f78virtualmachineid=cae46088-5aec-4305-ab43-bd71e740f1d2apiKey=NpffyWZkfwK7gPcNpx28Ohv6K56ftl57A409SyokqHjJ2ZNe3AvvF3F0teTETeIIqrtlcWpQOooM3cQyPveGXwcommand=migrateVirtualMachinesignature=ynKin%2FCRvRLp9JqWtSd1xbWhyxk%3Dresponse=json
 2014-08-20 14:08:47,551 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-21:ctx-b8261333) ===START===  10.220.135.48 -- GET  
 jobid=dd179539-d888-47b6-8a9e-3c264ee23df4apiKey=NpffyWZkfwK7gPcNpx28Ohv6K56ftl57A409SyokqHjJ2ZNe3AvvF3F0teTETeIIqrtlcWpQOooM3cQyPveGXwcommand=queryAsyncJobResultresponse=jsonsignature=wjUpMS7U0V4T8bdiCPgLnglOAdE%3D
 2014-08-20 14:08:47,599 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-21:ctx-b8261333 ctx-ef6ec76a ctx-b6cbec9c) ===END===  
 10.220.135.48 -- GET  
 jobid=dd179539-d888-47b6-8a9e-3c264ee23df4apiKey=NpffyWZkfwK7gPcNpx28Ohv6K56ftl57A409SyokqHjJ2ZNe3AvvF3F0teTETeIIqrtlcWpQOooM3cQyPveGXwcommand=queryAsyncJobResultresponse=jsonsignature=wjUpMS7U0V4T8bdiCPgLnglOAdE%3D
 2014-08-20 14:08:47,614 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (API-Job-Executor-60:ctx-3bfb9e76 job-8131 ctx-aba0d6fb) Sync job-8132 
 execution on object VmWorkJobQueue.1142
 2014-08-20 14:08:47,616 WARN  [c.c.u.d.Merovingian2] 
 (API-Job-Executor-60:ctx-3bfb9e76 job-8131 ctx-aba0d6fb) Was unable to find 
 lock for the key vm_instance1142 and thread id 474572326
 2014-08-20 14:08:49,187 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (AsyncJobMgr-Heartbeat-1:ctx-77b6882f) Execute sync-queue item: 
 SyncQueueItemVO {id:3265, queueId: 3264, contentType: AsyncJob, contentId: 
 8132, lastProcessMsid: null, lastprocessNumber: null, lastProcessTime: null, 
 created: Wed Aug 20 14:08:47 UTC 2014}
 2014-08-20

[jira] [Commented] (CLOUDSTACK-7420) Creating a stickiness policy for a load balancer rule that has protocol SSL will fail

2014-08-26 Thread Patrick D. (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110828#comment-14110828
 ] 

Patrick D. commented on CLOUDSTACK-7420:


Create an LB rule:
algorithm=roundrobincommand=createLoadBalancerRulename=lbrulenetworkId=c3601690-3ea3-4987-b9e4-c55728a40384privatePort=12projectId=777cd2f4-8d38-4510-bce6-7d94eede0557protocol=sslpublicIpId=feffe971-5f58-4763-80eb-a5bfd72330c9publicPort=12response=json

Assign instances to it:
command=assignToLoadBalancerRuleid=46844e60-a168-4278-bd20-4f2efe21d4f5projectId=777cd2f4-8d38-4510-bce6-7d94eede0557response=jsonvirtualmachineids=0f09d6c8-d4de-4f38-a179-6b552839002b

Assign an SSL cert to it:
certId=3ed76011-c135-41d4-b180-237433b763d1command=assignCertToLoadBalancerlbRuleId=46844e60-a168-4278-bd20-4f2efe21d4f5response=json

Create an LB stickiness policy for LB rule:
command=createLBStickinessPolicylbruleid=46844e60-a168-4278-bd20-4f2efe21d4f5methodname=LbCookiename=ckieparam[0].name=holdtimeparam[0].value=10projectid=777cd2f4-8d38-4510-bce6-7d94eede0557response=json

It will then fail with the same exception.
However, if you create a rule, create a stickiness policy, assign the cert and 
then assign instances, it will not fail

 Creating a stickiness policy for a load balancer rule that has protocol SSL 
 will fail
 -

 Key: CLOUDSTACK-7420
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7420
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.4.0
Reporter: Patrick D.

 2014-08-25 11:36:05,562 ERROR [c.c.n.ExternalLoadBalancerDeviceManagerImpl] 
 (API-Job-Executor-67:ctx-a8f58eed job-674 ctx-47688fe7) Unable to apply load 
 balancer rules to the external load balancer appliance in zone dev3_zone1 due 
 to: Exception: com.cloud.utils.exception.ExecutionException
 Message: Failed to create new virtual server:Cloud-VirtualServer due to Can 
 not update virtual server:Cloud-VirtualServer as current protocol:SSL of 
 virtual server is different from the  intended protocol:HTTP
 Stack: com.cloud.utils.exception.ExecutionException: Failed to create new 
 virtual server:Cloud-VirtualServer due to Can not update virtual 
 server:Cloud-VirtualServer as current protocol:SSL of virtual server is 
 different from the  intended protocol:HTTP
   at 
 com.cloud.network.resource.NetscalerResource.addLBVirtualServer(NetscalerResource.java:2802)
   at 
 com.cloud.network.resource.NetscalerResource.execute(NetscalerResource.java:589)
   at 
 com.cloud.network.resource.NetscalerResource.executeRequest(NetscalerResource.java:427)
   at 
 com.cloud.network.resource.NetscalerResource.retry(NetscalerResource.java:3656)
   at 
 com.cloud.network.resource.NetscalerResource.execute(NetscalerResource.java:885)
   at 
 com.cloud.network.resource.NetscalerResource.executeRequest(NetscalerResource.java:427)
   at 
 com.cloud.network.resource.NetscalerResource.retry(NetscalerResource.java:3656)
   at 
 com.cloud.network.resource.NetscalerResource.execute(NetscalerResource.java:885)
   at 
 com.cloud.network.resource.NetscalerResource.executeRequest(NetscalerResource.java:427)
   at 
 com.cloud.network.resource.NetscalerResource.executeRequest(NetscalerResource.java:416)
   at 
 com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216)
   at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
   at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
   at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
   at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
   at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
   at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
   at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
   at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
   at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
   at java.lang.Thread.run(Thread.java:745)



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

[jira] [Commented] (CLOUDSTACK-7315) [LXC] libvirt Exception when deleting volume as a part of expunge VM

2014-08-26 Thread Marcus Sorensen (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110936#comment-14110936
 ] 

Marcus Sorensen commented on CLOUDSTACK-7315:
-

I haven't been paying a ton of attention to the list, admittedly, but I think 
it would be good to use caution when changing signatures of functions. This 
commit breaks storage plugins (adaptors) for KVM. We will want to notify Mike 
and whoever else may have implemented a Storage Adaptor.

 [LXC] libvirt Exception when deleting volume as a part of expunge VM
 

 Key: CLOUDSTACK-7315
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7315
 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

 Attachments: agent.log


 Repro steps:
 Create a LXC VM
 Destroy the VM  with expunge=true :
 Agent log shows following exception :
 Instructing libvirt to remove volume c24ecda3-128f-4e3e-bec9-04aca09cdeb1 
 from pool dfa2ec3c-d133-3284-8583-0a0845aa4424
 2014-08-12 04:38:37,759 DEBUG [kvm.storage.KVMStorageProcessor] 
 (agentRequest-Handler-3:null) Failed to delete volume:
 com.cloud.utils.exception.CloudRuntimeException: 
 org.libvirt.LibvirtException: cannot remove directory 
 '/mnt/dfa2ec3c-d133-3284-8583-0a0845aa4424/c24ecda3-128f-4e3e-bec9-04aca09cdeb1':
  Directory not empty
 at 
 com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.deletePhysicalDisk(LibvirtStorageAdaptor.java:856)
 at 
 com.cloud.hypervisor.kvm.storage.LibvirtStoragePool.deletePhysicalDisk(LibvirtStoragePool.java:175)
 at 
 com.cloud.hypervisor.kvm.storage.KVMStorageProcessor.deleteVolume(KVMStorageProcessor.java:1203)
 at 
 com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:124)
 at 
 com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:57)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1356)
 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-12 04:38:37,759 DEBUG [cloud.agent.Agent] 
 (agentRequest-Handler-3:null) Seq 1-4558487247829097659:  { Ans: , MgmtId: 
 233845177509765, via: 1, Ver: v1, Flags: 10, 
 [{com.cloud.agent.api.Answer:{result:false,details:com.cloud.utils.exception.CloudRuntimeException:
  org.libvirt.LibvirtException: cannot remove directory 
 '/mnt/dfa2ec3c-d133-3284-8583-0a0845aa4424/c24ecda3-128f-4e3e-bec9-04aca09cdeb1':
  Directory not empty,wait:0}}] }
 2014-08-12 04:38:38,321 DEBUG [cloud.agent.Agent] 
 (agentRequest-Handler-1:null) Processing command: 
 com.cloud.agent.api.GetStorageStatsCommand
 2014-08-12 04:38:38,321 DEBUG [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-1:null) 



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

[jira] [Comment Edited] (CLOUDSTACK-7315) [LXC] libvirt Exception when deleting volume as a part of expunge VM

2014-08-26 Thread Marcus Sorensen (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110936#comment-14110936
 ] 

Marcus Sorensen edited comment on CLOUDSTACK-7315 at 8/26/14 4:52 PM:
--

I haven't been paying a ton of attention to the list, admittedly, but I think 
it would be good to use caution when changing signatures of functions. This 
commit breaks storage plugins (adaptors) for KVM. We will want to notify Mike 
and whoever else may have implemented a Storage Adaptor. ... actually Mike's 
code has been changed so scratch that.


was (Author: mlsorensen):
I haven't been paying a ton of attention to the list, admittedly, but I think 
it would be good to use caution when changing signatures of functions. This 
commit breaks storage plugins (adaptors) for KVM. We will want to notify Mike 
and whoever else may have implemented a Storage Adaptor.

 [LXC] libvirt Exception when deleting volume as a part of expunge VM
 

 Key: CLOUDSTACK-7315
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7315
 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

 Attachments: agent.log


 Repro steps:
 Create a LXC VM
 Destroy the VM  with expunge=true :
 Agent log shows following exception :
 Instructing libvirt to remove volume c24ecda3-128f-4e3e-bec9-04aca09cdeb1 
 from pool dfa2ec3c-d133-3284-8583-0a0845aa4424
 2014-08-12 04:38:37,759 DEBUG [kvm.storage.KVMStorageProcessor] 
 (agentRequest-Handler-3:null) Failed to delete volume:
 com.cloud.utils.exception.CloudRuntimeException: 
 org.libvirt.LibvirtException: cannot remove directory 
 '/mnt/dfa2ec3c-d133-3284-8583-0a0845aa4424/c24ecda3-128f-4e3e-bec9-04aca09cdeb1':
  Directory not empty
 at 
 com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.deletePhysicalDisk(LibvirtStorageAdaptor.java:856)
 at 
 com.cloud.hypervisor.kvm.storage.LibvirtStoragePool.deletePhysicalDisk(LibvirtStoragePool.java:175)
 at 
 com.cloud.hypervisor.kvm.storage.KVMStorageProcessor.deleteVolume(KVMStorageProcessor.java:1203)
 at 
 com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:124)
 at 
 com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:57)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1356)
 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-12 04:38:37,759 DEBUG [cloud.agent.Agent] 
 (agentRequest-Handler-3:null) Seq 1-4558487247829097659:  { Ans: , MgmtId: 
 233845177509765, via: 1, Ver: v1, Flags: 10, 
 [{com.cloud.agent.api.Answer:{result:false,details:com.cloud.utils.exception.CloudRuntimeException:
  org.libvirt.LibvirtException: cannot remove directory 
 '/mnt/dfa2ec3c-d133-3284-8583-0a0845aa4424/c24ecda3-128f-4e3e-bec9-04aca09cdeb1':
  Directory not empty,wait:0}}] }
 2014-08-12 04:38:38,321 DEBUG [cloud.agent.Agent] 
 (agentRequest-Handler-1:null) Processing command: 
 com.cloud.agent.api.GetStorageStatsCommand
 2014-08-12 04:38:38,321 DEBUG [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-1:null) 



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

[jira] [Updated] (CLOUDSTACK-7341) Snapshot not allowed for hypervisor KVM


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

Rohit Yadav updated CLOUDSTACK-7341:


Fix Version/s: (was: 4.4.1)
   Future

 Snapshot not allowed for hypervisor KVM
 ---

 Key: CLOUDSTACK-7341
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7341
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.4.0, 4.4.1
Reporter: Rohit Yadav
Priority: Blocker
 Fix For: Future


 Deployed Basic zone (default networking) on KVM/Ubuntu, created an instance. 
 Tried to create snapshot of running and stopped instance, both failed with: 
 431 VM snapshot is not enabled for hypervisor type: KVM (from api response).
 Is this alright, or something wrong with KVM, we don't have snapshots with 
 KVM?



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

[jira] [Updated] (CLOUDSTACK-7341) Snapshot not allowed for hypervisor KVM


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

Rohit Yadav updated CLOUDSTACK-7341:


Priority: Major  (was: Blocker)

 Snapshot not allowed for hypervisor KVM
 ---

 Key: CLOUDSTACK-7341
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7341
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.4.0, 4.4.1
Reporter: Rohit Yadav
 Fix For: Future


 Deployed Basic zone (default networking) on KVM/Ubuntu, created an instance. 
 Tried to create snapshot of running and stopped instance, both failed with: 
 431 VM snapshot is not enabled for hypervisor type: KVM (from api response).
 Is this alright, or something wrong with KVM, we don't have snapshots with 
 KVM?



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

[jira] [Updated] (CLOUDSTACK-7341) Snapshot not allowed for hypervisor KVM


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

Rohit Yadav updated CLOUDSTACK-7341:


Issue Type: Improvement  (was: Bug)

 Snapshot not allowed for hypervisor KVM
 ---

 Key: CLOUDSTACK-7341
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7341
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.4.0, 4.4.1
Reporter: Rohit Yadav
Priority: Blocker
 Fix For: Future


 Deployed Basic zone (default networking) on KVM/Ubuntu, created an instance. 
 Tried to create snapshot of running and stopped instance, both failed with: 
 431 VM snapshot is not enabled for hypervisor type: KVM (from api response).
 Is this alright, or something wrong with KVM, we don't have snapshots with 
 KVM?



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

[jira] [Commented] (CLOUDSTACK-7419) Document How to configure SAML SSO/SLO with CloudStack


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14111000#comment-14111000
 ] 

Rohit Yadav commented on CLOUDSTACK-7419:
-

Doc gurus -- [~sebgoa] [~radhikap] [~pdion]
Do we document a plugin usage or configuration such as this one on cwiki.a.o or 
on https://github.com/apache/cloudstack-docs-admin ?

 Document How to configure SAML SSO/SLO with CloudStack
 --

 Key: CLOUDSTACK-7419
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7419
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Reporter: Rohit Yadav
Assignee: Rohit Yadav
Priority: Minor
 Fix For: 4.5.0






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

[jira] [Assigned] (CLOUDSTACK-7341) Snapshot not allowed for hypervisor KVM


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

Rohit Yadav reassigned CLOUDSTACK-7341:
---

Assignee: Rohit Yadav

 Snapshot not allowed for hypervisor KVM
 ---

 Key: CLOUDSTACK-7341
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7341
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.4.0, 4.4.1
Reporter: Rohit Yadav
Assignee: Rohit Yadav
 Fix For: Future


 Deployed Basic zone (default networking) on KVM/Ubuntu, created an instance. 
 Tried to create snapshot of running and stopped instance, both failed with: 
 431 VM snapshot is not enabled for hypervisor type: KVM (from api response).
 Is this alright, or something wrong with KVM, we don't have snapshots with 
 KVM?



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

[jira] [Resolved] (CLOUDSTACK-7083) Implement SAML 2.0 plugin


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

Rohit Yadav resolved CLOUDSTACK-7083.
-

Resolution: Implemented

The feature is implemented in saml2 branch and a merge request has been sent to 
the dev ML. Once the branch is merged, this issue will be closed. Resolving now 
as implemented.

 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-7341) Snapshot not allowed for hypervisor KVM


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14111001#comment-14111001
 ] 

Rohit Yadav commented on CLOUDSTACK-7341:
-

Looks like this is a much needed feature but cannot be supported now, moving to 
future.

 Snapshot not allowed for hypervisor KVM
 ---

 Key: CLOUDSTACK-7341
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7341
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.4.0, 4.4.1
Reporter: Rohit Yadav
 Fix For: Future


 Deployed Basic zone (default networking) on KVM/Ubuntu, created an instance. 
 Tried to create snapshot of running and stopped instance, both failed with: 
 431 VM snapshot is not enabled for hypervisor type: KVM (from api response).
 Is this alright, or something wrong with KVM, we don't have snapshots with 
 KVM?



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

[jira] [Comment Edited] (CLOUDSTACK-6889) UI - create network offering - remove non-needed parameters from API call whose size might exceed limit in some cases.


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027033#comment-14027033
 ] 

Jessica Wang edited comment on CLOUDSTACK-6889 at 8/26/14 5:40 PM:
---

https://issues.citrite.net/i#browse/ES-2177

https://issues.citrite.net/i#browse/CS-20251

https://issues.citrite.net/browse/CS-20252




was (Author: jessicawang):
https://issues.citrite.net/i#browse/ES-2177

https://issues.citrite.net/i#browse/CS-20251



 UI - create network offering - remove non-needed parameters from API call 
 whose size might exceed limit in some cases.
 --

 Key: CLOUDSTACK-6889
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6889
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Jessica Wang
Assignee: Jessica Wang





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

[jira] [Created] (CLOUDSTACK-7431) [Automation] Fix the script test_ldap.py - Move the Ldap configuration information to test_data.py

Chandan Purushothama created CLOUDSTACK-7431:


 Summary: [Automation] Fix the script test_ldap.py - Move the 
Ldap configuration information to test_data.py
 Key: CLOUDSTACK-7431
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7431
 Project: CloudStack
  Issue Type: Test
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Priority: Critical
 Fix For: 4.5.0


Currently because the ldap configuration is hard coded in the script it is 
failing to work on other setups with different ldap configuration. Please move 
that information to test_data.py

*Error Message*

addLdapConfiguration failed   Logs available at 
http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=ldap

Stacktrace

  File /usr/lib/python2.7/unittest/case.py, line 332, in run
testMethod()
  File /root/cloudstack/test/integration/component/test_ldap.py, line 154, in 
test_01_addLdapConfiguration
self.assertEquals(self.ldapconfRes,1,addLdapConfiguration failed)
  File /usr/lib/python2.7/unittest/case.py, line 516, in assertEqual
assertion_func(first, second, msg=msg)
  File /usr/lib/python2.7/unittest/case.py, line 509, in _baseAssertEqual
raise self.failureException(msg)
'addLdapConfiguration failed\n

Logs available at 
http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=ldap




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

[jira] [Created] (CLOUDSTACK-7432) [Automation] Fix the script test_escalations_ipaddresses.py - Service/provider combination Vpn/VpcVirtualRouter is not supported by VPC

Chandan Purushothama created CLOUDSTACK-7432:


 Summary: [Automation] Fix the script 
test_escalations_ipaddresses.py - Service/provider combination 
Vpn/VpcVirtualRouter is not supported by VPC
 Key: CLOUDSTACK-7432
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7432
 Project: CloudStack
  Issue Type: Test
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Priority: Critical
 Fix For: 4.5.0


Three tests in this test suite failed with the same error as shown below:

*Error Message*

Execute cmd: createnetwork failed, due to: errorCode: 431, 
errorText:Service/provider combination Vpn/VpcVirtualRouter is not supported by 
VPC [VPC [26-vpc_vpn-Y1KQVC]   Logs available at 
http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=escalations_ipaddr

Stacktrace

  File /usr/lib/python2.7/unittest/case.py, line 332, in run
testMethod()
  File 
/root/cloudstack/test/integration/component/test_escalations_ipaddresses.py, 
line 890, in test_05_create_delete_lbrule_forvpc
netmask=self.services[ntwk][netmask]
  File /usr/local/lib/python2.7/dist-packages/marvin/lib/base.py, line 2602, 
in create
return Network(apiclient.createNetwork(cmd).__dict__)
  File 
/usr/local/lib/python2.7/dist-packages/marvin/cloudstackAPI/cloudstackAPIClient.py,
 line 1884, in createNetwork
response = self.connection.marvinRequest(command, response_type=response, 
method=method)
  File /usr/local/lib/python2.7/dist-packages/marvin/cloudstackConnection.py, 
line 379, in marvinRequest
raise e
'Execute cmd: createnetwork failed, due to: errorCode: 431, 
errorText:Service/provider combination Vpn/VpcVirtualRouter is not supported by 
VPC [VPC [26-vpc_vpn-Y1KQVC]\n

Logs available at 
http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=escalations_ipaddr
  

Failed Test Cases Information is present at 
http://ccp-tests.xenrt.xs.citrite.net/jenkins/view/Goleta-Regression/job/xenrt-regression-adv-xs/10/testReport/integration.component.test_escalations_ipaddresses/



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

[jira] [Created] (CLOUDSTACK-7433) [Automation] Fix the script test_deploy_vm_userdata_reg.py - Host credentials are hardcoded in the script

Chandan Purushothama created CLOUDSTACK-7433:


 Summary: [Automation] Fix the script 
test_deploy_vm_userdata_reg.py - Host credentials are hardcoded in the script
 Key: CLOUDSTACK-7433
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7433
 Project: CloudStack
  Issue Type: Test
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Priority: Critical
 Fix For: 4.5.0


The host credentials are hardcoded in the script. Please take the host specific 
information from test_data.py which is configurable.

*Error Message*

SSH Connection Failed   Logs available at 
http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=deploy_vm_userdata

Stacktrace

  File /usr/lib/python2.7/unittest/case.py, line 332, in run
testMethod()
  File 
/root/cloudstack/test/integration/component/test_deploy_vm_userdata_reg.py, 
line 209, in test_deployvm_userdata_post
cmd
  File /usr/local/lib/python2.7/dist-packages/marvin/lib/utils.py, line 198, 
in get_process_status
ssh = SshClient(hostip, port, username, password)
  File /usr/local/lib/python2.7/dist-packages/marvin/sshClient.py, line 81, 
in __init__
raise internalError(SSH Connection Failed)
'SSH Connection Failed\n

Logs available at 
http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=deploy_vm_userdata
  



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

[jira] [Updated] (CLOUDSTACK-7422) [Automation] Attach volume test case failing with error Invalid configuration for device '0'


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

Animesh Chaturvedi updated CLOUDSTACK-7422:
---

Assignee: Amogh Vasekar

 [Automation] Attach volume test case failing with error Invalid 
 configuration for device '0'
 --

 Key: CLOUDSTACK-7422
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7422
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Volumes
Affects Versions: 4.5.0
 Environment: Vmware 5.0
 build 4.5
Reporter: Rayees Namathponnan
Assignee: Amogh Vasekar
Priority: Critical
 Fix For: 4.5.0


 Steps to reproduce the defect 
 Run the test 
 integration.component.test_volumes.TestAttachVolumeISO.test_01_volume_iso_attach
 This test case performing below steps 
  678 # Validate the following
  679 # 1. Create and attach 5 data volumes to VM
  680 # 2. Create an ISO. Attach it to VM instance
  681 # 3. Verify that attach ISO is successful
 Here attach volume fails with below error 
 {noformat}
 a5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1ldAASTGphdmEvbGFuZy9TdHJpbmc7eHAAAgACAZh0ABRWb2x1
 bWVBcGlTZXJ2aWNlSW1wbHNyAA5qYXZhLmxhbmcuTG9uZzuL5JDMjyPfAgABSgAFdmFsdWV4cgAQamF2YS5sYW5nLk51bWJlcoaslR0LlOCLAgAAeHAACnNxAH4ABgHJ
 , cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, 
 result: null, initMsid: 90928106758026, completeMsid: null, lastUpdated:
 null, lastPolled: null, created: Sat Aug 23 14:45:42 PDT 2014}, job 
 origin:3043
 com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume 
 TestDiskServ to VM TestVM-24cfe95b-8976-48af-ba42-459b37cfb89c; AttachV
 olumeCommand failed due to Exception: java.lang.RuntimeException
 Message: Invalid configuration for device '0'.
 at 
 com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:2248)
 at 
 com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1216)
 at 
 com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:2615)
 at sun.reflect.GeneratedMethodAccessor855.invoke(Unknown Source)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at 
 com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
 at 
 com.cloud.storage.VolumeApiServiceImpl.handleVmWorkJob(VolumeApiServiceImpl.java:2654)
 at sun.reflect.GeneratedMethodAccessor568.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.$Proxy184.handleVmWorkJob(Unknown Source)
 at 
 com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
 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 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.run(FutureTask.java:262)

[jira] [Updated] (CLOUDSTACK-7421) [Automation] Remove nic from default report CloudRuntimeException in log


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

Animesh Chaturvedi updated CLOUDSTACK-7421:
---

Assignee: Jayapal Reddy

 [Automation] Remove nic from default report CloudRuntimeException in log
 

 Key: CLOUDSTACK-7421
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7421
 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: Rayees Namathponnan
Assignee: Jayapal Reddy
 Fix For: 4.5.0


 Steps to reproduce 
 1 ) Deploy VM 
 2) Add one more nic
 3) remove default nic the VM 
 Result 
 Below exception thrown in log, it should be handled with proper messgae 
 cloud.vm.VmWorkRemoveNicFromVm for VM 30, job origin: 248
 2014-08-23 09:50:33,665 ERROR [c.c.v.VmWorkJobDispatcher] 
 (Work-Job-Executor-61:ctx-5c747fe0 job-248/job-249) Unable to complete 
 AsyncJobVO {id:249, userId: 2, accountId: 2, instanceType: null, instanceId: 
 null, cmd: com.cloud.vm.VmWorkRemoveNicFromVm, cmdInfo: 
 rO0ABXNyACJjb20uY2xvdWQudm0uVm1Xb3JrUmVtb3ZlTmljRnJvbVZtxM1Xh9nBu10CAAFMAAVuaWNJZHQAEExqYXZhL2xhbmcvTG9uZzt4cgATY29tLmNsb3VkLnZtLlZtV29ya5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1ldAASTGphdmEvbGFuZy9TdHJpbmc7eHAAAgACAB50ABlWaXJ0dWFsTWFjaGluZU1hbmFnZXJJbXBsc3IADmphdmEubGFuZy5Mb25nO4vkkMyPI98CAAFKAAV2YWx1ZXhyABBqYXZhLmxhbmcuTnVtYmVyhqyVHQuU4IsCAAB4cABI,
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 90928106758026, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: Sat Aug 23 09:50:32 PDT 2014}, job origin:248
 com.cloud.utils.exception.CloudRuntimeException: Failed to remove nic from 
 VM[User|i-18-30-TestVM] in Ntwk[222|Guest|17], nic is default.
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateRemoveNicFromVm(VirtualMachineManagerImpl.java:2963)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateRemoveNicFromVm(VirtualMachineManagerImpl.java:4690)
 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 
 com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:4738)
 at 
 com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
 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 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.run(FutureTask.java:262)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:744)



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

[jira] [Updated] (CLOUDSTACK-7396) [Automation] Failed to stop VPC router in KVM


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

Animesh Chaturvedi updated CLOUDSTACK-7396:
---

Assignee: edison su

 [Automation] Failed to stop VPC router in KVM
 -

 Key: CLOUDSTACK-7396
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7396
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Affects Versions: 4.5.0
Reporter: Rayees Namathponnan
Assignee: edison su
Priority: Blocker
 Fix For: 4.5.0

 Attachments: agent.rar, kvm.sql, management-server.rar


 This issue observed with latest automation run,  deploy a VPC router and stop 
 Virtual router stop fails with below exception 
 {noformat}
 lhY2NvdW50SWRKAAZ1c2VySWRKAAR2bUlkTAALaGFuZGxlck5hbWV0ABJMamF2YS9sYW5nL1N0cmluZzt4cAABAAEC-XQAGVZpcn
 R1YWxNYWNoaW5lTWFuYWdlckltcGwA, cmdVersion: 0, status: IN_PROGRESS, 
 processStatus: 0, resultCode: 0, result: null, initMsid:
  29066118877352, completeMsid: null, lastUpdated: null, lastPolled: null, 
 created: Thu Aug 21 22:24:10 PDT 2014}, job origin
 :8131
 com.cloud.utils.exception.CloudRuntimeException: Unable to stop 
 VM[DomainRouter|r-761-VM]
 at 
 com.cloud.vm.VirtualMachineManagerImpl.advanceStop(VirtualMachineManagerImpl.java:1523)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateStop(VirtualMachineManagerImpl.java:1377)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateStop(VirtualMachineManagerImpl.java:4594)
 at sun.reflect.GeneratedMethodAccessor162.invoke(Unknown Source)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at 
 com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:4738)
 at 
 com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
 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 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.run(FutureTask.java:262)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:744)
 2014-08-21 22:24:11,959 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (Work-Job-Executor-28:ctx-8824da69 job-8131/job-8162) Comple
 te async job-8162, jobStatus: FAILED, resultCode: 0, result: 
 rO0ABXNyABpqYXZhLmxhbmcuUnVudGltZUV4Y2VwdGlvbp5fBkcKNIPlAgAAeHI
 AE2phdmEubGFuZy5FeGNlcHRpb27Q_R8-GjscxAIAAHhyABNqYXZhLmxhbmcuVGhyb3dhYmxl1cY1Jzl3uMsDAARMAAVjYXVzZXQAFUxqYXZhL2xhbmcvVGhyb3d
 hYmxlO0wADWRldGFpbE1lc3NhZ2V0ABJMamF2YS9sYW5nL1N0cmluZztbAApzdGFja1RyYWNldAAeW0xqYXZhL2xhbmcvU3RhY2tUcmFjZUVsZW1lbnQ7TAAUc3V
 wcHJlc3NlZEV4Y2VwdGlvbnN0ABBMamF2YS91dGlsL0xpc3Q7eHBxAH4AB3QAREpvYiBmYWlsZWQgZHVlIHRvIGV4Y2VwdGlvbiBVbmFibGUgdG8gc3RvcCBWTVt
 Eb21haW5Sb3V0ZXJ8ci03NjEtVk1ddXIAHltMamF2YS5sYW5nLlN0YWNrVHJhY2VFbGVtZW50OwJGKjw8_SI5AgAAeHANc3IAG2phdmEubGFuZy5TdGFja1R
 yYWNlRWxlbWVudGEJxZomNt2FAgAESQAKbGluZU51bWJlckwADmRlY2xhcmluZ0NsYXNzcQB-AARMAAhmaWxlTm
 2014-08-21 22:42:19,885 ERROR [c.c.v.VmWorkJobDispatcher] 
 (Work-Job-Executor-149:ctx-5eeadd75 job-8131/job-8304) Unable to c
 omplete AsyncJobVO {id:8304, userId: 1, accountId: 1, instanceType: null, 
 instanceId: null, cmd: com.cloud.vm.VmWorkStop, cm
 dInfo: 
 rO0ABXNyABdjb20uY2xvdWQudm0uVm1Xb3JrU3RvcALQ4GymiWjjAgABWgAHY2xlYW51cHhyABNjb20uY2xvdWQudm0uVm1Xb3Jrn5m2VvAlZ2sCAARKA
 AlhY2NvdW50SWRKAAZ1c2VySWRKAAR2bUlkTAALaGFuZGxlck5hbWV0ABJMamF2YS9sYW5nL1N0cmluZzt4cAABAAEDBnQAGVZpc
 nR1YWxNYWNoaW5lTWFuYWdlckltcGwA, cmdVersion: 0, status: IN_PROGRESS, 
 processStatus: 0, resultCode:

[jira] [Updated] (CLOUDSTACK-7429) [LXC][UI] hypervisor dropdown in advance zone with SG is not showing LXC hypervisor


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

Animesh Chaturvedi updated CLOUDSTACK-7429:
---

Assignee: Kishan Kavala

 [LXC][UI] hypervisor dropdown in advance zone with SG is not showing LXC 
 hypervisor
 ---

 Key: CLOUDSTACK-7429
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7429
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.5.0
Reporter: shweta agarwal
Assignee: Kishan Kavala
Priority: Blocker
 Fix For: 4.5.0

 Attachments: lxc-sg.png


 Repro Steps :
 Try creating a SG enabled advance zone with LXC hypervisor. 
 Bug:
 Hypervisor dropdown is not showing LXC hypervisor



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

[jira] [Updated] (CLOUDSTACK-7382) [LXC] [UI] add rhel 7 in OS type dropdown of register templates


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

Animesh Chaturvedi updated CLOUDSTACK-7382:
---

Assignee: Kishan Kavala

 [LXC] [UI] add rhel 7 in OS type dropdown of register templates
 ---

 Key: CLOUDSTACK-7382
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7382
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM, UI
Affects Versions: 4.5.0
Reporter: shweta agarwal
Assignee: Kishan Kavala
Priority: Blocker
 Fix For: 4.5.0


 Repro steps
 Try to register  rhel 7 template on rhel 7 LXC setup .
 Bug:
 OS types rhel 7 not shown in UI in drop down
 We should also remove other non Linux based OS from this list in case of LXC



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

[jira] [Updated] (CLOUDSTACK-6838) Add test cases for download url expiration functionality


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

Animesh Chaturvedi updated CLOUDSTACK-6838:
---

Priority: Major  (was: Critical)

 Add test cases for download url expiration functionality
 

 Key: CLOUDSTACK-6838
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6838
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.4.0
Reporter: Nitin Mehta
Assignee: Nitin Mehta
 Fix For: 4.5.0


 Download urls for template/volume should expire after configurable time.
 We should add test cases for download url expiration functionality if it 
 doesnt already exist.



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

[jira] [Created] (CLOUDSTACK-7434) [Automation] Fix the script test_custom_hostname.py - Internal name comparision appears to be wrong

Chandan Purushothama created CLOUDSTACK-7434:


 Summary: [Automation] Fix the script test_custom_hostname.py - 
Internal name comparision appears to be wrong
 Key: CLOUDSTACK-7434
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7434
 Project: CloudStack
  Issue Type: Test
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Priority: Critical
 Fix For: 4.5.0



Error Log from the client results info:


requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
(1): 10.220.135.69
requests.packages.urllib3.connectionpool: DEBUG: GET 
/client/api?apiKey=YuaraAK9l9g2KJCAw3APnrD2aNpVmhAesCvWFxlDvGCb0NcARH_sKQxfRM6WF-SCAxikI8awlxCrmw010lUFzgresponse=jsoncommand=listVirtualMachinessignature=J07ySQE7LwJA%2FYsOK4ouiEPsM7Y%3Did=6548a12c-b999-495b-83bc-b928dcee99eblistall=True
 HTTP/1.1 200 1645
test_01_user_provided_hostname 
(integration.component.test_custom_hostname.TestInstanceNameFlagTrue): DEBUG: 
Response : [{domain : u'ROOT', domainid : 
u'56ab18f0-2b4d-11e4-89bd-1e5d0e053e75', haenable : False, templatename : 
u'CentOS 5.6(64-bit) no GUI (XenServer)', securitygroup : [], zoneid : 
u'eb811e7d-59d4-4c72-a965-80d9e30572d1', cpunumber : 1, ostypeid : 142, 
passwordenabled : False, instancename : u'i-220-406-VM', id : 
u'6548a12c-b999-495b-83bc-b928dcee99eb', hostname : u'cl09-B-02', displayvm : 
True, state : u'Running', guestosid : u'56bf8060-2b4d-11e4-89bd-1e5d0e053e75', 
details : {hypervisortoolsversion : u'xenserver56'}, memory : 128, 
serviceofferingid : u'27fc8179-da86-419e-99dd-f438e7b91c63', zonename : 
u'XenRT-Zone-0', isdynamicallyscalable : True, displayname : u'TestVM', tags : 
[], nic : [{networkid : u'435fb179-7868-48bd-bfb7-0efa86ee93ef', macaddress : 
u'02:00:56:8b:00:01', isolationuri : u'vlan://3074', type : u'Isolated', 
broadcasturi : u'vlan://3074', traffictype : u'Guest', netmask : 
u'255.255.255.0', ipaddress : u'192.168.200.171', id : 
u'95c36dd9-31e7-4be1-899b-20d5a36bf322', networkname : 
u'test-TestInstanceNameFlagTrue-test_01_custom_hostname_instancename_false-AWTN42-network',
 gateway : u'192.168.200.1', isdefault : True}], cpuspeed : 100, templateid : 
u'56af8f20-2b4d-11e4-89bd-1e5d0e053e75', affinitygroup : [], account : 
u'test-TestInstanceNameFlagTrue-test_01_custom_hostname_instancename_false-AWTN42',
 hostid : u'1065d9b2-260a-4642-bffe-b2523db3d798', name : 
u'VM-6548a12c-b999-495b-83bc-b928dcee99eb', created : 
u'2014-08-24T09:17:35+', hypervisor : u'XenServer', rootdevicetype : 
u'ROOT', rootdeviceid : 0, serviceofferingname : u'Tiny Instance', 
templatedisplaytext : u'CentOS 5.6(64-bit) no GUI (XenServer)'}]
test_01_user_provided_hostname 
(integration.component.test_custom_hostname.TestInstanceNameFlagTrue): DEBUG: 
vm.displayname: TestVM, original: TestVM
test_01_user_provided_hostname 
(integration.component.test_custom_hostname.TestInstanceNameFlagTrue): DEBUG: 
select id from account where uuid = 'd7313bc7-14ce-4df1-8949-f70c542e98a4';
test_01_user_provided_hostname 
(integration.component.test_custom_hostname.TestInstanceNameFlagTrue): DEBUG: 
select id from vm_instance where uuid = '6548a12c-b999-495b-83bc-b928dcee99eb';
test_01_user_provided_hostname 
(integration.component.test_custom_hostname.TestInstanceNameFlagTrue): DEBUG: 
Query result: 406
test_01_user_provided_hostname 
(integration.component.test_custom_hostname.TestInstanceNameFlagTrue): DEBUG: 
Internal name: i-220-406-TestVM
test_01_user_provided_hostname 
(integration.component.test_custom_hostname.TestInstanceNameFlagTrue): 
CRITICAL: FAILED: test_01_user_provided_hostname: ['Traceback (most recent call 
last):\n', '  File /usr/lib/python2.7/unittest/case.py, line 332, in run\n
testMethod()\n', '  File 
/root/cloudstack/test/integration/component/test_custom_hostname.py, line 
289, in test_01_user_provided_hostname\nVM internal name should match with 
that of the format\n', '  File /usr/lib/python2.7/unittest/case.py, line 
516, in assertEqual\nassertion_func(first, second, msg=msg)\n', '  File 
/usr/lib/python2.7/unittest/case.py, line 927, in assertMultiLineEqual\n
self.fail(self._formatMessage(msg, standardMsg))\n', '  File 
/usr/lib/python2.7/unittest/case.py, line 413, in fail\nraise 
self.failureException(msg)\n', 'AssertionError: VM internal name should match 
with that of the format\n']
-  end captured logging  -

==
FAIL: @Desc: Test whether cloudstack allows duplicate vm instance names in the 
diff networks
--
Traceback (most recent call last):

[jira] [Commented] (CLOUDSTACK-7435) Changing Instance/VM Ownership not tied into UI feedback system


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14111297#comment-14111297
 ] 

Jessica Wang commented on CLOUDSTACK-7435:
--

https://issues.citrite.net/browse/CS-20160

 Changing Instance/VM Ownership not tied into UI feedback system
 ---

 Key: CLOUDSTACK-7435
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7435
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Jessica Wang
Assignee: Jessica Wang

 1. Create a VM Instance in CCP 4.3.0.1.
 2. Power it off.
 3. Use the Change Ownership button in the CCP UI when viewing the VM 
 Instance details to move ownership of the VM to another Account (in my case 
 from the default Admin account to a custom NormalUsers account).
 Expected: Visual confirmation that the Change Ownership request was 
 successful.
 Actual: The Web Browser will send one API request requesting the ownership 
 change. The main panel where information about the VM is stored will show the 
 pulsing circle icon and not stop.
 No asynchronous notification is added to the notifications pane to confirm 
 the account change was successful. The end user has to change to another 
 location and back to the instance details to confirm the change in ownership 
 occurred.



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

[jira] [Created] (CLOUDSTACK-7435) Changing Instance/VM Ownership not tied into UI feedback system

Jessica Wang created CLOUDSTACK-7435:


 Summary: Changing Instance/VM Ownership not tied into UI feedback 
system
 Key: CLOUDSTACK-7435
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7435
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: UI
Reporter: Jessica Wang
Assignee: Jessica Wang




1. Create a VM Instance in CCP 4.3.0.1.
2. Power it off.
3. Use the Change Ownership button in the CCP UI when viewing the VM Instance 
details to move ownership of the VM to another Account (in my case from the 
default Admin account to a custom NormalUsers account).

Expected: Visual confirmation that the Change Ownership request was successful.

Actual: The Web Browser will send one API request requesting the ownership 
change. The main panel where information about the VM is stored will show the 
pulsing circle icon and not stop.

No asynchronous notification is added to the notifications pane to confirm the 
account change was successful. The end user has to change to another location 
and back to the instance details to confirm the change in ownership occurred.




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

[jira] [Updated] (CLOUDSTACK-7435) Changing Instance/VM Ownership not tied into UI feedback system


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

Jessica Wang updated CLOUDSTACK-7435:
-

Attachment: jessica1.PNG

 Changing Instance/VM Ownership not tied into UI feedback system
 ---

 Key: CLOUDSTACK-7435
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7435
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Jessica Wang
Assignee: Jessica Wang
 Attachments: jessica1.PNG


 1. Create a VM Instance in CCP 4.3.0.1.
 2. Power it off.
 3. Use the Change Ownership button in the CCP UI when viewing the VM 
 Instance details to move ownership of the VM to another Account (in my case 
 from the default Admin account to a custom NormalUsers account).
 Expected: Visual confirmation that the Change Ownership request was 
 successful.
 Actual: The Web Browser will send one API request requesting the ownership 
 change. The main panel where information about the VM is stored will show the 
 pulsing circle icon and not stop.
 No asynchronous notification is added to the notifications pane to confirm 
 the account change was successful. The end user has to change to another 
 location and back to the instance details to confirm the change in ownership 
 occurred.



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

[jira] [Reopened] (CLOUDSTACK-7133) [Automation] Failed to reboot Virtual Machine - Runtime Exception - Unable to Start VM


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

Chandan Purushothama reopened CLOUDSTACK-7133:
--


The failure happens repeatedly. For more information please refer to 
http://ccp-tests.xenrt.xs.citrite.net/jenkins/view/Goleta-Regression/job/xenrt-regression-adv-xs/10/testReport/integration.component.test_base_image_updation/TestBaseImageUpdate/test_04_reoccuring_snapshot_rules/

 [Automation] Failed to reboot Virtual Machine - Runtime Exception - Unable to 
 Start VM
 --

 Key: CLOUDSTACK-7133
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7133
 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: Chandan Purushothama
Assignee: Koushik Das
Priority: Critical
 Fix For: 4.5.0

 Attachments: management-server(1).zip


 =
 Runtime Exception during VM Reboot Job:
 =
 2014-07-11 15:10:51,329 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (Work-Job-Executor-119:ctx-2cd21b46 job-420/job-422) Complete async job-422, 
 jobStatus: FAILED, resultCode: 0, result: 
 rO0ABXNyABpqYXZhLmxhbmcuUnVudGltZUV4Y2VwdGlvbp5fBkcKNIPlAgAAeHIAE2phdmEubGFuZy5FeGNlcHRpb27Q_R8-GjscxAIAAHhyABNqYXZhLmxhbmcuVGhyb3dhYmxl1cY1Jzl3uMsDAARMAAVjYXVzZXQAFUxqYXZhL2xhbmcvVGhyb3dhYmxlO0wADWRldGFpbE1lc3NhZ2V0ABJMamF2YS9sYW5nL1N0cmluZztbAApzdGFja1RyYWNldAAeW0xqYXZhL2xhbmcvU3RhY2tUcmFjZUVsZW1lbnQ7TAAUc3VwcHJlc3NlZEV4Y2VwdGlvbnN0ABBMamF2YS91dGlsL0xpc3Q7eHBxAH4AB3QAlkpvYiBmYWlsZWQgZHVlIHRvIGV4Y2VwdGlvbiBSZXNvdXJjZSBbSG9zdDoxXSBpcyB1bnJlYWNoYWJsZTogSG9zdCAxOiBVbmFibGUgdG8gc3RhcnQgaW5zdGFuY2UgZHVlIHRvIGNhbid0IGZpbmQgcmVhZHkgdGVtcGxhdGU6IDIwMyBmb3IgZGF0YSBjZW50ZXIgMXVyAB5bTGphdmEubGFuZy5TdGFja1RyYWNlRWxlbWVudDsCRio8PP0iOQIAAHhwDnNyABtqYXZhLmxhbmcuU3RhY2tUcmFjZUVsZW1lbnRhCcWaJjbdhQIABEkACmxpbmVOdW1iZXJMAA5kZWNsYXJpbmdDbGFzc3EAfgAETAAIZmlsZU5hbWVxAH4ABEwACm1ldGhvZE5hbWVxAH4ABHhwcnQAIGNvbS5jbG91ZC52bS5WbVdvcmtKb2JEaXNwYXRjaGVydAAYVm1Xb3JrSm9iRGlzcGF0Y2hlci5qYXZhdAAGcnVuSm9ic3EAfgALAAAB-3QAP29yZy5hcGFjaGUuY2xvdWRzdGFjay5mcmFtZXdvcmsuam9icy5pbXBsLkFzeW5jSm9iTWFuYWdlckltcGwkNXQAGEFzeW5jSm9iTWFuYWdlckltcGwuamF2YXQADHJ1bkluQ29udGV4dHNxAH4ACwAAADF0AD5vcmcuYXBhY2hlLmNsb3Vkc3RhY2subWFuYWdlZC5jb250ZXh0Lk1hbmFnZWRDb250ZXh0UnVubmFibGUkMXQAG01hbmFnZWRDb250ZXh0UnVubmFibGUuamF2YXQAA3J1bnNxAH4ACwAAADh0AEJvcmcuYXBhY2hlLmNsb3Vkc3RhY2subWFuYWdlZC5jb250ZXh0LmltcGwuRGVmYXVsdE1hbmFnZWRDb250ZXh0JDF0ABpEZWZhdWx0TWFuYWdlZENvbnRleHQuamF2YXQABGNhbGxzcQB-AAsAAABndABAb3JnLmFwYWNoZS5jbG91ZHN0YWNrLm1hbmFnZWQuY29udGV4dC5pbXBsLkRlZmF1bHRNYW5hZ2VkQ29udGV4dHEAfgAadAAPY2FsbFdpdGhDb250ZXh0c3EAfgALNXEAfgAdcQB-ABp0AA5ydW5XaXRoQ29udGV4dHNxAH4ACwAAAC50ADxvcmcuYXBhY2hlLmNsb3Vkc3RhY2subWFuYWdlZC5jb250ZXh0Lk1hbmFnZWRDb250ZXh0UnVubmFibGVxAH4AFnEAfgAXc3EAfgALAAAB0HEAfgARcQB-ABJxAH4AF3NxAH4ACwAAAdd0AC5qYXZhLnV0aWwuY29uY3VycmVudC5FeGVjdXRvcnMkUnVubmFibGVBZGFwdGVydAAORXhlY3V0b3JzLmphdmFxAH4AG3NxAH4ACwAAAU50ACRqYXZhLnV0aWwuY29uY3VycmVudC5GdXR1cmVUYXNrJFN5bmN0AA9GdXR1cmVUYXNrLmphdmF0AAhpbm5lclJ1bnNxAH4ACwAAAKZ0AB9qYXZhLnV0aWwuY29uY3VycmVudC5GdXR1cmVUYXNrcQB-AClxAH4AF3NxAH4ACwAABFZ0ACdqYXZhLnV0aWwuY29uY3VycmVudC5UaHJlYWRQb29sRXhlY3V0b3J0ABdUaHJlYWRQb29sRXhlY3V0b3IuamF2YXQACXJ1bldvcmtlcnNxAH4ACwAAAlt0AC5qYXZhLnV0aWwuY29uY3VycmVudC5UaHJlYWRQb29sRXhlY3V0b3IkV29ya2VycQB-AC9xAH4AF3NxAH4ACwAAAtJ0ABBqYXZhLmxhbmcuVGhyZWFkdAALVGhyZWFkLmphdmFxAH4AF3NyACZqYXZhLnV0aWwuQ29sbGVjdGlvbnMkVW5tb2RpZmlhYmxlTGlzdPwPJTG17I4QAgABTAAEbGlzdHEAfgAGeHIALGphdmEudXRpbC5Db2xsZWN0aW9ucyRVbm1vZGlmaWFibGVDb2xsZWN0aW9uGUIAgMte9x4CAAFMAAFjdAAWTGphdmEvdXRpbC9Db2xsZWN0aW9uO3hwc3IAE2phdmEudXRpbC5BcnJheUxpc3R4gdIdmcdhnQMAAUkABHNpemV4cAB3BAB4cQB-ADt4
 2014-07-11 15:10:51,338 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (Work-Job-Executor-119:ctx-2cd21b46 job-420/job-422) Done executing 
 com.cloud.vm.VmWorkStart for job-422
 2014-07-11 15:10:51,343 DEBUG [c.c.v.UserVmManagerImpl] 
 (API-Job-Executor-108:ctx-d1b37d15 job-420 ctx-b9cc76f0) Unable to start VM 
 f1d98737-f934-4811-b7ef-402844e3b451
 java.lang.RuntimeException: Job failed due to exception Resource [Host:1] is 
 unreachable: Host 1: Unable to start instance due to can't find ready 
 template: 203 for data center 1
   at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:114)
   at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:507)
   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

[jira] [Resolved] (CLOUDSTACK-7339) [UI] Delete Host button is missing in the UI

2014-08-26 Thread ASF subversion and git services (JIRA)


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

Brian Federle resolved CLOUDSTACK-7339.
---

Resolution: Fixed

 [UI] Delete Host button is missing in the UI
 

 Key: CLOUDSTACK-7339
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7339
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.5.0
Reporter: Abhinav Roy
Assignee: Brian Federle
Priority: Critical
 Fix For: 4.5.0

 Attachments: delete_host_missing.jpg


 Steps :
 ===
 1. Login to CS from UI
 2. Goto Infrastructure -  Hosts -  Hostname and put the host to 
 maintenance mode.
 3. Try to delete the Host from UI
 Expected behavior :
 ==
 UI button to delete host should be present.
 Observed behavior :
 ==
 UI button to delete host is missing.
 Attaching a screenshot for the same.



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

[jira] [Commented] (CLOUDSTACK-7339) [UI] Delete Host button is missing in the UI


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14111331#comment-14111331
 ] 

ASF subversion and git services commented on CLOUDSTACK-7339:
-

Commit eee93aef3d217babbd76f08d425f3b8c7c984fba in cloudstack's branch 
refs/heads/master from [~bfederle]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=eee93ae ]

CLOUDSTACK-7339: Fix missing delete host action

Restore hidden remove host action, caused by misplaced preFilter
function


 [UI] Delete Host button is missing in the UI
 

 Key: CLOUDSTACK-7339
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7339
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.5.0
Reporter: Abhinav Roy
Assignee: Brian Federle
Priority: Critical
 Fix For: 4.5.0

 Attachments: delete_host_missing.jpg


 Steps :
 ===
 1. Login to CS from UI
 2. Goto Infrastructure -  Hosts -  Hostname and put the host to 
 maintenance mode.
 3. Try to delete the Host from UI
 Expected behavior :
 ==
 UI button to delete host should be present.
 Observed behavior :
 ==
 UI button to delete host is missing.
 Attaching a screenshot for the same.



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

[jira] [Resolved] (CLOUDSTACK-7435) Changing Instance/VM Ownership not tied into UI feedback system

2014-08-26 Thread ASF subversion and git services (JIRA)


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

Jessica Wang resolved CLOUDSTACK-7435.
--

Resolution: Fixed

 Changing Instance/VM Ownership not tied into UI feedback system
 ---

 Key: CLOUDSTACK-7435
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7435
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Jessica Wang
Assignee: Jessica Wang
 Attachments: jessica1.PNG


 1. Create a VM Instance in CCP 4.3.0.1.
 2. Power it off.
 3. Use the Change Ownership button in the CCP UI when viewing the VM 
 Instance details to move ownership of the VM to another Account (in my case 
 from the default Admin account to a custom NormalUsers account).
 Expected: Visual confirmation that the Change Ownership request was 
 successful.
 Actual: The Web Browser will send one API request requesting the ownership 
 change. The main panel where information about the VM is stored will show the 
 pulsing circle icon and not stop.
 No asynchronous notification is added to the notifications pane to confirm 
 the account change was successful. The end user has to change to another 
 location and back to the instance details to confirm the change in ownership 
 occurred.



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

[jira] [Commented] (CLOUDSTACK-7435) Changing Instance/VM Ownership not tied into UI feedback system


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14111337#comment-14111337
 ] 

ASF subversion and git services commented on CLOUDSTACK-7435:
-

Commit 5b221c21265f425bc37cbd5fcfd9ec58ba5bda43 in cloudstack's branch 
refs/heads/master from [~jessicawang]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5b221c2 ]

CLOUDSTACK-7435: UI  instance page  assign instance to another account  fix 
an error TypeError: json.virtualmachine is undefined [Break On This Error] var 
item = json.virtualmachine.virtualmachine; that showed after the action is 
clicked.


 Changing Instance/VM Ownership not tied into UI feedback system
 ---

 Key: CLOUDSTACK-7435
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7435
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Jessica Wang
Assignee: Jessica Wang
 Attachments: jessica1.PNG


 1. Create a VM Instance in CCP 4.3.0.1.
 2. Power it off.
 3. Use the Change Ownership button in the CCP UI when viewing the VM 
 Instance details to move ownership of the VM to another Account (in my case 
 from the default Admin account to a custom NormalUsers account).
 Expected: Visual confirmation that the Change Ownership request was 
 successful.
 Actual: The Web Browser will send one API request requesting the ownership 
 change. The main panel where information about the VM is stored will show the 
 pulsing circle icon and not stop.
 No asynchronous notification is added to the notifications pane to confirm 
 the account change was successful. The end user has to change to another 
 location and back to the instance details to confirm the change in ownership 
 occurred.



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

[jira] [Updated] (CLOUDSTACK-7435) Changing Instance/VM Ownership not tied into UI feedback system

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

Jessica Wang updated CLOUDSTACK-7435:
-

Attachment: 2_error_is_caused_by_this_API_change.PNG
1_error_on_UI.PNG

Changing Instance/VM Ownership not tied into UI feedback system
---

Key: CLOUDSTACK-7435
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7435
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: UI
Reporter: Jessica Wang
Assignee: Jessica Wang
Attachments: 1_error_on_UI.PNG,
2_error_is_caused_by_this_API_change.PNG

1. Create a VM Instance in CCP 4.3.0.1.
2. Power it off.
3. Use the Change Ownership button in the CCP UI when viewing the VM
Instance details to move ownership of the VM to another Account (in my case
from the default Admin account to a custom NormalUsers account).
Expected: Visual confirmation that the Change Ownership request was
successful.
Actual: The Web Browser will send one API request requesting the ownership
change. The main panel where information about the VM is stored will show the
pulsing circle icon and not stop.
No asynchronous notification is added to the notifications pane to confirm
the account change was successful. The end user has to change to another
location and back to the instance details to confirm the change in ownership
occurred.

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

[jira] [Updated] (CLOUDSTACK-7435) Changing Instance/VM Ownership not tied into UI feedback system


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

Jessica Wang updated CLOUDSTACK-7435:
-

Attachment: (was: jessica1.PNG)

 Changing Instance/VM Ownership not tied into UI feedback system
 ---

 Key: CLOUDSTACK-7435
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7435
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Jessica Wang
Assignee: Jessica Wang
 Attachments: 1_error_on_UI.PNG, 
 2_error_is_caused_by_this_API_change.PNG


 1. Create a VM Instance in CCP 4.3.0.1.
 2. Power it off.
 3. Use the Change Ownership button in the CCP UI when viewing the VM 
 Instance details to move ownership of the VM to another Account (in my case 
 from the default Admin account to a custom NormalUsers account).
 Expected: Visual confirmation that the Change Ownership request was 
 successful.
 Actual: The Web Browser will send one API request requesting the ownership 
 change. The main panel where information about the VM is stored will show the 
 pulsing circle icon and not stop.
 No asynchronous notification is added to the notifications pane to confirm 
 the account change was successful. The end user has to change to another 
 location and back to the instance details to confirm the change in ownership 
 occurred.



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

[jira] [Resolved] (CLOUDSTACK-4046) Can't edit global settings


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

Brian Federle resolved CLOUDSTACK-4046.
---

Resolution: Fixed

 Can't edit global settings
 --

 Key: CLOUDSTACK-4046
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4046
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.1.0
Reporter: Nicolas Lamirault
Assignee: Brian Federle
Priority: Minor
 Fix For: Future

 Attachments: CloudStack_GlobalSettingsOK.png, 
 CloudStack_GlobalSettingsOK2.png, CloudStack_GlobalSettingsOK3.png


 Hi,
 in our Cloudstack, we've got a strange behavior.
 gradually as one moves down the settings, the Edit box disappears.
 See screenshots.
 Regards



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

[jira] [Issue Comment Deleted] (CLOUDSTACK-4046) Can't edit global settings

2014-08-26 Thread ASF subversion and git services (JIRA)


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

Brian Federle updated CLOUDSTACK-4046:
--

Comment: was deleted

(was: This will be fixed in a future release, once several widget/UI refactor 
tasks have been completed.)

 Can't edit global settings
 --

 Key: CLOUDSTACK-4046
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4046
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.1.0
Reporter: Nicolas Lamirault
Assignee: Brian Federle
Priority: Minor
 Fix For: Future

 Attachments: CloudStack_GlobalSettingsOK.png, 
 CloudStack_GlobalSettingsOK2.png, CloudStack_GlobalSettingsOK3.png


 Hi,
 in our Cloudstack, we've got a strange behavior.
 gradually as one moves down the settings, the Edit box disappears.
 See screenshots.
 Regards



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

[jira] [Commented] (CLOUDSTACK-4046) Can't edit global settings


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14111356#comment-14111356
 ] 

ASF subversion and git services commented on CLOUDSTACK-4046:
-

Commit e7e6b7233bc882b559877a6048895f0d0ec1e6a6 in cloudstack's branch 
refs/heads/master from [~bfederle]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e7e6b72 ]

CLOUDSTACK-4046: Fix global settings CSS

-Truncate key/name field to prevent long strings from stretching the
 table width beyond the container bounds.

-Update min-width for truncated fields for better compatibility


 Can't edit global settings
 --

 Key: CLOUDSTACK-4046
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4046
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.1.0
Reporter: Nicolas Lamirault
Assignee: Brian Federle
Priority: Minor
 Fix For: Future

 Attachments: CloudStack_GlobalSettingsOK.png, 
 CloudStack_GlobalSettingsOK2.png, CloudStack_GlobalSettingsOK3.png


 Hi,
 in our Cloudstack, we've got a strange behavior.
 gradually as one moves down the settings, the Edit box disappears.
 See screenshots.
 Regards



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

[jira] [Resolved] (CLOUDSTACK-6265) Recover/restore VM actions: Fix icon, label, and confirmation dialog


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

Brian Federle resolved CLOUDSTACK-6265.
---

Resolution: Duplicate

Duplicate of CLOUDSTACK-6272, which was resolved a while ago.

 Recover/restore VM actions: Fix icon, label, and confirmation dialog
 

 Key: CLOUDSTACK-6265
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6265
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Brian Federle
Assignee: Brian Federle
Priority: Minor
 Fix For: 4.4.0


 (1) Label the action icon that fires recoverVirtualMachine API as Recover. 
Label the action icon that fires restoreVirtualMachine API as Reinstall. 
 (2) change text in confirmation dialog of Reinstall action as: 
 The VM will be reinstalled from template, all current data will be lost, 
 proceed with caution! Extra data volumes, if any, will not be touched.
 (3) Change Reinstall icon to use a ‘recycle’ symbol, to avoid confusion w/ 
 reboot VM
 (4) Remove text label appearance from action button, so that it is consistent 
 with other action icons



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

[jira] [Assigned] (CLOUDSTACK-3537) [UI] - when pass pageSize to the list* api calls, check against global config default.page.size


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

Brian Federle reassigned CLOUDSTACK-3537:
-

Assignee: Jessica Wang  (was: Brian Federle)

Jessica, can you verify if this older issue is relevant anymore?

 [UI] - when pass pageSize to the list* api calls, check against global config 
 default.page.size
 -

 Key: CLOUDSTACK-3537
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3537
 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: Alena Prokharchyk
Assignee: Jessica Wang
 Fix For: Future


 Global config default.page.size defines max allowed pageSize for list* api 
 calls. If no pageSize specified in the call, then its being defaulted to this 
 global config. When pageSize is passed to the call, then it shouldn't be 
 greater than default.page.size.
 The bug is: UI passed pageSize to the number of API calls w/o verifying 
 whether this number is less than default.page.size allows. And it ends up 
 with the errors on the API side Page size can't exceed max allowed page size 
 value
 Suggested fix: when UI passes pageSize param to the list* API call:
 * verify its value against default.page.size
 * if its =, pass it to the call
 * if its , then pass default.page.size to the call.



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

[jira] [Created] (CLOUDSTACK-7436) [Automation] Redundant state of the router should be BACKUP but is UNKNOWN

Chandan Purushothama created CLOUDSTACK-7436:


 Summary: [Automation] Redundant state of the router should be 
BACKUP but is UNKNOWN 
 Key: CLOUDSTACK-7436
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7436
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Automation, Test, Virtual Router
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Priority: Critical
 Fix For: 4.5.0


The following testcase reported the error message shown below:

integration.component.maint.test_redundant_router.TestRvRRedundancy.test_05_stopBackupRvR_startInstance
 (from nosetests)

*Error Message*

Redundant state of the router should be BACKUP but is UNKNOWN   Logs available 
at 
http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Serialtest=redundant_router

Stacktrace

  File /usr/lib/python2.7/unittest/case.py, line 332, in run
testMethod()
  File 
/root/cloudstack/test/integration/component/maint/test_redundant_router.py, 
line 1583, in test_05_stopBackupRvR_startInstance
Redundant state of the router should be BACKUP but is %s % 
routers[0].redundantstate
  File /usr/lib/python2.7/unittest/case.py, line 516, in assertEqual
assertion_func(first, second, msg=msg)
  File /usr/lib/python2.7/unittest/case.py, line 509, in _baseAssertEqual
raise self.failureException(msg)
'Redundant state of the router should be BACKUP but is UNKNOWN\n

Logs available at 
http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Serialtest=redundant_router
  



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

[jira] [Updated] (CLOUDSTACK-7435) Changing Instance/VM Ownership not tied into UI feedback system


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

Jessica Wang updated CLOUDSTACK-7435:
-

Attachment: (was: 2_error_is_caused_by_this_API_change.PNG)

 Changing Instance/VM Ownership not tied into UI feedback system
 ---

 Key: CLOUDSTACK-7435
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7435
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Jessica Wang
Assignee: Jessica Wang

 1. Create a VM Instance in CCP 4.3.0.1.
 2. Power it off.
 3. Use the Change Ownership button in the CCP UI when viewing the VM 
 Instance details to move ownership of the VM to another Account (in my case 
 from the default Admin account to a custom NormalUsers account).
 Expected: Visual confirmation that the Change Ownership request was 
 successful.
 Actual: The Web Browser will send one API request requesting the ownership 
 change. The main panel where information about the VM is stored will show the 
 pulsing circle icon and not stop.
 No asynchronous notification is added to the notifications pane to confirm 
 the account change was successful. The end user has to change to another 
 location and back to the instance details to confirm the change in ownership 
 occurred.



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

[jira] [Updated] (CLOUDSTACK-7435) Changing Instance/VM Ownership not tied into UI feedback system


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

Jessica Wang updated CLOUDSTACK-7435:
-

Attachment: (was: 1_error_on_UI.PNG)

 Changing Instance/VM Ownership not tied into UI feedback system
 ---

 Key: CLOUDSTACK-7435
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7435
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Jessica Wang
Assignee: Jessica Wang

 1. Create a VM Instance in CCP 4.3.0.1.
 2. Power it off.
 3. Use the Change Ownership button in the CCP UI when viewing the VM 
 Instance details to move ownership of the VM to another Account (in my case 
 from the default Admin account to a custom NormalUsers account).
 Expected: Visual confirmation that the Change Ownership request was 
 successful.
 Actual: The Web Browser will send one API request requesting the ownership 
 change. The main panel where information about the VM is stored will show the 
 pulsing circle icon and not stop.
 No asynchronous notification is added to the notifications pane to confirm 
 the account change was successful. The end user has to change to another 
 location and back to the instance details to confirm the change in ownership 
 occurred.



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

[jira] [Updated] (CLOUDSTACK-7435) Changing Instance/VM Ownership not tied into UI feedback system


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

Jessica Wang updated CLOUDSTACK-7435:
-

Attachment: 2_cause.PNG
1_error.PNG

 Changing Instance/VM Ownership not tied into UI feedback system
 ---

 Key: CLOUDSTACK-7435
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7435
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Jessica Wang
Assignee: Jessica Wang
 Attachments: 1_error.PNG, 2_cause.PNG


 1. Create a VM Instance in CCP 4.3.0.1.
 2. Power it off.
 3. Use the Change Ownership button in the CCP UI when viewing the VM 
 Instance details to move ownership of the VM to another Account (in my case 
 from the default Admin account to a custom NormalUsers account).
 Expected: Visual confirmation that the Change Ownership request was 
 successful.
 Actual: The Web Browser will send one API request requesting the ownership 
 change. The main panel where information about the VM is stored will show the 
 pulsing circle icon and not stop.
 No asynchronous notification is added to the notifications pane to confirm 
 the account change was successful. The end user has to change to another 
 location and back to the instance details to confirm the change in ownership 
 occurred.



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

[jira] [Resolved] (CLOUDSTACK-5952) [UI] VM ip address information is not shown after configuring static NAT

2014-08-26 Thread ASF subversion and git services (JIRA)


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

Brian Federle resolved CLOUDSTACK-5952.
---

   Resolution: Fixed
Fix Version/s: (was: Future)
   4.5.0

26904d1a2b0d2faf29e8110072263be3d640 HEAD asf/master master
Author: Brian Federle brian.fede...@citrix.com
Date:   Tue Aug 26 14:38:55 2014 -0700

CLOUDSTACK-5952: Add 'VM IP Address' field to IP detail view

 [UI] VM ip address information is not shown after configuring static NAT
 

 Key: CLOUDSTACK-5952
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5952
 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: Jayapal Reddy
Assignee: Brian Federle
 Fix For: 4.5.0


 1. Create a VM and acquire secondary ip address for the nic.
 2. Go to network - IP address: Enable the static nat for the for the VM 
 secondary ip address.
 3. After static nat enable success, go to ip addresses page.
 4. On public the static nat is configured, on vm name column there is no vm 
 ip address info.
   Expected: The ip address should also displayed.
 5. In API listPublicIpAddresses response has the vm ip addr info with name 
 'vmipaddress'



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

[jira] [Commented] (CLOUDSTACK-5952) [UI] VM ip address information is not shown after configuring static NAT


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-5952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14111380#comment-14111380
 ] 

ASF subversion and git services commented on CLOUDSTACK-5952:
-

Commit 26904d1a2b0d2faf29e8110072263be3d640 in cloudstack's branch 
refs/heads/master from [~bfederle]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=26904d1 ]

CLOUDSTACK-5952: Add 'VM IP Address' field to IP detail view


 [UI] VM ip address information is not shown after configuring static NAT
 

 Key: CLOUDSTACK-5952
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5952
 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: Jayapal Reddy
Assignee: Brian Federle
 Fix For: 4.5.0


 1. Create a VM and acquire secondary ip address for the nic.
 2. Go to network - IP address: Enable the static nat for the for the VM 
 secondary ip address.
 3. After static nat enable success, go to ip addresses page.
 4. On public the static nat is configured, on vm name column there is no vm 
 ip address info.
   Expected: The ip address should also displayed.
 5. In API listPublicIpAddresses response has the vm ip addr info with name 
 'vmipaddress'



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

[jira] [Created] (CLOUDSTACK-7437) [Automation] Fix the script test_escalations_snapshots.py - unable to find a snapshot with id

Chandan Purushothama created CLOUDSTACK-7437:


 Summary: [Automation] Fix the script 
test_escalations_snapshots.py - unable to find a snapshot with id
 Key: CLOUDSTACK-7437
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7437
 Project: CloudStack
  Issue Type: Test
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
 Fix For: 4.5.0


Do not add the created snapshot to the cleanup resources since it has been 
consciously deleted during the test case (test_01). Since the snapshot is no 
longer there the cleanup_resources method results in an error.

integration.component.test_escalations_snapshots.TestSnapshots.test_01_list_volume_snapshots_pagination
 (from nosetests)

*Error Message*

Job failed: {jobprocstatus : 0, created : u'2014-08-24T19:01:28+', 
jobresult : {errorcode : 530, errortext : u'unable to find a snapshot with id 
43'}, cmd : 
u'org.apache.cloudstack.api.command.user.snapshot.DeleteSnapshotCmd', userid : 
u'77df13d2-2b4d-11e4-89bd-1e5d0e053e75', jobstatus : 2, jobid : 
u'0fb9d284-9908-4e37-b176-b83eb2792399', jobresultcode : 530, jobinstanceid : 
u'2b4a7334-c477-4dbb-a870-3a6c1ed5fcfb', jobresulttype : u'object', 
jobinstancetype : u'Snapshot', accountid : 
u'77df055e-2b4d-11e4-89bd-1e5d0e053e75'}   Logs available at 
http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=escalations_snapsh

*Stacktrace*

  File /usr/lib/python2.7/unittest/case.py, line 361, in run
self.tearDown()
  File 
/root/cloudstack/test/integration/component/test_escalations_snapshots.py, 
line 106, in tearDown
cleanup_resources(self.apiClient, self.cleanup)
  File /usr/local/lib/python2.7/dist-packages/marvin/lib/utils.py, line 121, 
in cleanup_resources
obj.delete(api_client)
  File /usr/local/lib/python2.7/dist-packages/marvin/lib/base.py, line 986, 
in delete
apiclient.deleteSnapshot(cmd)
  File 
/usr/local/lib/python2.7/dist-packages/marvin/cloudstackAPI/cloudstackAPIClient.py,
 line 784, in deleteSnapshot
response = self.connection.marvinRequest(command, response_type=response, 
method=method)
  File /usr/local/lib/python2.7/dist-packages/marvin/cloudstackConnection.py, 
line 379, in marvinRequest
raise e
'Job failed: {jobprocstatus : 0, created : u\'2014-08-24T19:01:28+\', 
jobresult : {errorcode : 530, errortext : u\'unable to find a snapshot with id 
43\'}, cmd : 
u\'org.apache.cloudstack.api.command.user.snapshot.DeleteSnapshotCmd\', userid 
: u\'77df13d2-2b4d-11e4-89bd-1e5d0e053e75\', jobstatus : 2, jobid : 
u\'0fb9d284-9908-4e37-b176-b83eb2792399\', jobresultcode : 530, jobinstanceid : 
u\'2b4a7334-c477-4dbb-a870-3a6c1ed5fcfb\', jobresulttype : u\'object\', 
jobinstancetype : u\'Snapshot\', accountid : 
u\'77df055e-2b4d-11e4-89bd-1e5d0e053e75\'}\n

Logs available at 
http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=escalations_snapsh
  





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

[jira] [Updated] (CLOUDSTACK-4749) Clean up stylesheet code


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

Brian Federle updated CLOUDSTACK-4749:
--

Assignee: (was: Brian Federle)

 Clean up stylesheet code
 

 Key: CLOUDSTACK-4749
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4749
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Brian Federle
 Fix For: Future


 As the UI is getting more complex, need a major refactor the stylesheet to 
 reduce redundant code and help utilize newer CSS3 standards.
 This will be accomplished with SASS and associated helper libraries.



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

[jira] [Updated] (CLOUDSTACK-4851) Integrate SASS into UI


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

Brian Federle updated CLOUDSTACK-4851:
--

Assignee: (was: Brian Federle)

 Integrate SASS into UI
 --

 Key: CLOUDSTACK-4851
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4851
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server, UI
Affects Versions: 4.3.0
Reporter: Brian Federle
 Fix For: Future


 Moving forward, CloudStack will be using SASS for styling instead of CSS. 
 This will require refactoring existing CSS as SASS.
 This should compile down ui/stylesheets/cloudstack.scss to 
 ui/stylesheets/cloudstack.css.



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

[jira] [Updated] (CLOUDSTACK-4748) Update UI visual appearance


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

Brian Federle updated CLOUDSTACK-4748:
--

Assignee: (was: Brian Federle)

 Update UI visual appearance
 ---

 Key: CLOUDSTACK-4748
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4748
 Project: CloudStack
  Issue Type: Task
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Brian Federle
 Fix For: Future


 Dev branch: ui-restyle
 Functional spec: 
 https://cwiki.apache.org/confluence/display/CLOUDSTACK/Update+UI+visual+appearance
 Need a visual 'makeover' of the UI, to promote better usability and a more 
 fluid user experience in modern browsers.
 The UI workflow will remain the same, but the following elements will be 
 given a new appearance:
 -Header
 -Navigation
 -Common components: Buttons, text fields, dropdowns, tables
 -Use CSS3 transitions instead of jQuery animations
 -Use grid system for layout
 -Convert to SASS framework for cleaner code base (see subtask)
 -Use consistent color themes, matching other ASF CloudStack branding



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

[jira] [Updated] (CLOUDSTACK-5896) Need to localize doc tooltips


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

Brian Federle updated CLOUDSTACK-5896:
--

Assignee: (was: Brian Federle)

 Need to localize doc tooltips
 -

 Key: CLOUDSTACK-5896
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5896
 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: Brian Federle
 Fix For: Future


 Currently, all docs (docs.js) are hardcoded to English-only. This needs to be 
 split up into one file per language (i.e., docs.en.js, docs.ja.js, ...), and 
 loaded up per user's selected language. If there is no translation for the 
 target language, hide tooltip.



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

[jira] [Assigned] (CLOUDSTACK-7381) UI: Unable to copy apikey/secret keys from UI


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

Brian Federle reassigned CLOUDSTACK-7381:
-

Assignee: Gabor Apati-Nagy  (was: Brian Federle)

Assigning to Gabor, who wrote the original copy-paste widget.

 UI: Unable to copy apikey/secret keys from UI
 -

 Key: CLOUDSTACK-7381
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7381
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Reporter: Rohit Yadav
Assignee: Gabor Apati-Nagy

 Login and goto a user and create apikey/secretkey.
 Click on the copy button next to folded apikey string, it does not work or 
 copy to clipboard on OSX/Chrome.
 Tested on master, affecting possibly 4.4 and others branches.



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

[jira] [Commented] (CLOUDSTACK-6694) [UI]while assigning VM to internal LB(VPC),ListVMs is not listing VM nic primary and secondary IPS.


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14111490#comment-14111490
 ] 

Brian Federle commented on CLOUDSTACK-6694:
---

This is still an issue. Basically, the internal LB uses entirely separate code 
from the standard LB rules, so will need re-implementation of the secondary IP 
select box. This will require a bit of refactoring to fix.

 [UI]while assigning VM to internal LB(VPC),ListVMs is not listing VM nic 
 primary and secondary IPS.
 ---

 Key: CLOUDSTACK-6694
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6694
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.4.0
Reporter: manasaveloori
Assignee: Brian Federle
Priority: Critical
 Fix For: 4.4.0

 Attachments: InternalLB.jpg


 1. Create VPC.
 2. Create a tier network using the network offering having internal LB 
 support.
 3. Deploy VMs under this network.Acquire secondary Ips.
 4.Goto VPC -configure-tier- internal LB.configure internal LB.
 5. Assign VM to LB rule.
 Observation:
 There is no listing of primary and secondary IPs   for the VM while assigning 
 it  internal LB rule.
 attaching the screen shot.



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

[jira] [Updated] (CLOUDSTACK-6694) [UI]while assigning VM to internal LB(VPC),ListVMs is not listing VM nic primary and secondary IPS.


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

Brian Federle updated CLOUDSTACK-6694:
--


WIP branch: ui-internal-lb-subselect

 [UI]while assigning VM to internal LB(VPC),ListVMs is not listing VM nic 
 primary and secondary IPS.
 ---

 Key: CLOUDSTACK-6694
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6694
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.4.0
Reporter: manasaveloori
Assignee: Brian Federle
Priority: Critical
 Fix For: 4.4.0

 Attachments: InternalLB.jpg


 1. Create VPC.
 2. Create a tier network using the network offering having internal LB 
 support.
 3. Deploy VMs under this network.Acquire secondary Ips.
 4.Goto VPC -configure-tier- internal LB.configure internal LB.
 5. Assign VM to LB rule.
 Observation:
 There is no listing of primary and secondary IPs   for the VM while assigning 
 it  internal LB rule.
 attaching the screen shot.



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

[jira] [Updated] (CLOUDSTACK-6694) [UI]while assigning VM to internal LB(VPC),ListVMs is not listing VM nic primary and secondary IPS.


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

Brian Federle updated CLOUDSTACK-6694:
--

Remaining Estimate: 72h
 Original Estimate: 72h

 [UI]while assigning VM to internal LB(VPC),ListVMs is not listing VM nic 
 primary and secondary IPS.
 ---

 Key: CLOUDSTACK-6694
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6694
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.4.0
Reporter: manasaveloori
Assignee: Brian Federle
Priority: Critical
 Fix For: 4.4.0

 Attachments: InternalLB.jpg

   Original Estimate: 72h
  Remaining Estimate: 72h

 1. Create VPC.
 2. Create a tier network using the network offering having internal LB 
 support.
 3. Deploy VMs under this network.Acquire secondary Ips.
 4.Goto VPC -configure-tier- internal LB.configure internal LB.
 5. Assign VM to LB rule.
 Observation:
 There is no listing of primary and secondary IPs   for the VM while assigning 
 it  internal LB rule.
 attaching the screen shot.



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

[jira] [Created] (CLOUDSTACK-7438) [Automation] List tags should not return empty response

Chandan Purushothama created CLOUDSTACK-7438:


 Summary: [Automation] List tags should not return empty response
 Key: CLOUDSTACK-7438
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7438
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Priority: Critical
 Fix For: 4.5.0



=
Info from the Client results log shows creation and listing of tags:
=

test_06_template_tag (integration.component.test_tags.TestResourceTags): DEBUG: 
Sending GET Cmd : createTags===
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
(1): 10.220.135.69
requests.packages.urllib3.connectionpool: DEBUG: GET 
/client/api?apiKey=YuaraAK9l9g2KJCAw3APnrD2aNpVmhAesCvWFxlDvGCb0NcARH_sKQxfRM6WF-SCAxikI8awlxCrmw010lUFzgresourcetype=TemplateresourceIds=7f62bc5b-8e16-47fb-ab3d-12aa94532b3acommand=createTagssignature=w0XlJIylJpRdt9MTZbLL2x1z9nU%3Dtags%5B0%5D.key=OSresponse=jsontags%5B0%5D.value=CentOS
 HTTP/1.1 200 75
test_06_template_tag (integration.component.test_tags.TestResourceTags): DEBUG: 
=== Jobid: 1146e783-54e9-4bfa-8d08-981cc25c0c33 Started ===
test_06_template_tag (integration.component.test_tags.TestResourceTags): DEBUG: 
Payload: {'signature': 'utF4HLORlspxi354V8Pf8Baxsts=', 'apiKey': 
u'YuaraAK9l9g2KJCAw3APnrD2aNpVmhAesCvWFxlDvGCb0NcARH_sKQxfRM6WF-SCAxikI8awlxCrmw010lUFzg',
 'command': 'queryAsyncJobResult', 'response': 'json', 'jobid': 
u'1146e783-54e9-4bfa-8d08-981cc25c0c33'}
test_06_template_tag (integration.component.test_tags.TestResourceTags): DEBUG: 
Sending GET Cmd : queryAsyncJobResult===
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
(1): 10.220.135.69
requests.packages.urllib3.connectionpool: DEBUG: GET 
/client/api?jobid=1146e783-54e9-4bfa-8d08-981cc25c0c33apiKey=YuaraAK9l9g2KJCAw3APnrD2aNpVmhAesCvWFxlDvGCb0NcARH_sKQxfRM6WF-SCAxikI8awlxCrmw010lUFzgcommand=queryAsyncJobResultresponse=jsonsignature=utF4HLORlspxi354V8Pf8Baxsts%3D
 HTTP/1.1 200 389
test_06_template_tag (integration.component.test_tags.TestResourceTags): DEBUG: 
Response : {jobprocstatus : 0, created : u'2014-08-24T15:38:01+', cmd : 
u'org.apache.cloudstack.api.command.user.tag.CreateTagsCmd', userid : 
u'77df13d2-2b4d-11e4-89bd-1e5d0e053e75', jobstatus : 1, jobid : 
u'1146e783-54e9-4bfa-8d08-981cc25c0c33', jobresultcode : 0, jobresulttype : 
u'object', jobresult : {success : True}, accountid : 
u'77df055e-2b4d-11e4-89bd-1e5d0e053e75'}
test_06_template_tag (integration.component.test_tags.TestResourceTags): DEBUG: 
===Jobid:1146e783-54e9-4bfa-8d08-981cc25c0c33 ; StartTime:Sun Aug 24 15:38:01 
2014 ; EndTime:Sun Aug 24 15:38:01 2014 ; TotalTime:0===
test_06_template_tag (integration.component.test_tags.TestResourceTags): DEBUG: 
Response : {jobprocstatus : 0, created : u'2014-08-24T15:38:01+', cmd : 
u'org.apache.cloudstack.api.command.user.tag.CreateTagsCmd', userid : 
u'77df13d2-2b4d-11e4-89bd-1e5d0e053e75', jobstatus : 1, jobid : 
u'1146e783-54e9-4bfa-8d08-981cc25c0c33', jobresultcode : 0, jobresulttype : 
u'object', jobresult : {success : True}, accountid : 
u'77df055e-2b4d-11e4-89bd-1e5d0e053e75'}
test_06_template_tag (integration.component.test_tags.TestResourceTags): DEBUG: 
Tag created: {'success': True}
test_06_template_tag (integration.component.test_tags.TestResourceTags): DEBUG: 
Payload: {'account': u'test-TestResourceTags-SKLJM8', 'domainid': 
u'56ab18f0-2b4d-11e4-89bd-1e5d0e053e75', 'resourceType': 'Template', 'value': 
'CentOS', 'apiKey': 
u'YuaraAK9l9g2KJCAw3APnrD2aNpVmhAesCvWFxlDvGCb0NcARH_sKQxfRM6WF-SCAxikI8awlxCrmw010lUFzg',
 'command': 'listTags', 'key': 'OS', 'signature': 
'mcKSukLYBWmPOlsgS4NKx1OXXZ8=', 'response': 'json', 'listall': True}
test_06_template_tag (integration.component.test_tags.TestResourceTags): DEBUG: 
Sending GET Cmd : listTags===
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
(1): 10.220.135.69
requests.packages.urllib3.connectionpool: DEBUG: GET 
/client/api?account=test-TestResourceTags-SKLJM8domainid=56ab18f0-2b4d-11e4-89bd-1e5d0e053e75resourceType=Templatevalue=CentOSapiKey=YuaraAK9l9g2KJCAw3APnrD2aNpVmhAesCvWFxlDvGCb0NcARH_sKQxfRM6WF-SCAxikI8awlxCrmw010lUFzgcommand=listTagskey=OSsignature=mcKSukLYBWmPOlsgS4NKx1OXXZ8%3Dresponse=jsonlistall=True
 HTTP/1.1 200 28
test_06_template_tag (integration.component.test_tags.TestResourceTags): DEBUG: 
Response : None
test_06_template_tag (integration.component.test_tags.TestResourceTags): 
CRITICAL: FAILED: test_06_template_tag: ['Traceback (most recent call 
last):\n', '  File /usr/lib/python2.7/unittest/case.py, line 332, in

[jira] [Updated] (CLOUDSTACK-7438) [Automation] List tags should not return empty response


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

Chandan Purushothama updated CLOUDSTACK-7438:
-

Description: 
Two tests failed : *test_06_template_tag*  *test_15_project_tag*

=
Info from the Client results log shows creation and listing of tags:
=


FAIL: Test creation, listing and deletion tag on templates
--
Traceback (most recent call last):
  File /root/cloudstack/test/integration/component/test_tags.py, line 1002, 
in test_06_template_tag
List tags should not return empty response
AssertionError: List tags should not return empty response
  begin captured stdout  -
=== TestName: test_06_template_tag | Status : FAILED ===
.
.
.
.
test_06_template_tag (integration.component.test_tags.TestResourceTags): DEBUG: 
Sending GET Cmd : createTags===
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
(1): 10.220.135.69
requests.packages.urllib3.connectionpool: DEBUG: GET 
/client/api?apiKey=YuaraAK9l9g2KJCAw3APnrD2aNpVmhAesCvWFxlDvGCb0NcARH_sKQxfRM6WF-SCAxikI8awlxCrmw010lUFzgresourcetype=TemplateresourceIds=7f62bc5b-8e16-47fb-ab3d-12aa94532b3acommand=createTagssignature=w0XlJIylJpRdt9MTZbLL2x1z9nU%3Dtags%5B0%5D.key=OSresponse=jsontags%5B0%5D.value=CentOS
 HTTP/1.1 200 75
test_06_template_tag (integration.component.test_tags.TestResourceTags): DEBUG: 
=== Jobid: 1146e783-54e9-4bfa-8d08-981cc25c0c33 Started ===
test_06_template_tag (integration.component.test_tags.TestResourceTags): DEBUG: 
Payload: {'signature': 'utF4HLORlspxi354V8Pf8Baxsts=', 'apiKey': 
u'YuaraAK9l9g2KJCAw3APnrD2aNpVmhAesCvWFxlDvGCb0NcARH_sKQxfRM6WF-SCAxikI8awlxCrmw010lUFzg',
 'command': 'queryAsyncJobResult', 'response': 'json', 'jobid': 
u'1146e783-54e9-4bfa-8d08-981cc25c0c33'}
test_06_template_tag (integration.component.test_tags.TestResourceTags): DEBUG: 
Sending GET Cmd : queryAsyncJobResult===
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
(1): 10.220.135.69
requests.packages.urllib3.connectionpool: DEBUG: GET 
/client/api?jobid=1146e783-54e9-4bfa-8d08-981cc25c0c33apiKey=YuaraAK9l9g2KJCAw3APnrD2aNpVmhAesCvWFxlDvGCb0NcARH_sKQxfRM6WF-SCAxikI8awlxCrmw010lUFzgcommand=queryAsyncJobResultresponse=jsonsignature=utF4HLORlspxi354V8Pf8Baxsts%3D
 HTTP/1.1 200 389
test_06_template_tag (integration.component.test_tags.TestResourceTags): DEBUG: 
Response : {jobprocstatus : 0, created : u'2014-08-24T15:38:01+', cmd : 
u'org.apache.cloudstack.api.command.user.tag.CreateTagsCmd', userid : 
u'77df13d2-2b4d-11e4-89bd-1e5d0e053e75', jobstatus : 1, jobid : 
u'1146e783-54e9-4bfa-8d08-981cc25c0c33', jobresultcode : 0, jobresulttype : 
u'object', jobresult : {success : True}, accountid : 
u'77df055e-2b4d-11e4-89bd-1e5d0e053e75'}
test_06_template_tag (integration.component.test_tags.TestResourceTags): DEBUG: 
===Jobid:1146e783-54e9-4bfa-8d08-981cc25c0c33 ; StartTime:Sun Aug 24 15:38:01 
2014 ; EndTime:Sun Aug 24 15:38:01 2014 ; TotalTime:0===
test_06_template_tag (integration.component.test_tags.TestResourceTags): DEBUG: 
Response : {jobprocstatus : 0, created : u'2014-08-24T15:38:01+', cmd : 
u'org.apache.cloudstack.api.command.user.tag.CreateTagsCmd', userid : 
u'77df13d2-2b4d-11e4-89bd-1e5d0e053e75', jobstatus : 1, jobid : 
u'1146e783-54e9-4bfa-8d08-981cc25c0c33', jobresultcode : 0, jobresulttype : 
u'object', jobresult : {success : True}, accountid : 
u'77df055e-2b4d-11e4-89bd-1e5d0e053e75'}
test_06_template_tag (integration.component.test_tags.TestResourceTags): DEBUG: 
Tag created: {'success': True}
test_06_template_tag (integration.component.test_tags.TestResourceTags): DEBUG: 
Payload: {'account': u'test-TestResourceTags-SKLJM8', 'domainid': 
u'56ab18f0-2b4d-11e4-89bd-1e5d0e053e75', 'resourceType': 'Template', 'value': 
'CentOS', 'apiKey': 
u'YuaraAK9l9g2KJCAw3APnrD2aNpVmhAesCvWFxlDvGCb0NcARH_sKQxfRM6WF-SCAxikI8awlxCrmw010lUFzg',
 'command': 'listTags', 'key': 'OS', 'signature': 
'mcKSukLYBWmPOlsgS4NKx1OXXZ8=', 'response': 'json', 'listall': True}
test_06_template_tag (integration.component.test_tags.TestResourceTags): DEBUG: 
Sending GET Cmd : listTags===
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
(1): 10.220.135.69
requests.packages.urllib3.connectionpool: DEBUG: GET 
/client/api?account=test-TestResourceTags-SKLJM8domainid=56ab18f0-2b4d-11e4-89bd-1e5d0e053e75resourceType=Templatevalue=CentOSapiKey=YuaraAK9l9g2KJCAw3APnrD2aNpVmhAesCvWFxlDvGCb0NcARH_sKQxfRM6WF-SCAxikI8awlxCrmw010lUFzgcommand=listTagskey=OSsignature=mcKSukLYBWmPOlsgS4NKx1OXXZ8%3Dresponse=jsonlistall=True
 HTTP/1.1 200 28
test_06_template_tag (integration.component.test_tags.TestResourceTags): DEBUG: 
Response : None

[jira] [Created] (CLOUDSTACK-7439) [Automation] Fix the script test_tags.py - Unable to find resource by uuid since it is already destroyed

Chandan Purushothama created CLOUDSTACK-7439:


 Summary: [Automation] Fix the script test_tags.py - Unable to 
find resource by uuid since it is already destroyed 
 Key: CLOUDSTACK-7439
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7439
 Project: CloudStack
  Issue Type: Test
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Priority: Critical
 Fix For: 4.5.0


I am not sure whether we allow creation of tags on destroyed VMs. Currently 
that Use case fails.

*Error Message*

Job failed: {jobprocstatus : 0, created : u'2014-08-24T15:44:22+', cmd : 
u'org.apache.cloudstack.api.command.user.tag.CreateTagsCmd', userid : 
u'77df13d2-2b4d-11e4-89bd-1e5d0e053e75', jobstatus : 2, jobid : 
u'37f08e53-2f4a-40d5-a241-687948b2afb8', jobresultcode : 530, jobresulttype : 
u'object', jobresult : {errorcode : 530, errortext : u'Unable to find resource 
by uuid 9ea1264a-3914-41b4-9807-28e442ce752d and type UserVm'}, accountid : 
u'77df055e-2b4d-11e4-89bd-1e5d0e053e75'}   Logs available at 
http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=tags

Stacktrace

  File /usr/lib/python2.7/unittest/case.py, line 332, in run
testMethod()
  File /root/cloudstack/test/integration/component/test_tags.py, line 2249, 
in test_22_create_tag_destroyed_vm
tags={'region': 'India'}
  File /usr/local/lib/python2.7/dist-packages/marvin/lib/base.py, line 3783, 
in create
return Tag(apiclient.createTags(cmd).__dict__)
  File 
/usr/local/lib/python2.7/dist-packages/marvin/cloudstackAPI/cloudstackAPIClient.py,
 line 2294, in createTags
response = self.connection.marvinRequest(command, response_type=response, 
method=method)
  File /usr/local/lib/python2.7/dist-packages/marvin/cloudstackConnection.py, 
line 379, in marvinRequest
raise e
'Job failed: {jobprocstatus : 0, created : u\'2014-08-24T15:44:22+\', cmd : 
u\'org.apache.cloudstack.api.command.user.tag.CreateTagsCmd\', userid : 
u\'77df13d2-2b4d-11e4-89bd-1e5d0e053e75\', jobstatus : 2, jobid : 
u\'37f08e53-2f4a-40d5-a241-687948b2afb8\', jobresultcode : 530, jobresulttype : 
u\'object\', jobresult : {errorcode : 530, errortext : u\'Unable to find 
resource by uuid 9ea1264a-3914-41b4-9807-28e442ce752d and type UserVm\'}, 
accountid : u\'77df055e-2b4d-11e4-89bd-1e5d0e053e75\'}\n

Logs available at 
http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=tags




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

[jira] [Created] (CLOUDSTACK-7440) [Automation] Fix the script test_usage.py - Template is registered as admin's

Chandan Purushothama created CLOUDSTACK-7440:


 Summary: [Automation] Fix the script test_usage.py - Template is 
registered as admin's
 Key: CLOUDSTACK-7440
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7440
 Project: CloudStack
  Issue Type: Test
  Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Chandan Purushothama
Priority: Critical


Template got registered as admin's . Hence the event belongs to the admin. 
Please correct the template registration part of the code.

client log info:
{code}
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
(1): 10.220.135.69
requests.packages.urllib3.connectionpool: DEBUG: GET 
/client/api?jobid=4df356b8-bc11-4536-a396-2fb81f682aa4apiKey=YuaraAK9l9g2KJCAw3APnrD2aNpVmhAesCvWFxlDvGCb0NcARH_sKQxfRM6WF-SCAxikI8awlxCrmw010lUFzgcommand=queryAsyncJobResultresponse=jsonsignature=x%2B20vHzmuIb%2BanPRk0EoGtgYm0c%3D
 HTTP/1.1 200 1325
test_01_template_usage (integration.component.test_usage.TestTemplateUsage): 
DEBUG: Response : {jobprocstatus : 0, created : u'2014-08-24T16:18:58+', 
jobresult : {domain : u'ROOT', domainid : 
u'56ab18f0-2b4d-11e4-89bd-1e5d0e053e75', ostypename : u'CentOS 5.3 (64-bit)', 
zoneid : u'eb811e7d-59d4-4c72-a965-80d9e30572d1', displaytext : u'Template', 
ostypeid : u'56b1e2f2-2b4d-11e4-89bd-1e5d0e053e75', passwordenabled : False, id 
: u'cba11332-8bd9-40a4-bb90-79a47ee170fd', size : 21474836480, isready : True, 
format : u'VHD', templatetype : u'USER', details : {platform : 
u'viridian:true;acpi:1;apic:true;pae:true;nx:true', 
Message.ReservedCapacityFreed.Flag : u'false'}, zonename : u'XenRT-Zone-0', 
status : u'Download Complete', isdynamicallyscalable : False, tags : [], 
isfeatured : False, sshkeyenabled : False, account : u'admin', isextractable : 
True, crossZones : False, sourcetemplateid : 
u'56af8f20-2b4d-11e4-89bd-1e5d0e053e75', name : u'Template-RJQEXI', created : 
u'2014-08-24T16:18:58+', hypervisor : u'XenServer', ispublic : False}, cmd 
: u'org.apache.cloudstack.api.command.admin.template.CreateTemplateCmdByAdmin', 
userid : u'77df13d2-2b4d-11e4-89bd-1e5d0e053e75', jobstatus : 1, jobid : 
u'4df356b8-bc11-4536-a396-2fb81f682aa4', jobresultcode : 0, jobinstanceid : 
u'cba11332-8bd9-40a4-bb90-79a47ee170fd', jobresulttype : u'object', 
jobinstancetype : u'Template', accountid : 
u'77df055e-2b4d-11e4-89bd-1e5d0e053e75'}
test_01_template_usage (integration.component.test_usage.TestTemplateUsage): 
DEBUG: ===Jobid:4df356b8-bc11-4536-a396-2fb81f682aa4 ; StartTime:Sun Aug 24 
16:18:58 2014 ; EndTime:Sun Aug 24 16:23:40 2014 ; TotalTime:-281===
test_01_template_usage (integration.component.test_usage.TestTemplateUsage): 
DEBUG: Response : {jobprocstatus : 0, created : u'2014-08-24T16:18:58+', 
jobresult : {domain : u'ROOT', domainid : 
u'56ab18f0-2b4d-11e4-89bd-1e5d0e053e75', ostypename : u'CentOS 5.3 (64-bit)', 
zoneid : u'eb811e7d-59d4-4c72-a965-80d9e30572d1', displaytext : u'Template', 
ostypeid : u'56b1e2f2-2b4d-11e4-89bd-1e5d0e053e75', passwordenabled : False, id 
: u'cba11332-8bd9-40a4-bb90-79a47ee170fd', size : 21474836480, isready : True, 
format : u'VHD', templatetype : u'USER', details : {platform : 
u'viridian:true;acpi:1;apic:true;pae:true;nx:true', 
Message.ReservedCapacityFreed.Flag : u'false'}, zonename : u'XenRT-Zone-0', 
status : u'Download Complete', isdynamicallyscalable : False, tags : [], 
isfeatured : False, sshkeyenabled : False, account : u'admin', isextractable : 
True, crossZones : False, sourcetemplateid : 
u'56af8f20-2b4d-11e4-89bd-1e5d0e053e75', name : u'Template-RJQEXI', created : 
u'2014-08-24T16:18:58+', hypervisor : u'XenServer', ispublic : False}, cmd 
: u'org.apache.cloudstack.api.command.admin.template.CreateTemplateCmdByAdmin', 
userid : u'77df13d2-2b4d-11e4-89bd-1e5d0e053e75', jobstatus : 1, jobid : 
u'4df356b8-bc11-4536-a396-2fb81f682aa4', jobresultcode : 0, jobinstanceid : 
u'cba11332-8bd9-40a4-bb90-79a47ee170fd', jobresulttype : u'object', 
jobinstancetype : u'Template', accountid : 
u'77df055e-2b4d-11e4-89bd-1e5d0e053e75'}
test_01_template_usage (integration.component.test_usage.TestTemplateUsage): 
DEBUG: Created template with ID: cba11332-8bd9-40a4-bb90-79a47ee170fd
test_01_template_usage (integration.component.test_usage.TestTemplateUsage): 
DEBUG: Payload: {'signature': 'uZXZ8Emles1zD9O5Z8AKkcKON0g=', 'apiKey': 
u'YuaraAK9l9g2KJCAw3APnrD2aNpVmhAesCvWFxlDvGCb0NcARH_sKQxfRM6WF-SCAxikI8awlxCrmw010lUFzg',
 'command': 'deleteTemplate', 'id': u'cba11332-8bd9-40a4-bb90-79a47ee170fd', 
'response': 'json'}
test_01_template_usage (integration.component.test_usage.TestTemplateUsage): 
DEBUG: Sending GET Cmd : deleteTemplate===
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
(1): 10.220.135.69
requests.packages.urllib3.connectionpool: DEBUG: GET

[jira] [Created] (CLOUDSTACK-7441) [Automation] Fix the script test_resource_limits.py - Templates are registered as admin's

Chandan Purushothama created CLOUDSTACK-7441:


 Summary: [Automation] Fix the script test_resource_limits.py - 
Templates are registered as admin's
 Key: CLOUDSTACK-7441
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7441
 Project: CloudStack
  Issue Type: Test
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Priority: Critical
 Fix For: 4.5.0


Two test cases are failing in the test suite: *test_05_templates_per_account*  
*test_05_templates_per_domain*

*Error Message*

Exception not raised   Logs available at 
http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=resource_limits

Stacktrace

  File /usr/lib/python2.7/unittest/case.py, line 332, in run
testMethod()
  File /root/cloudstack/test/integration/component/test_resource_limits.py, 
line 844, in test_05_templates_per_account
domainid=self.account_1.domainid,
  File /usr/lib/python2.7/unittest/case.py, line 116, in __exit__
{0} not raised.format(exc_name))
'Exception not raised\n

Logs available at 
http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=resource_limits
 

*Error Message*

Exception not raised   Logs available at 
http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=resource_limits

Stacktrace

  File /usr/lib/python2.7/unittest/case.py, line 332, in run
testMethod()
  File /root/cloudstack/test/integration/component/test_resource_limits.py, 
line 1355, in test_05_templates_per_domain
domainid=self.account.domainid,
  File /usr/lib/python2.7/unittest/case.py, line 116, in __exit__
{0} not raised.format(exc_name))
'Exception not raised\n

Logs available at 
http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=resource_limits
 


*Bug Information in the Client result logs:*

{code}
==
FAIL: Test Templates limit per account
--
Traceback (most recent call last):
  File /root/cloudstack/test/integration/component/test_resource_limits.py, 
line 844, in test_05_templates_per_account
domainid=self.account_1.domainid,
AssertionError: Exception not raised
  begin captured stdout  -
=== TestName: test_05_templates_per_account | Status : FAILED ===
.
.
.
.
test_05_templates_per_account 
(integration.component.test_resource_limits.TestResourceLimitsAccount): DEBUG: 
Response : {jobprocstatus : 0, created : u'2014-08-24T14:19:11+', jobresult 
: {domain : u'ROOT', domainid : u'56ab18f0-2b4d-11e4-89bd-1e5d0e053e75', 
ostypename : u'CentOS 5.3 (64-bit)', zoneid : 
u'eb811e7d-59d4-4c72-a965-80d9e30572d1', displaytext : u'Cent OS Template', 
ostypeid : u'56b1e2f2-2b4d-11e4-89bd-1e5d0e053e75', passwordenabled : False, id 
: u'c406715b-aa97-4361-a212-32cdfba76b00', size : 21474836480, isready : True, 
format : u'VHD', templatetype : u'USER', details : {platform : 
u'viridian:true;acpi:1;apic:true;pae:true;nx:true', 
Message.ReservedCapacityFreed.Flag : u'false'}, zonename : u'XenRT-Zone-0', 
status : u'Download Complete', isdynamicallyscalable : False, tags : [], 
isfeatured : False, sshkeyenabled : False, account : u'admin', isextractable : 
True, crossZones : False, sourcetemplateid : 
u'56af8f20-2b4d-11e4-89bd-1e5d0e053e75', name : u'Cent OS Template-LS47A4', 
created : u'2014-08-24T14:19:11+', hypervisor : u'XenServer', ispublic : 
False}, cmd : 
u'org.apache.cloudstack.api.command.admin.template.CreateTemplateCmdByAdmin', 
userid : u'77df13d2-2b4d-11e4-89bd-1e5d0e053e75', jobstatus : 1, jobid : 
u'e9295a94-4dfd-4c27-a405-fab4975f0eee', jobresultcode : 0, jobinstanceid : 
u'c406715b-aa97-4361-a212-32cdfba76b00', jobresulttype : u'object', 
jobinstancetype : u'Template', accountid : 
u'77df055e-2b4d-11e4-89bd-1e5d0e053e75'}
test_05_templates_per_account 
(integration.component.test_resource_limits.TestResourceLimitsAccount): DEBUG: 
===Jobid:e9295a94-4dfd-4c27-a405-fab4975f0eee ; StartTime:Sun Aug 24 14:19:12 
2014 ; EndTime:Sun Aug 24 14:20:52 2014 ; TotalTime:-100===
test_05_templates_per_account 
(integration.component.test_resource_limits.TestResourceLimitsAccount): DEBUG: 
Response : {jobprocstatus : 0, created : u'2014-08-24T14:19:11+', jobresult 
: {domain : u'ROOT', domainid : u'56ab18f0-2b4d-11e4-89bd-1e5d0e053e75', 
ostypename : u'CentOS 5.3 (64-bit)', zoneid : 
u'eb811e7d-59d4-4c72-a965-80d9e30572d1', displaytext : u'Cent OS Template', 
ostypeid : u'56b1e2f2-2b4d-11e4-89bd-1e5d0e053e75', passwordenabled : False, id 
: u'c406715b-aa97-4361-a212-32cdfba76b00', size : 21474836480,

[jira] [Created] (CLOUDSTACK-7442) [Automation] Fix the script test_project_resources.py - No permissions updated, please verify the account names

Chandan Purushothama created CLOUDSTACK-7442:


 Summary: [Automation] Fix the script test_project_resources.py - 
No permissions updated, please verify the account names
 Key: CLOUDSTACK-7442
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7442
 Project: CloudStack
  Issue Type: Test
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Priority: Critical
 Fix For: 4.5.0


The following script failed during regression run:

integration.component.test_project_resources.TestTemplates.test_05_use_private_template_in_project
 

*Error Message*

Exception occured: Execute cmd: updatetemplatepermissions failed, due to: 
errorCode: 431, errorText:Unable to grant a launch permission to account 
PrjAcct-Project-TQDWSH-99 in domain id=56ab18f0-2b4d-11e4-89bd-1e5d0e053e75, 
account not found.  No permissions updated, please verify the account names and 
retry.   Logs available at 
http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=project_resources

Stacktrace

  File /usr/lib/python2.7/unittest/case.py, line 332, in run
testMethod()
  File /root/cloudstack/test/integration/component/test_project_resources.py, 
line 768, in test_05_use_private_template_in_project
self.fail(Exception occured: %s % e)
  File /usr/lib/python2.7/unittest/case.py, line 413, in fail
raise self.failureException(msg)
'Exception occured: Execute cmd: updatetemplatepermissions failed, due to: 
errorCode: 431, errorText:Unable to grant a launch permission to account 
PrjAcct-Project-TQDWSH-99 in domain id=56ab18f0-2b4d-11e4-89bd-1e5d0e053e75, 
account not found.  No permissions updated, please verify the account names and 
retry.\n

Logs available at 
http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogsid=804076phase=Paralleltest=project_resources
   



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

[jira] [Commented] (CLOUDSTACK-7404) Failed to start an instance when originating template has been deleted

2014-08-26 Thread Chiradeep Vittal (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14111656#comment-14111656
 ] 

Chiradeep Vittal commented on CLOUDSTACK-7404:
--

You might want to change 
VirtualMachineTemplate template = 
_entityMgr.findById(VirtualMachineTemplate.class, vm.getTemplateId()); 
to
VirtualMachineTemplate template = 
_entityMgr.findByIdIncludingRemoved(VirtualMachineTemplate.class, 
vm.getTemplateId());

in orchestrateStart

 Failed to start an instance when originating template has been deleted
 --

 Key: CLOUDSTACK-7404
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7404
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM, Management Server
Affects Versions: 4.3.0
 Environment: Ubuntu 12.04, KVM, basic networking, Cloudstack 4.3.0
Reporter: Loic Lambiel

 Hi,
 I have an issue were I cannot start an instance that was previously stopped 
 when it's originating template has been deleted.
 Steps to reproduce:
 Deploy an instance
 Stop the instance
 Delete it's originating template
 Wait a few minutes
 Start the instance
 This was working ok on CS 4.0.x
 Management server log:
 2014-08-22 14:01:51,163 DEBUG [cloud.capacity.CapacityManagerImpl] 
 (Job-Executor-87:ctx-17783fe6 ctx-7479eb99) VM state transitted from :Stopped 
 to Starting with event: StartReques
 tedvm's original host id: 48 new host id: null host id before state 
 transition: null
 2014-08-22 14:01:51,164 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-87:ctx-17783fe6 ctx-7479eb99) Successfully transitioned to 
 start state for VM[User|VM-69b4c242-fcd1
 -47ec-9afa-a798c370da5d] reservation id = 7bc0e976-6ba3-4b58-aa59-1eb011c1de4e
 2014-08-22 14:01:51,167 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-87:ctx-17783fe6 ctx-7479eb99) Trying to deploy VM, vm has dcId: 
 1 and podId: 1
 2014-08-22 14:01:51,168 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-87:ctx-17783fe6 ctx-7479eb99) advanceStart: DeploymentPlan is 
 provided, using dcId:1, podId: 1, clu
 sterId: 1, hostId: 48, poolId: null
 2014-08-22 14:01:51,168 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-87:ctx-17783fe6 ctx-7479eb99) Deploy avoids pods: null, 
 clusters: null, hosts: null
 2014-08-22 14:01:51,177 DEBUG [cloud.capacity.CapacityManagerImpl] 
 (Job-Executor-87:ctx-17783fe6 ctx-7479eb99) VM state transitted from 
 :Starting to Stopped with event: OperationFa
 iledvm's original host id: 48 new host id: null host id before state 
 transition: null
 2014-08-22 14:01:51,188 DEBUG [cloud.capacity.CapacityManagerImpl] 
 (Job-Executor-87:ctx-17783fe6 ctx-7479eb99) VM state transitted from :Stopped 
 to Starting with event: StartReques
 tedvm's original host id: 48 new host id: null host id before state 
 transition: null
 2014-08-22 14:01:51,189 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-87:ctx-17783fe6 ctx-7479eb99) Successfully transitioned to 
 start state for VM[User|VM-69b4c242-fcd1
 -47ec-9afa-a798c370da5d] reservation id = 342cb1d2-fc32-4cdf-94c6-049cf16d5509
 2014-08-22 14:01:51,191 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-87:ctx-17783fe6 ctx-7479eb99) Trying to deploy VM, vm has dcId: 
 1 and podId: 1
 2014-08-22 14:01:51,192 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-87:ctx-17783fe6 ctx-7479eb99) Deploy avoids pods: null, 
 clusters: null, hosts: null
 2014-08-22 14:01:51,198 DEBUG [cloud.capacity.CapacityManagerImpl] 
 (Job-Executor-87:ctx-17783fe6 ctx-7479eb99) VM state transitted from 
 :Starting to Stopped with event: OperationFa
 iledvm's original host id: 48 new host id: null host id before state 
 transition: null
 2014-08-22 14:01:51,210 ERROR [cloud.api.ApiAsyncJobDispatcher] 
 (Job-Executor-87:ctx-17783fe6) Unexpected exception while executing 
 org.apache.cloudstack.api.command.user.vm.StartVMCmd
 java.lang.NullPointerException
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:858)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:761)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:601)
 at 
 org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:237)
 at 
 org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:207)
 at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3581)
 at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2043)
 at

[jira] [Created] (CLOUDSTACK-7443) Cannot launch SSVMs when using Swift as Secondary Storage

2014-08-26 Thread Francois Gaudreault (JIRA)

Francois Gaudreault created CLOUDSTACK-7443:
---

 Summary: Cannot launch SSVMs when using Swift as Secondary Storage
 Key: CLOUDSTACK-7443
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7443
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.4.1
Reporter: Francois Gaudreault
Priority: Critical


When using swift as secondary storage, the management server will download the 
system vm, push it to swift. But then when it's time to start the SSVMs, the 
template is not downloaded back to the NFS store, and the SSVM will fail to 
create.

It looks like a path issue. If I strip one path level, say from template/1/1 to 
template/1, the template will be downloaded properly, and the SSVMs will start.



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

[jira] [Updated] (CLOUDSTACK-7443) Cannot launch SSVMs when using Swift as Secondary Storage

2014-08-26 Thread Francois Gaudreault (JIRA)

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

Francois Gaudreault updated CLOUDSTACK-7443:

Description:
When using swift as secondary storage, the management server will download the
system vm, push it to swift. But then when it's time to start the SSVMs, the
template is not downloaded back to the NFS store, and the SSVM will fail to
create.

It looks like a path issue. If I strip one path level, say from template/1/1 to
template/1, the template will be downloaded properly. However, SSVMs have a
rough time to start.

was:
When using swift as secondary storage, the management server will download the
system vm, push it to swift. But then when it's time to start the SSVMs, the
template is not downloaded back to the NFS store, and the SSVM will fail to
create.

It looks like a path issue. If I strip one path level, say from template/1/1 to
template/1, the template will be downloaded properly, and the SSVMs will start.

Cannot launch SSVMs when using Swift as Secondary Storage
-

Key: CLOUDSTACK-7443
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7443
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Affects Versions: 4.4.1
Reporter: Francois Gaudreault
Priority: Critical

When using swift as secondary storage, the management server will download
the system vm, push it to swift. But then when it's time to start the SSVMs,
the template is not downloaded back to the NFS store, and the SSVM will fail
to create.
It looks like a path issue. If I strip one path level, say from template/1/1
to template/1, the template will be downloaded properly. However, SSVMs have
a rough time to start.

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

[jira] [Assigned] (CLOUDSTACK-7443) Cannot launch SSVMs when using Swift as Secondary Storage

2014-08-26 Thread Sudha Ponnaganti (JIRA)


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

Sudha Ponnaganti reassigned CLOUDSTACK-7443:


Assignee: Sudha Ponnaganti

 Cannot launch SSVMs when using Swift as Secondary Storage
 -

 Key: CLOUDSTACK-7443
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7443
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.4.1
Reporter: Francois Gaudreault
Assignee: Sudha Ponnaganti
Priority: Critical

 When using swift as secondary storage, the management server will download 
 the system vm, push it to swift. But then when it's time to start the SSVMs, 
 the template is not downloaded back to the NFS store, and the SSVM will fail 
 to create.
 It looks like a path issue. If I strip one path level, say from template/1/1 
 to template/1, the template will be downloaded properly. However, SSVMs have 
 a rough time to start.



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

[jira] [Created] (CLOUDSTACK-7444) [Automation] Fix the script test_snapshots_improvement.py - Templates are registered as admin's