[jira] [Commented] (CLOUDSTACK-2729) [Automation] Libvirt failed find primary storage and VM deployment failed
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14170567#comment-14170567
]
Wei Zhou commented on CLOUDSTACK-2729:
--
For those who are using CentOS/RHEL 6 as host, it is better to install the
following libvirt rpms.
https://rhn.redhat.com/errata/RHBA-2014-1374.html
> [Automation] Libvirt failed find primary storage and VM deployment failed
>
>
> Key: CLOUDSTACK-2729
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2729
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller
>Affects Versions: 4.2.0
> Environment: Master branch build
> Automation environment - KVM
>Reporter: Rayees Namathponnan
>Assignee: edison su
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: 2729.rar, 2729_08_13_13_Agents.rar,
> 2729_08_13_13_Managment.rar, Agent_2729.rar, CLOUDSTACK-2729.rar,
> CLOUDSTACK-2729_8_18_Agent.rar, CLOUDSTACK-2729_8_18_MS.rar, agent.log,
> cloud.dmp, management-server.rar
>
>
> Failed to deploy VM in automation, environment created with , 2 hosts and 2
> primary storages in a cluster
> 1) /export/home/rayees/SC_QA_AUTO4/primary2
> 2) /export/home/rayees/SC_QA_AUTO4/primary
> Libvirt failed to find the primary storage
> /export/home/rayees/SC_QA_AUTO4/primary and VM deployment failed
> MS log
> 2013-05-28 21:11:44,540 DEBUG [agent.transport.Request] (consoleproxy-1:null)
> Seq 4-936706756: Sending { Cmd , MgmtId: 29066118877352, via: 4, Ver: v1,
> Flags: 100111,
> [{"StartCommand":{"vm":{"id":29,"name":"v-29-QA","type":"ConsoleProxy","cpus":1,"minSpeed":500,"maxSpeed":500,"minRam":1073741824,"maxRam":1073741824,"arch":"x86_64","os":"Debian
> GNU/Linux 5.0 (32-bit)","bootArgs":" template=domP type=consoleproxy
> host=10.223.49.195 port=8250 name=v-29-QA premium=true zone=1 pod=1
> guid=Proxy.29 proxy_vm=29 disable_rp_filter=true eth2ip=10.223.122.73
> eth2mask=255.255.255.192 gateway=10.223.122.65 eth0ip=169.254.0.154
> eth0mask=255.255.0.0 eth1ip=10.223.50.96 eth1mask=255.255.255.192
> mgmtcidr=10.223.49.192/26 localgw=10.223.50.65 internaldns1=10.223.110.254
> dns1=72.52.126.11","rebootOnCrash":false,"enableHA":false,"limitCpuUse":false,"vncPassword":"d099568827911cef","params":{},"uuid":"5a146833-6a8c-44e5-83c0-50f34accf513","disks":[{"id":32,"name":"ROOT-29","mountPoint":"/export/home/rayees/SC_QA_AUTO4/primary","path":"f6f8d865-e9c0-4188-8a33-6c6383ca5075","size":276406784,"type":"ROOT","storagePoolType":"NetworkFilesystem","storagePoolUuid":"fff90cb5-06dd-33b3-8815-d78c08ca01d9","deviceId":0}],"nics":[{"deviceId":2,"networkRateMbps":-1,"defaultNic":true,"uuid":"21175978-96bd-4160-8228-8ad15aa40c66","ip":"10.223.122.73","netmask":"255.255.255.192","gateway":"10.223.122.65","mac":"06:2e:5a:00:00:42","dns1":"72.52.126.11","broadcastType":"Vlan","type":"Public","broadcastUri":"vlan://1221","isolationUri":"vlan://1221","isSecurityGroupEnabled":false},{"deviceId":0,"networkRateMbps":-1,"defaultNic":false,"uuid":"e0651452-a76e-4564-96b2-3d5d51e9bcd6","ip":"169.254.0.154","netmask":"255.255.0.0","gateway":"169.254.0.1","mac":"0e:00:a9:fe:00:9a","broadcastType":"LinkLocal","type":"Control","isSecurityGroupEnabled":false},{"deviceId":1,"networkRateMbps":-1,"defaultNic":false,"uuid":"0765c229-468e-4dfd-8382-24ac49791a8d","ip":"10.223.50.96","netmask":"255.255.255.192","gateway":"10.223.50.65","mac":"06:a8:e8:00:00:1d","broadcastType":"Native","type":"Management","isSecurityGroupEnabled":false}]},"hostIp":"10.223.50.66","wait":0}},{"check.CheckSshCommand":{"ip":"169.254.0.154","port":3922,"interval":6,"retries":100,"name":"v-29-QA","wait":0}}]
> }
> 2013-05-28 21:11:44,552 DEBUG [agent.transport.Request]
> (AgentManager-Handler-1:null) Seq 4-936706756: Processing: { Ans: , MgmtId:
> 29066118877352, via: 4, Ver: v1, Flags: 110,
> [{"Answer":{"result":false,"details":"com.cloud.utils.exception.CloudRuntimeException:
> org.libvirt.LibvirtException: Storage pool not found: no pool with matching
> uuid\n\tat
> com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.getStoragePool(LibvirtStorageAdaptor.java:380)\n\tat
>
> com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.getStoragePool(KVMStoragePoolManager.java:72)\n\tat
>
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVbd(LibvirtComputingResource.java:3399)\n\tat
>
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3293)\n\tat
>
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1187)\n\tat
> com.cloud.agent.Agent.processRequest(Agent.java:525)\n\tat
[jira] [Reopened] (CLOUDSTACK-7671) [RHEL7] management server failed to start once machine is rebooted
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T reopened CLOUDSTACK-7671: - Assignee: Rayees Namathponnan (was: Damodar Reddy T) > [RHEL7] management server failed to start once machine is rebooted > -- > > Key: CLOUDSTACK-7671 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7671 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Damodar Reddy T >Assignee: Rayees Namathponnan > > Repro stesp: > Create a rhel 7 host > Install MS > Start MS > Once MS is up and running . Reboot MS . Notice Cloudstack-management service > status > Bug: > Notice MS fails to start even after calling service cloudstack-management > restart it failed to start > systemctl status cloudstack-management.service > cloudstack-management.service - Citrix Cloud Plaltform >Loaded: loaded (/usr/lib/systemd/system/cloudstack-management.service; > enabled) >Active: failed (Result: exit-code) since Tue 2014-09-23 12:10:09 IST; 1min > 28s ago > Process: 4618 ExecStart=/usr/sbin/cloudstack-management start (code=exited, > status=1/FAILURE) > Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: Starting Citrix Cloud Plaltform... > Sep 23 12:10:09 Rack1Pod1Host27 cloudstack-management[4618]: > /usr/sbin/tomcat: line 50: /var/run/cloudstack-management.pid: Permission > denied > Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: cloudstack-management.service: > control process exited, code=exited status=1 > Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: Failed to start Citrix Cloud > Plaltform. > Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: Unit > cloudstack-management.service entered failed state. > [root@Rack1Pod1Host27 run]# > service cloudstack-management status > Redirecting to /bin/systemctl status cloudstack-management.service > cloudstack-management.service - Citrix Cloud Plaltform >Loaded: loaded (/usr/lib/systemd/system/cloudstack-management.service; > enabled) >Active: failed (Result: exit-code) since Tue 2014-09-23 12:14:05 IST; 8s > ago > Process: 4691 ExecStart=/usr/sbin/cloudstack-management start (code=exited, > status=1/FAILURE) > Sep 23 12:14:05 Rack1Pod1Host27 cloudstack-management[4691]: > /usr/sbin/tomcat: line 50: /var/run/cloudstack-management.pid: Permission > denied > Sep 23 12:14:05 Rack1Pod1Host27 systemd[1]: cloudstack-management.service: > control process exited, code=exited status=1 > Sep 23 12:14:05 Rack1Pod1Host27 systemd[1]: Failed to start Citrix Cloud > Plaltform. > Sep 23 12:14:05 Rack1Pod1Host27 systemd[1]: Unit > cloudstack-management.service entered failed state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7560) Usage Event is not generated when VM state is transited from RUNNING to STOPPED directly
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damodar Reddy T resolved CLOUDSTACK-7560.
-
Resolution: Fixed
Fix Version/s: (was: Future)
4.5.0
Got fixed as part of https://issues.apache.org/jira/browse/CLOUDSTACK-7648
> Usage Event is not generated when VM state is transited from RUNNING to
> STOPPED directly
>
>
> Key: CLOUDSTACK-7560
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7560
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Usage
>Affects Versions: 4.5.0
>Reporter: Damodar Reddy T
>Assignee: Damodar Reddy T
> Fix For: 4.5.0
>
>
> When Maagement server is not able to detect VM state, after a specific time
> it will try to change the RUNNING state to STOPPED state directly without
> STOPPING state in between. Which is causing the event not to be generated and
> now if you DESTROY the VM still it will generate the usage records for a
> period of 24 hrs every day.
> Logs are attached below...
> 2014-05-15 16:13:25,197 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
> (DirectAgent-117:ctx-775a3f34) Run missing VM report. current time:
> 1400163205197
> 2014-05-15 16:13:25,197 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
> (DirectAgent-117:ctx-775a3f34) Detected missing VM. host: 1, vm id: 106,
> power state: PowerReportMissing, last state update: 1400162537000
> 2014-05-15 16:13:25,197 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
> (DirectAgent-117:ctx-775a3f34) vm id: 106 - time since last state
> update(668197ms) has passed graceful period
> 2014-05-15 16:13:25,202 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
> (DirectAgent-117:ctx-775a3f34) VM state report is updated. host: 1, vm id:
> 106, power state: PowerReportMissing
> 2014-05-15 16:13:25,207 INFO [c.c.v.VirtualMachineManagerImpl]
> (DirectAgent-117:ctx-775a3f34) VM i-5-106-VM is at Running and we received a
> power-off report while there is no pending jobs on it
> 2014-05-15 16:13:25,210 DEBUG [c.c.a.t.Request]
> (DirectAgent-117:ctx-775a3f34) Seq 1-1971781673: Sending { Cmd , MgmtId:
> 20750978301280, via: 1(XSMASTER-5), Ver: v1, Flags: 100111,
> [{"com.cloud.agent.api.StopCommand":{"isProxy":false,"executeInSequence":true,"checkBeforeCleanup":true,"vmName":"i-5-106-VM","wait":0}}]
> }
> 2014-05-15 16:13:25,210 DEBUG [c.c.a.t.Request]
> (DirectAgent-117:ctx-775a3f34) Seq 1-1971781673: Executing: { Cmd , MgmtId:
> 20750978301280, via: 1(XSMASTER-5), Ver: v1, Flags: 100111,
> [{"com.cloud.agent.api.StopCommand":{"isProxy":false,"executeInSequence":true,"checkBeforeCleanup":true,"vmName":"i-5-106-VM","wait":0}}]
> }
> 2014-05-15 16:13:25,210 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-18:ctx-7180bb9c) Seq 1-1971781673: Executing request
> 2014-05-15 16:13:25,249 DEBUG [c.c.h.x.r.CitrixResourceBase]
> (DirectAgent-18:ctx-7180bb9c) 9. The VM i-5-106-VM is in Stopping state
> 2014-05-15 16:13:25,293 INFO [c.c.h.x.r.XenServer56Resource]
> (DirectAgent-18:ctx-7180bb9c) Catch com.xensource.xenapi.Types$VifInUse:
> failed to destory VLAN eth0 on host c4080dac-f034-452f-9203-8e69d5512315 due
> to Network has active VIFs
> 2014-05-15 16:13:25,294 DEBUG [c.c.h.x.r.CitrixResourceBase]
> (DirectAgent-18:ctx-7180bb9c) 10. The VM i-5-106-VM is in Stopped state
> 2014-05-15 16:13:25,294 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-18:ctx-7180bb9c) Seq 1-1971781673: Response Received:
> 2014-05-15 16:13:25,294 DEBUG [c.c.a.t.Request] (DirectAgent-18:ctx-7180bb9c)
> Seq 1-1971781673: Processing: { Ans: , MgmtId: 20750978301280, via: 1, Ver:
> v1, Flags: 110,
> [{"com.cloud.agent.api.StopAnswer":{"platform":"viridian:true;acpi:1;apic:true;pae:true;nx:true","result":true,"details":"Stop
> VM i-5-106-VM Succeed","wait":0}}] }
> 2014-05-15 16:13:25,294 DEBUG [c.c.a.t.Request]
> (DirectAgent-117:ctx-775a3f34) Seq 1-1971781673: Received: { Ans: , MgmtId:
> 20750978301280, via: 1, Ver: v1, Flags: 110, { StopAnswer } }
> 2014-05-15 16:13:25,301 DEBUG [c.c.a.m.AgentAttache]
> (DirectAgent-18:ctx-7180bb9c) Seq 1-1971781673: No more commands found
> 2014-05-15 16:13:25,365 DEBUG [c.c.c.CapacityManagerImpl]
> (DirectAgent-117:ctx-775a3f34) VM state transitted from :Running to Stopped
> with event: FollowAgentPowerOffReportvm's original host id: 1 new host id:
> null host id before state transition: 1
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (CLOUDSTACK-7560) Usage Event is not generated when VM state is transited from RUNNING to STOPPED directly
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damodar Reddy T reassigned CLOUDSTACK-7560:
---
Assignee: Damodar Reddy T
> Usage Event is not generated when VM state is transited from RUNNING to
> STOPPED directly
>
>
> Key: CLOUDSTACK-7560
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7560
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Usage
>Affects Versions: 4.5.0
>Reporter: Damodar Reddy T
>Assignee: Damodar Reddy T
> Fix For: Future
>
>
> When Maagement server is not able to detect VM state, after a specific time
> it will try to change the RUNNING state to STOPPED state directly without
> STOPPING state in between. Which is causing the event not to be generated and
> now if you DESTROY the VM still it will generate the usage records for a
> period of 24 hrs every day.
> Logs are attached below...
> 2014-05-15 16:13:25,197 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
> (DirectAgent-117:ctx-775a3f34) Run missing VM report. current time:
> 1400163205197
> 2014-05-15 16:13:25,197 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
> (DirectAgent-117:ctx-775a3f34) Detected missing VM. host: 1, vm id: 106,
> power state: PowerReportMissing, last state update: 1400162537000
> 2014-05-15 16:13:25,197 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
> (DirectAgent-117:ctx-775a3f34) vm id: 106 - time since last state
> update(668197ms) has passed graceful period
> 2014-05-15 16:13:25,202 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
> (DirectAgent-117:ctx-775a3f34) VM state report is updated. host: 1, vm id:
> 106, power state: PowerReportMissing
> 2014-05-15 16:13:25,207 INFO [c.c.v.VirtualMachineManagerImpl]
> (DirectAgent-117:ctx-775a3f34) VM i-5-106-VM is at Running and we received a
> power-off report while there is no pending jobs on it
> 2014-05-15 16:13:25,210 DEBUG [c.c.a.t.Request]
> (DirectAgent-117:ctx-775a3f34) Seq 1-1971781673: Sending { Cmd , MgmtId:
> 20750978301280, via: 1(XSMASTER-5), Ver: v1, Flags: 100111,
> [{"com.cloud.agent.api.StopCommand":{"isProxy":false,"executeInSequence":true,"checkBeforeCleanup":true,"vmName":"i-5-106-VM","wait":0}}]
> }
> 2014-05-15 16:13:25,210 DEBUG [c.c.a.t.Request]
> (DirectAgent-117:ctx-775a3f34) Seq 1-1971781673: Executing: { Cmd , MgmtId:
> 20750978301280, via: 1(XSMASTER-5), Ver: v1, Flags: 100111,
> [{"com.cloud.agent.api.StopCommand":{"isProxy":false,"executeInSequence":true,"checkBeforeCleanup":true,"vmName":"i-5-106-VM","wait":0}}]
> }
> 2014-05-15 16:13:25,210 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-18:ctx-7180bb9c) Seq 1-1971781673: Executing request
> 2014-05-15 16:13:25,249 DEBUG [c.c.h.x.r.CitrixResourceBase]
> (DirectAgent-18:ctx-7180bb9c) 9. The VM i-5-106-VM is in Stopping state
> 2014-05-15 16:13:25,293 INFO [c.c.h.x.r.XenServer56Resource]
> (DirectAgent-18:ctx-7180bb9c) Catch com.xensource.xenapi.Types$VifInUse:
> failed to destory VLAN eth0 on host c4080dac-f034-452f-9203-8e69d5512315 due
> to Network has active VIFs
> 2014-05-15 16:13:25,294 DEBUG [c.c.h.x.r.CitrixResourceBase]
> (DirectAgent-18:ctx-7180bb9c) 10. The VM i-5-106-VM is in Stopped state
> 2014-05-15 16:13:25,294 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-18:ctx-7180bb9c) Seq 1-1971781673: Response Received:
> 2014-05-15 16:13:25,294 DEBUG [c.c.a.t.Request] (DirectAgent-18:ctx-7180bb9c)
> Seq 1-1971781673: Processing: { Ans: , MgmtId: 20750978301280, via: 1, Ver:
> v1, Flags: 110,
> [{"com.cloud.agent.api.StopAnswer":{"platform":"viridian:true;acpi:1;apic:true;pae:true;nx:true","result":true,"details":"Stop
> VM i-5-106-VM Succeed","wait":0}}] }
> 2014-05-15 16:13:25,294 DEBUG [c.c.a.t.Request]
> (DirectAgent-117:ctx-775a3f34) Seq 1-1971781673: Received: { Ans: , MgmtId:
> 20750978301280, via: 1, Ver: v1, Flags: 110, { StopAnswer } }
> 2014-05-15 16:13:25,301 DEBUG [c.c.a.m.AgentAttache]
> (DirectAgent-18:ctx-7180bb9c) Seq 1-1971781673: No more commands found
> 2014-05-15 16:13:25,365 DEBUG [c.c.c.CapacityManagerImpl]
> (DirectAgent-117:ctx-775a3f34) VM state transitted from :Running to Stopped
> with event: FollowAgentPowerOffReportvm's original host id: 1 new host id:
> null host id before state transition: 1
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7648) There are new VM State Machine changes introduced which were missed to capture the usage events
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T resolved CLOUDSTACK-7648. - Resolution: Fixed Fix Version/s: (was: Future) 4.5.0 > There are new VM State Machine changes introduced which were missed to > capture the usage events > --- > > Key: CLOUDSTACK-7648 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7648 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.5.0 >Reporter: Damodar Reddy T >Assignee: Damodar Reddy T > Fix For: 4.5.0 > > > There are new VM State Machine changes introduced while adding VM Sync > changes and these were missed to capture the usage events. > This is causing to get wrong usage statistics for a VM who's state is changed > by VM sync -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7700) Volume Snapshot Async Job returns Success for a failed operation
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Min Chen resolved CLOUDSTACK-7700.
--
Resolution: Fixed
> Volume Snapshot Async Job returns Success for a failed operation
>
>
> Key: CLOUDSTACK-7700
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7700
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller
>Affects Versions: 4.3.0
>Reporter: Min Chen
>Assignee: Min Chen
>Priority: Critical
> Fix For: 4.5.0
>
>
> Setup :
> Single zone , two clusters , one host in each cluster , have cluster wide
> storages and one zone wide primary storage
> Steps:
> 1. Install and configure Adv zone with Vmware 5.5 and CCP 4.3.0.1 IDCF branch
> setup
> 2. Deploy VM with DATA disk using Zonewide storage tagged offering and ensure
> that root and data disk of this VM are placed in ZWPS
> 3. Stop the VM and Try to create Volume snapshots till it gets failed.
> Observation:
> 1. It failed to create snapshot due to some temporary network issues .
> But It is returning success for a failed operation.
> 2014-10-13 17:39:52,365 DEBUG [c.c.v.VmWorkJobHandlerProxy]
> (Work-Job-Executor-12:ctx-9c1911cf job-36/job-37 ctx-14ac0075) Done executing
> VM work job: com.cloud.storage.VmWorkTakeVolumeSnapshot
> {"volumeId":4,"policyId":0,"snapshotId":7,"quiesceVm":false,"userId":2,"accountId":3,"vmId":3,"handlerName":"VolumeApiServiceImpl"}
> 2014-10-13 17:39:52,365 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Work-Job-Executor-12:ctx-9c1911cf job-36/job-37 ctx-14ac0075) Complete async
> job-37, jobStatus: SUCCEEDED, resultCode: 0, result:
> rO0ABXNyAA5qYXZhLmxhbmcuTG9uZzuL5JDMjyPfAgABSgAFdmFsdWV4cgAQamF2YS5sYW5nLk51bWJlcoaslR0LlOCLAgAAeHAABw
> 2014-10-13 17:39:52,375 DEBUG [c.c.v.VmWorkJobDispatcher]
> (Work-Job-Executor-12:ctx-9c1911cf job-36/job-37) Done with run of VM work
> job: com.cloud.storage.VmWorkTakeVolumeSnapshot for VM 3, job origin: 36
> 2014-10-13 17:39:52,375 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Work-Job-Executor-12:ctx-9c1911cf job-36/job-37) Done executing
> com.cloud.storage.VmWorkTakeVolumeSnapshot for job-37
> 2014-10-13 17:39:52,392 DEBUG [o.a.c.f.j.i.SyncQueueManagerImpl]
> (Work-Job-Executor-12:ctx-9c1911cf job-36/job-37) Sync queue (3) is currently
> empty
> 2014-10-13 17:39:52,393 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (Work-Job-Executor-12:ctx-9c1911cf job-36/job-37) Remove job-37 from job
> monitoring
> 2014-10-13 17:39:52,395 DEBUG [c.c.a.ApiResponseHelper]
> (API-Job-Executor-21:ctx-d9e77f3d job-36 ctx-16075f77) Unable to find info
> for image store snapshot with uuid 91fec32b-77f1-42af-909d-acca69772581
> 2014-10-13 17:39:52,396 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-21:ctx-d9e77f3d job-36 ctx-16075f77) Complete async job-36,
> jobStatus: SUCCEEDED, resultCode: 0, result:
> org.apache.cloudstack.api.response.SnapshotResponse/snapshot/
> {"id":"91fec32b-77f1-42af-909d-acca69772581","account":"cdcuser1","domainid":"0dc68c16-49d3-47ef-9ae2-40e043d3fe81","domain":"cdc","snapshottype":"MANUAL","volumeid":"5097706f-97d6-4133-b010-3c803bca66cf","volumename":"DATA-3","volumetype":"DATADISK","created":"2014-10-13T17:39:43+0530","name":"cdcuserinst1_DATA-3_20141013120943","intervaltype":"MANUAL","state":"Error","tags":[],"revertable":false}
> 2014-10-13 17:39:52,417 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-21:ctx-d9e77f3d job-36) Done executing
> org.apache.cloudstack.api.command.user.snapshot.CreateSnapshotCmd for job-36
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7700) Volume Snapshot Async Job returns Success for a failed operation
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14170259#comment-14170259
]
ASF subversion and git services commented on CLOUDSTACK-7700:
-
Commit 0db0e5e3cc91106002892a582e9843284eee19b4 in cloudstack's branch
refs/heads/4.5 from [~minchen07]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=0db0e5e ]
CLOUDSTACK-7700: Volume Snapshot Async Job returns Success for a failed
operation.
> Volume Snapshot Async Job returns Success for a failed operation
>
>
> Key: CLOUDSTACK-7700
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7700
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller
>Affects Versions: 4.3.0
>Reporter: Min Chen
>Assignee: Min Chen
>Priority: Critical
> Fix For: 4.5.0
>
>
> Setup :
> Single zone , two clusters , one host in each cluster , have cluster wide
> storages and one zone wide primary storage
> Steps:
> 1. Install and configure Adv zone with Vmware 5.5 and CCP 4.3.0.1 IDCF branch
> setup
> 2. Deploy VM with DATA disk using Zonewide storage tagged offering and ensure
> that root and data disk of this VM are placed in ZWPS
> 3. Stop the VM and Try to create Volume snapshots till it gets failed.
> Observation:
> 1. It failed to create snapshot due to some temporary network issues .
> But It is returning success for a failed operation.
> 2014-10-13 17:39:52,365 DEBUG [c.c.v.VmWorkJobHandlerProxy]
> (Work-Job-Executor-12:ctx-9c1911cf job-36/job-37 ctx-14ac0075) Done executing
> VM work job: com.cloud.storage.VmWorkTakeVolumeSnapshot
> {"volumeId":4,"policyId":0,"snapshotId":7,"quiesceVm":false,"userId":2,"accountId":3,"vmId":3,"handlerName":"VolumeApiServiceImpl"}
> 2014-10-13 17:39:52,365 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Work-Job-Executor-12:ctx-9c1911cf job-36/job-37 ctx-14ac0075) Complete async
> job-37, jobStatus: SUCCEEDED, resultCode: 0, result:
> rO0ABXNyAA5qYXZhLmxhbmcuTG9uZzuL5JDMjyPfAgABSgAFdmFsdWV4cgAQamF2YS5sYW5nLk51bWJlcoaslR0LlOCLAgAAeHAABw
> 2014-10-13 17:39:52,375 DEBUG [c.c.v.VmWorkJobDispatcher]
> (Work-Job-Executor-12:ctx-9c1911cf job-36/job-37) Done with run of VM work
> job: com.cloud.storage.VmWorkTakeVolumeSnapshot for VM 3, job origin: 36
> 2014-10-13 17:39:52,375 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Work-Job-Executor-12:ctx-9c1911cf job-36/job-37) Done executing
> com.cloud.storage.VmWorkTakeVolumeSnapshot for job-37
> 2014-10-13 17:39:52,392 DEBUG [o.a.c.f.j.i.SyncQueueManagerImpl]
> (Work-Job-Executor-12:ctx-9c1911cf job-36/job-37) Sync queue (3) is currently
> empty
> 2014-10-13 17:39:52,393 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (Work-Job-Executor-12:ctx-9c1911cf job-36/job-37) Remove job-37 from job
> monitoring
> 2014-10-13 17:39:52,395 DEBUG [c.c.a.ApiResponseHelper]
> (API-Job-Executor-21:ctx-d9e77f3d job-36 ctx-16075f77) Unable to find info
> for image store snapshot with uuid 91fec32b-77f1-42af-909d-acca69772581
> 2014-10-13 17:39:52,396 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-21:ctx-d9e77f3d job-36 ctx-16075f77) Complete async job-36,
> jobStatus: SUCCEEDED, resultCode: 0, result:
> org.apache.cloudstack.api.response.SnapshotResponse/snapshot/
> {"id":"91fec32b-77f1-42af-909d-acca69772581","account":"cdcuser1","domainid":"0dc68c16-49d3-47ef-9ae2-40e043d3fe81","domain":"cdc","snapshottype":"MANUAL","volumeid":"5097706f-97d6-4133-b010-3c803bca66cf","volumename":"DATA-3","volumetype":"DATADISK","created":"2014-10-13T17:39:43+0530","name":"cdcuserinst1_DATA-3_20141013120943","intervaltype":"MANUAL","state":"Error","tags":[],"revertable":false}
> 2014-10-13 17:39:52,417 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-21:ctx-d9e77f3d job-36) Done executing
> org.apache.cloudstack.api.command.user.snapshot.CreateSnapshotCmd for job-36
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7700) Volume Snapshot Async Job returns Success for a failed operation
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14170039#comment-14170039
]
ASF subversion and git services commented on CLOUDSTACK-7700:
-
Commit 1e20600ecaa3487f9d2eac53505c2e9e0f0f9e88 in cloudstack's branch
refs/heads/master from [~minchen07]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=1e20600 ]
CLOUDSTACK-7700: Volume Snapshot Async Job returns Success for a failed
operation.
> Volume Snapshot Async Job returns Success for a failed operation
>
>
> Key: CLOUDSTACK-7700
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7700
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller
>Affects Versions: 4.3.0
>Reporter: Min Chen
>Assignee: Min Chen
>Priority: Critical
> Fix For: 4.5.0
>
>
> Setup :
> Single zone , two clusters , one host in each cluster , have cluster wide
> storages and one zone wide primary storage
> Steps:
> 1. Install and configure Adv zone with Vmware 5.5 and CCP 4.3.0.1 IDCF branch
> setup
> 2. Deploy VM with DATA disk using Zonewide storage tagged offering and ensure
> that root and data disk of this VM are placed in ZWPS
> 3. Stop the VM and Try to create Volume snapshots till it gets failed.
> Observation:
> 1. It failed to create snapshot due to some temporary network issues .
> But It is returning success for a failed operation.
> 2014-10-13 17:39:52,365 DEBUG [c.c.v.VmWorkJobHandlerProxy]
> (Work-Job-Executor-12:ctx-9c1911cf job-36/job-37 ctx-14ac0075) Done executing
> VM work job: com.cloud.storage.VmWorkTakeVolumeSnapshot
> {"volumeId":4,"policyId":0,"snapshotId":7,"quiesceVm":false,"userId":2,"accountId":3,"vmId":3,"handlerName":"VolumeApiServiceImpl"}
> 2014-10-13 17:39:52,365 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Work-Job-Executor-12:ctx-9c1911cf job-36/job-37 ctx-14ac0075) Complete async
> job-37, jobStatus: SUCCEEDED, resultCode: 0, result:
> rO0ABXNyAA5qYXZhLmxhbmcuTG9uZzuL5JDMjyPfAgABSgAFdmFsdWV4cgAQamF2YS5sYW5nLk51bWJlcoaslR0LlOCLAgAAeHAABw
> 2014-10-13 17:39:52,375 DEBUG [c.c.v.VmWorkJobDispatcher]
> (Work-Job-Executor-12:ctx-9c1911cf job-36/job-37) Done with run of VM work
> job: com.cloud.storage.VmWorkTakeVolumeSnapshot for VM 3, job origin: 36
> 2014-10-13 17:39:52,375 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Work-Job-Executor-12:ctx-9c1911cf job-36/job-37) Done executing
> com.cloud.storage.VmWorkTakeVolumeSnapshot for job-37
> 2014-10-13 17:39:52,392 DEBUG [o.a.c.f.j.i.SyncQueueManagerImpl]
> (Work-Job-Executor-12:ctx-9c1911cf job-36/job-37) Sync queue (3) is currently
> empty
> 2014-10-13 17:39:52,393 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (Work-Job-Executor-12:ctx-9c1911cf job-36/job-37) Remove job-37 from job
> monitoring
> 2014-10-13 17:39:52,395 DEBUG [c.c.a.ApiResponseHelper]
> (API-Job-Executor-21:ctx-d9e77f3d job-36 ctx-16075f77) Unable to find info
> for image store snapshot with uuid 91fec32b-77f1-42af-909d-acca69772581
> 2014-10-13 17:39:52,396 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-21:ctx-d9e77f3d job-36 ctx-16075f77) Complete async job-36,
> jobStatus: SUCCEEDED, resultCode: 0, result:
> org.apache.cloudstack.api.response.SnapshotResponse/snapshot/
> {"id":"91fec32b-77f1-42af-909d-acca69772581","account":"cdcuser1","domainid":"0dc68c16-49d3-47ef-9ae2-40e043d3fe81","domain":"cdc","snapshottype":"MANUAL","volumeid":"5097706f-97d6-4133-b010-3c803bca66cf","volumename":"DATA-3","volumetype":"DATADISK","created":"2014-10-13T17:39:43+0530","name":"cdcuserinst1_DATA-3_20141013120943","intervaltype":"MANUAL","state":"Error","tags":[],"revertable":false}
> 2014-10-13 17:39:52,417 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-21:ctx-d9e77f3d job-36) Done executing
> org.apache.cloudstack.api.command.user.snapshot.CreateSnapshotCmd for job-36
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7700) Volume Snapshot Async Job returns Success for a failed operation
Min Chen created CLOUDSTACK-7700:
Summary: Volume Snapshot Async Job returns Success for a failed
operation
Key: CLOUDSTACK-7700
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7700
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Storage Controller
Affects Versions: 4.3.0
Reporter: Min Chen
Assignee: Min Chen
Priority: Critical
Fix For: 4.5.0
Setup :
Single zone , two clusters , one host in each cluster , have cluster wide
storages and one zone wide primary storage
Steps:
1. Install and configure Adv zone with Vmware 5.5 and CCP 4.3.0.1 IDCF branch
setup
2. Deploy VM with DATA disk using Zonewide storage tagged offering and ensure
that root and data disk of this VM are placed in ZWPS
3. Stop the VM and Try to create Volume snapshots till it gets failed.
Observation:
1. It failed to create snapshot due to some temporary network issues .
But It is returning success for a failed operation.
2014-10-13 17:39:52,365 DEBUG [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-12:ctx-9c1911cf job-36/job-37 ctx-14ac0075) Done executing
VM work job: com.cloud.storage.VmWorkTakeVolumeSnapshot
{"volumeId":4,"policyId":0,"snapshotId":7,"quiesceVm":false,"userId":2,"accountId":3,"vmId":3,"handlerName":"VolumeApiServiceImpl"}
2014-10-13 17:39:52,365 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Work-Job-Executor-12:ctx-9c1911cf job-36/job-37 ctx-14ac0075) Complete async
job-37, jobStatus: SUCCEEDED, resultCode: 0, result:
rO0ABXNyAA5qYXZhLmxhbmcuTG9uZzuL5JDMjyPfAgABSgAFdmFsdWV4cgAQamF2YS5sYW5nLk51bWJlcoaslR0LlOCLAgAAeHAABw
2014-10-13 17:39:52,375 DEBUG [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-12:ctx-9c1911cf job-36/job-37) Done with run of VM work job:
com.cloud.storage.VmWorkTakeVolumeSnapshot for VM 3, job origin: 36
2014-10-13 17:39:52,375 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Work-Job-Executor-12:ctx-9c1911cf job-36/job-37) Done executing
com.cloud.storage.VmWorkTakeVolumeSnapshot for job-37
2014-10-13 17:39:52,392 DEBUG [o.a.c.f.j.i.SyncQueueManagerImpl]
(Work-Job-Executor-12:ctx-9c1911cf job-36/job-37) Sync queue (3) is currently
empty
2014-10-13 17:39:52,393 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(Work-Job-Executor-12:ctx-9c1911cf job-36/job-37) Remove job-37 from job
monitoring
2014-10-13 17:39:52,395 DEBUG [c.c.a.ApiResponseHelper]
(API-Job-Executor-21:ctx-d9e77f3d job-36 ctx-16075f77) Unable to find info for
image store snapshot with uuid 91fec32b-77f1-42af-909d-acca69772581
2014-10-13 17:39:52,396 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-21:ctx-d9e77f3d job-36 ctx-16075f77) Complete async job-36,
jobStatus: SUCCEEDED, resultCode: 0, result:
org.apache.cloudstack.api.response.SnapshotResponse/snapshot/
{"id":"91fec32b-77f1-42af-909d-acca69772581","account":"cdcuser1","domainid":"0dc68c16-49d3-47ef-9ae2-40e043d3fe81","domain":"cdc","snapshottype":"MANUAL","volumeid":"5097706f-97d6-4133-b010-3c803bca66cf","volumename":"DATA-3","volumetype":"DATADISK","created":"2014-10-13T17:39:43+0530","name":"cdcuserinst1_DATA-3_20141013120943","intervaltype":"MANUAL","state":"Error","tags":[],"revertable":false}
2014-10-13 17:39:52,417 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-21:ctx-d9e77f3d job-36) Done executing
org.apache.cloudstack.api.command.user.snapshot.CreateSnapshotCmd for job-36
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7699) Disable attach/detach root volume
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta resolved CLOUDSTACK-7699. - Resolution: Fixed > Disable attach/detach root volume > -- > > Key: CLOUDSTACK-7699 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7699 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.5.0 >Reporter: Nitin Mehta >Priority: Critical > Fix For: 4.5.0 > > > Disable attach/detach root volume -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7699) Disable attach/detach root volume
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169963#comment-14169963 ] Nitin Mehta commented on CLOUDSTACK-7699: - Please note this is disabled in 4.5 only and not in master. > Disable attach/detach root volume > -- > > Key: CLOUDSTACK-7699 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7699 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.5.0 >Reporter: Nitin Mehta >Priority: Critical > Fix For: 4.5.0 > > > Disable attach/detach root volume -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7699) Disable attach/detach root volume
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169957#comment-14169957 ] ASF subversion and git services commented on CLOUDSTACK-7699: - Commit a6d575b1275b861de7fb7e7298282483721aca9c in cloudstack's branch refs/heads/4.5 from [~nitinme] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a6d575b ] CLOUDSTACK-7699: Disable ROOT volume attach/detach ability. > Disable attach/detach root volume > -- > > Key: CLOUDSTACK-7699 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7699 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.5.0 >Reporter: Nitin Mehta >Priority: Critical > Fix For: 4.5.0 > > > Disable attach/detach root volume -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CLOUDSTACK-6772) [UI]need to change popup message fo Attach volume failure "Unexpected exception"
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jessica Wang reassigned CLOUDSTACK-6772:
Assignee: Animesh Chaturvedi (was: Jessica Wang)
Animesh,
This is an API bug, NOT UI bug.
Please assign this bug to an API developer.
===
API developer,
Please change attachVolumes API to return error "Unable to find suitable
primary storage" (like what is logged in log file) instead of a generic error
"Unexpected exception"
i.e. when this is logged in log file:
2014-05-27 10:01:51,381 ERROR [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-1:ctx-bf2f08f1 job-38/job-39 ctx-e6180457) Invocation
exception, caused by: com.cloud.utils.exception.CloudRuntimeException: Unable
to find suitable primary storage when creating volume fifty
Please make sure attachVolumes API return the same error ("Unable to find
suitable primary storage when creating volume fifty").
> [UI]need to change popup message fo Attach volume failure "Unexpected
> exception"
> --
>
> Key: CLOUDSTACK-6772
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6772
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API
>Affects Versions: 4.4.0
>Reporter: prashant kumar mishra
>Assignee: Animesh Chaturvedi
>Priority: Minor
> Fix For: 4.4.0
>
> Attachments: management-server.log
>
>
> step to reproduce
> ==
> 1-tried to attach a volume( size> available size on PS)
> 2-Attach volume failed
> 3-UI pop up a message " Unexpected exception"
> Expected
> ===
> we should clearly pop up message like " no suitable primary storage found"
> Logs
>
> 2014-05-27 10:01:51,360 DEBUG [c.c.s.StorageManagerImpl]
> (Work-Job-Executor-1:ctx-bf2f08f1 job-38/job-39 ctx-e6180457) Insufficient
> un-allocated capacity on: 1 for volume allocation: [Vol[8|vm=null|DATADISK]]
> since its allocated percentage: 1.6727310608597301 has crossed the allocated
> pool.storage.allocated.capacity.disablethreshold: 0.85, skipping this pool
> 2014-05-27 10:01:51,361 DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator]
> (Work-Job-Executor-1:ctx-bf2f08f1 job-38/job-39 ctx-e6180457)
> ClusterScopeStoragePoolAllocator returning 0 suitable storage pools
> 2014-05-27 10:01:51,364 DEBUG [o.a.c.s.a.ZoneWideStoragePoolAllocator]
> (Work-Job-Executor-1:ctx-bf2f08f1 job-38/job-39 ctx-e6180457)
> ZoneWideStoragePoolAllocator to find storage pool
> 2014-05-27 10:01:51,372 WARN [o.a.c.e.o.VolumeOrchestrator]
> (Work-Job-Executor-1:ctx-bf2f08f1 job-38/job-39 ctx-e6180457) Unable to find
> suitable primary storage when creating volume fifty
> 2014-05-27 10:01:51,381 ERROR [c.c.v.VmWorkJobHandlerProxy]
> (Work-Job-Executor-1:ctx-bf2f08f1 job-38/job-39 ctx-e6180457) Invocation
> exception, caused by: com.cloud.utils.exception.CloudRuntimeException: Unable
> to find suitable primary storage when creating volume fifty
> 2014-05-27 10:01:51,382 INFO [c.c.v.VmWorkJobHandlerProxy]
> (Work-Job-Executor-1:ctx-bf2f08f1 job-38/job-39 ctx-e6180457) Rethrow
> exception com.cloud.utils.exception.CloudRuntimeException: Unable to find
> suitable primary storage when creating volume fifty
> 2014-05-27 10:01:51,382 DEBUG [c.c.v.VmWorkJobDispatcher]
> (Work-Job-Executor-1:ctx-bf2f08f1 job-38/job-39) Done with run of VM work
> job: com.cloud.storage.VmWorkAttachVolume for VM 6, job origin: 38
> 2014-05-27 10:01:51,384 ERROR [c.c.v.VmWorkJobDispatcher]
> (Work-Job-Executor-1:ctx-bf2f08f1 job-38/job-39) Unable to complete
> AsyncJobVO {id:39, userId: 2, accountId: 2, instanceType: null, instanceId:
> null, cmd: com.cloud.storage.VmWorkAttachVolume, cmdInfo:
> rO0ABXNyACRjb20uY2xvdWQuc3RvcmFnZS5WbVdvcmtBdHRhY2hWb2x1bWUHra_5YYfiHAIAAkwACGRldmljZUlkdAAQTGphdmEvbGFuZy9Mb25nO0wACHZvbHVtZUlkcQB-AAF4cgATY29tLmNsb3VkLnZtLlZtV29ya5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1ldAASTGphdmEvbGFuZy9TdHJpbmc7eHAAAgACAAZ0ABRWb2x1bWVBcGlTZXJ2aWNlSW1wbHBzcgAOamF2YS5sYW5nLkxvbmc7i-SQzI8j3wIAAUoABXZhbHVleHIAEGphdmEubGFuZy5OdW1iZXKGrJUdC5TgiwIAAHhwAAg,
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 7204337877055, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: Tue May 27 10:01:50 EDT 2014}, job origin:38
> com.cloud.utils.exception.CloudRuntimeException: Unable to find suitable
> primary storage when creating volume fifty
> at
> org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.createVolume(VolumeOrchestrator.java:447)
> at
> org.apache.cloudstack.engine.orchestration.V
[jira] [Created] (CLOUDSTACK-7699) Disable attach/detach root volume
Nitin Mehta created CLOUDSTACK-7699: --- Summary: Disable attach/detach root volume Key: CLOUDSTACK-7699 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7699 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nitin Mehta Priority: Critical Disable attach/detach root volume -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7699) Disable attach/detach root volume
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-7699: Affects Version/s: 4.5.0 > Disable attach/detach root volume > -- > > Key: CLOUDSTACK-7699 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7699 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.5.0 >Reporter: Nitin Mehta >Priority: Critical > Fix For: 4.5.0 > > > Disable attach/detach root volume -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7699) Disable attach/detach root volume
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-7699: Fix Version/s: 4.5.0 > Disable attach/detach root volume > -- > > Key: CLOUDSTACK-7699 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7699 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.5.0 >Reporter: Nitin Mehta >Priority: Critical > Fix For: 4.5.0 > > > Disable attach/detach root volume -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-6772) [UI]need to change popup message fo Attach volume failure "Unexpected exception"
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jessica Wang updated CLOUDSTACK-6772:
-
Component/s: (was: UI)
API
> [UI]need to change popup message fo Attach volume failure "Unexpected
> exception"
> --
>
> Key: CLOUDSTACK-6772
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6772
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API
>Affects Versions: 4.4.0
>Reporter: prashant kumar mishra
>Assignee: Jessica Wang
>Priority: Minor
> Fix For: 4.4.0
>
> Attachments: management-server.log
>
>
> step to reproduce
> ==
> 1-tried to attach a volume( size> available size on PS)
> 2-Attach volume failed
> 3-UI pop up a message " Unexpected exception"
> Expected
> ===
> we should clearly pop up message like " no suitable primary storage found"
> Logs
>
> 2014-05-27 10:01:51,360 DEBUG [c.c.s.StorageManagerImpl]
> (Work-Job-Executor-1:ctx-bf2f08f1 job-38/job-39 ctx-e6180457) Insufficient
> un-allocated capacity on: 1 for volume allocation: [Vol[8|vm=null|DATADISK]]
> since its allocated percentage: 1.6727310608597301 has crossed the allocated
> pool.storage.allocated.capacity.disablethreshold: 0.85, skipping this pool
> 2014-05-27 10:01:51,361 DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator]
> (Work-Job-Executor-1:ctx-bf2f08f1 job-38/job-39 ctx-e6180457)
> ClusterScopeStoragePoolAllocator returning 0 suitable storage pools
> 2014-05-27 10:01:51,364 DEBUG [o.a.c.s.a.ZoneWideStoragePoolAllocator]
> (Work-Job-Executor-1:ctx-bf2f08f1 job-38/job-39 ctx-e6180457)
> ZoneWideStoragePoolAllocator to find storage pool
> 2014-05-27 10:01:51,372 WARN [o.a.c.e.o.VolumeOrchestrator]
> (Work-Job-Executor-1:ctx-bf2f08f1 job-38/job-39 ctx-e6180457) Unable to find
> suitable primary storage when creating volume fifty
> 2014-05-27 10:01:51,381 ERROR [c.c.v.VmWorkJobHandlerProxy]
> (Work-Job-Executor-1:ctx-bf2f08f1 job-38/job-39 ctx-e6180457) Invocation
> exception, caused by: com.cloud.utils.exception.CloudRuntimeException: Unable
> to find suitable primary storage when creating volume fifty
> 2014-05-27 10:01:51,382 INFO [c.c.v.VmWorkJobHandlerProxy]
> (Work-Job-Executor-1:ctx-bf2f08f1 job-38/job-39 ctx-e6180457) Rethrow
> exception com.cloud.utils.exception.CloudRuntimeException: Unable to find
> suitable primary storage when creating volume fifty
> 2014-05-27 10:01:51,382 DEBUG [c.c.v.VmWorkJobDispatcher]
> (Work-Job-Executor-1:ctx-bf2f08f1 job-38/job-39) Done with run of VM work
> job: com.cloud.storage.VmWorkAttachVolume for VM 6, job origin: 38
> 2014-05-27 10:01:51,384 ERROR [c.c.v.VmWorkJobDispatcher]
> (Work-Job-Executor-1:ctx-bf2f08f1 job-38/job-39) Unable to complete
> AsyncJobVO {id:39, userId: 2, accountId: 2, instanceType: null, instanceId:
> null, cmd: com.cloud.storage.VmWorkAttachVolume, cmdInfo:
> rO0ABXNyACRjb20uY2xvdWQuc3RvcmFnZS5WbVdvcmtBdHRhY2hWb2x1bWUHra_5YYfiHAIAAkwACGRldmljZUlkdAAQTGphdmEvbGFuZy9Mb25nO0wACHZvbHVtZUlkcQB-AAF4cgATY29tLmNsb3VkLnZtLlZtV29ya5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1ldAASTGphdmEvbGFuZy9TdHJpbmc7eHAAAgACAAZ0ABRWb2x1bWVBcGlTZXJ2aWNlSW1wbHBzcgAOamF2YS5sYW5nLkxvbmc7i-SQzI8j3wIAAUoABXZhbHVleHIAEGphdmEubGFuZy5OdW1iZXKGrJUdC5TgiwIAAHhwAAg,
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 7204337877055, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: Tue May 27 10:01:50 EDT 2014}, job origin:38
> com.cloud.utils.exception.CloudRuntimeException: Unable to find suitable
> primary storage when creating volume fifty
> at
> org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.createVolume(VolumeOrchestrator.java:447)
> at
> org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.createVolumeOnPrimaryStorage(VolumeOrchestrator.java:734)
> at
> com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1186)
> at
> com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1054)
> at
> com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:2475)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at
> com.cloud.vm.VmWorkJobHandlerProxy.handleV
[jira] [Resolved] (CLOUDSTACK-6284) Root volume detach support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta resolved CLOUDSTACK-6284. - Resolution: Implemented Nothing was needed to be done for Vmware and KVM > Root volume detach support > -- > > Key: CLOUDSTACK-6284 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6284 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.5.0 >Reporter: Alena Prokharchyk >Assignee: Nitin Mehta > Fix For: 4.5.0 > > > Add support for Root volume detach > FS link: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/ROOT+volume+detach -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-5309) version number and requires upgrade fields are not displayed for routers when navigating via physical network tab
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang resolved CLOUDSTACK-5309. -- Resolution: Fixed Fix Version/s: (was: 4.4.0) 4.5.0 shweta, The 2 fields are available now (as in my attached screenshot). But they are under "Infrastructure->Vritual Routers->details", NOT "Infrastructure->zone->physical network - > network service provider -> router/vpc router -> instance ->details" Jessica > version number and requires upgrade fields are not displayed for routers when > navigating via physical network tab > - > > Key: CLOUDSTACK-5309 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5309 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.3.0 >Reporter: shweta agarwal >Assignee: Jessica Wang >Priority: Minor > Fix For: 4.5.0 > > Attachments: 2014-10-13-jessica.PNG, fields-missing.png > > > Repro steps: > Navigate to router /vpc router via > Infrastructure->zone->physical network - > network service provider -> > router/vpc router -> instance ->details > Bug: > Notice router /vpc router is not listing version number and requires upgrade > fields details though api returns this values -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-5309) version number and requires upgrade fields are not displayed for routers when navigating via physical network tab
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang updated CLOUDSTACK-5309: - Attachment: 2014-10-13-jessica.PNG > version number and requires upgrade fields are not displayed for routers when > navigating via physical network tab > - > > Key: CLOUDSTACK-5309 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5309 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.3.0 >Reporter: shweta agarwal >Assignee: Jessica Wang >Priority: Minor > Fix For: 4.4.0 > > Attachments: 2014-10-13-jessica.PNG, fields-missing.png > > > Repro steps: > Navigate to router /vpc router via > Infrastructure->zone->physical network - > network service provider -> > router/vpc router -> instance ->details > Bug: > Notice router /vpc router is not listing version number and requires upgrade > fields details though api returns this values -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7626) SAMLUtilsTest failing inconsistently during build
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169653#comment-14169653 ] Rohit Yadav commented on CLOUDSTACK-7626: - Sure [~ke4qqq] Rayees, can you check again from the logs SAMLUtilsTest passed: Running org.apache.cloudstack.utils.auth.SAMLUtilsTest Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.245 sec But, it's the ConstantTimeBackoffTest that is failing (from logs): Running com.cloud.utils.backoff.impl.ConstantTimeBackoffTest 2014-09-24 03:38:25,036 INFO [backoff.impl.ConstantTimeBackoff] (Thread-1 Thread Thread-1 interrupted while waiting for retry 2014-09-24 03:38:30,699 DEBUG [backoff.impl.ConstantTimeBackoffTest] (main thread started 2014-09-24 03:38:30,700 DEBUG [backoff.impl.ConstantTimeBackoffTest] (Thread-2 before 2014-09-24 03:38:30,799 DEBUG [backoff.impl.ConstantTimeBackoffTest] (main testing wakeup Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 6.034 sec <<< FAILURE! On my system it did not fail, I'll try again with a clean env tomorrow morning. > SAMLUtilsTest failing inconsistently during build > --- > > Key: CLOUDSTACK-7626 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7626 > 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: 4.5 >Reporter: Rayees Namathponnan >Priority: Blocker > Fix For: 4.5.0 > > > 4.5 build failing inconsistently while running unit test, unning > org.apache.cloudstack.utils.auth.SAMLUtilsTest > I have seen this issue multiple times, after the some merge happened 2 week > ago, > > Build fails with below error > [INFO] --- maven-surefire-plugin:2.12:test (default-test) @ cloud-utils --- > [INFO] Surefire report directory: > /root/jenkins/build/workspace/CloudPlatform-4.x-rhel63_Simulator/internal-cloudstack/dist/rpmbuild/BUILD/cloudstack-4.5.0-SNAPSHOT/utils/target/surefire-reports > --- > T E S T S > --- > Running org.apache.cloudstack.utils.auth.SAMLUtilsTest > Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.245 sec > Running com.cloud.utils.TestProfiler > Configure log4j with default properties > 2014-09-24 03:38:16,415 INFO [cloud.utils.TestProfiler] (main:) > testProfiler() started > 2014-09-24 03:38:17,417 INFO [cloud.utils.TestProfiler] (main:) Duration : > 1000 > 2014-09-24 03:38:17,419 INFO [cloud.utils.TestProfiler] (main:) > testProfiler() stopped > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.012 sec > Running com.cloud.utils.ScriptTest > 2014-09-24 03:38:17,526 DEBUG [utils.script.Script] (main:) Executing: > /bin/echo bar > 2014-09-24 03:38:17,537 DEBUG [utils.script.Script] (main:) Execution is > successful. > 2014-09-24 03:38:17,545 DEBUG [utils.script.Script] (main:) Looking for pwd > in the classpath > 2014-09-24 03:38:17,545 DEBUG [utils.script.Script] (main:) System resource: > null > 2014-09-24 03:38:17,546 DEBUG [utils.script.Script] (main:) Classpath > resource: null > 2014-09-24 03:38:17,549 DEBUG [utils.script.Script] (main:) Executing: > /bin/bash -c echo 'hello world!' > 2014-09-24 03:38:17,551 DEBUG [utils.script.Script] (main:) Execution is > successful. > 2014-09-24 03:38:17,551 WARN [utils.script.Script] (main:) Exception: > /bin/bash -c echo 'hello world!' > java.lang.IllegalArgumentException > at com.cloud.utils.ScriptTest$1.interpret(ScriptTest.java:107) > at com.cloud.utils.script.Script.execute(Script.java:220) > at > com.cloud.utils.ScriptTest.executeWithOutputInterpreter(ScriptTest.java:103) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:5
[jira] [Resolved] (CLOUDSTACK-6826) Ability to gracefully expire urls and clean them up when ssvm is destroyed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta resolved CLOUDSTACK-6826. - Resolution: Fixed > Ability to gracefully expire urls and clean them up when ssvm is destroyed > -- > > Key: CLOUDSTACK-6826 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6826 > Project: CloudStack > Issue Type: Improvement > 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 > > > There should be ability to gracefully expire urls and clean them up before > ssvm is destroyed. Currently ssvm can be destroyed even if the agent is in > alert state. Also the cleanup mechanism needs to be enahanced to take care of > multiple ssvms and sending the cleaning up command to the right ssvm. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7469) Simulator build support need to extends for RPM build
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169618#comment-14169618 ] ASF subversion and git services commented on CLOUDSTACK-7469: - Commit e717450e0edd2406c4c3fc7341b3669c4390d507 in cloudstack's branch refs/heads/master from [~alexbre] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e717450 ] CLOUDSTACK-7469 Complete simulator build support The initial commit (f96c65416a2802bcf2a1f8d5a5070ffe6a29111f) missed part of the change to package.sh, so we were not actually passing through the simulator build option to the rpmbuild call. This patch completes the support. > Simulator build support need to extends for RPM build > --- > > Key: CLOUDSTACK-7469 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7469 > 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 >Reporter: Rayees Namathponnan >Assignee: Rayees Namathponnan > Fix For: 4.5.0 > > > Currently there is no option to build rpm with simulator, > We need to update the package.sh file to accept simulator > cloud.spec file need to be updated to build both oss and nooss simulator > buids -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-6826) Ability to gracefully expire urls and clean them up when ssvm is destroyed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169611#comment-14169611 ] Nitin Mehta commented on CLOUDSTACK-6826: - Issue1 - When download urls expire (after extract.url.expiration.interval) the deletion was sent to a random ssvm in the zone instead of the ssvm on which the symlink for the url was created Fix - Improving the download url expiration where the expiration work would be handled by the ssvm that has the corresponding symlink created on it. This is done by figuring out the ssvm from the public ip of the url created and then while cleaning up the url send command to the right ssvm. In case the ssvm doesnt exist send it to any ssvm and cleanup any artifacts if any (like volume). Issue 2 - When ssvm is destroyed download urls were not expired immediately and they were not usable Fix - When any ssvm is destroyed expire all the urls in the zone but setting the download url created time in store ref tables. QA Notes - You can create multiple ssvm in the zone and make sure url expiration is sent to right ssvm In case ssvm is in alert state make sure there is right error there. In case ssvm is destroyed or doesnt exist make sure artifacts (like volume) are still cleaned up Try this for http and https urls. When ssvm is destroyed make sure urls get expired all of them cleaned up in next cycle. > Ability to gracefully expire urls and clean them up when ssvm is destroyed > -- > > Key: CLOUDSTACK-6826 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6826 > Project: CloudStack > Issue Type: Improvement > 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 > > > There should be ability to gracefully expire urls and clean them up before > ssvm is destroyed. Currently ssvm can be destroyed even if the agent is in > alert state. Also the cleanup mechanism needs to be enahanced to take care of > multiple ssvms and sending the cleaning up command to the right ssvm. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-5044) Configuration Framework Issue
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Tutkowski closed CLOUDSTACK-5044. -- Thanks! > Configuration Framework Issue > - > > Key: CLOUDSTACK-5044 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5044 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.3.0 > Environment: Mac OS X 10.8.3 >Reporter: Mike Tutkowski >Assignee: Jessica Wang > Fix For: 4.4.0 > > Attachments: 2014-10-08-jessica.PNG, 2014-10-08-jessica2.PNG > > > When you click on the Settings tab of a cluster, an error is displayed in its > table: > http://i.imgur.com/k7oPoEp.jpg > From the MS console: > ERROR [c.c.a.ApiServer] (1243517273@qtp-1404190447-6:ctx-a7d38106 > ctx-82029652) unhandled exception executing api command: listConfigurations > java.lang.NullPointerException > at > com.cloud.server.ConfigurationServerImpl.getConfigListByScope(ConfigurationServerImpl.java:778) > at > com.cloud.server.ManagementServerImpl.searchForConfigurations(ManagementServerImpl.java:1674) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at > org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) > at > org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) > at > org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) > at com.sun.proxy.$Proxy233.searchForConfigurations(Unknown Source) > at > org.apache.cloudstack.api.command.admin.config.ListCfgsByCmd.execute(ListCfgsByCmd.java:115) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:527) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:370) > at com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:322) > at com.cloud.api.ApiServlet.access$000(ApiServlet.java:52) > at com.cloud.api.ApiServlet$1.run(ApiServlet.java:114) > 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 com.cloud.api.ApiServlet.processRequest(ApiServlet.java:111) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:73) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) > at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) > at > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401) > at > org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) > at > org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) > at > org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) > at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450) > at > org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) > at > org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) > at > org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) > at org.mortbay.jetty.Server.handle(Server.java:326) > at > org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) > at > org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928) > at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549) > at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) > at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) > at > org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannel
[jira] [Commented] (CLOUDSTACK-7626) SAMLUtilsTest failing inconsistently during build
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169284#comment-14169284 ] David Nalley commented on CLOUDSTACK-7626: -- [~bhaisaab] Can you take a look at this? > SAMLUtilsTest failing inconsistently during build > --- > > Key: CLOUDSTACK-7626 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7626 > 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: 4.5 >Reporter: Rayees Namathponnan >Priority: Blocker > Fix For: 4.5.0 > > > 4.5 build failing inconsistently while running unit test, unning > org.apache.cloudstack.utils.auth.SAMLUtilsTest > I have seen this issue multiple times, after the some merge happened 2 week > ago, > > Build fails with below error > [INFO] --- maven-surefire-plugin:2.12:test (default-test) @ cloud-utils --- > [INFO] Surefire report directory: > /root/jenkins/build/workspace/CloudPlatform-4.x-rhel63_Simulator/internal-cloudstack/dist/rpmbuild/BUILD/cloudstack-4.5.0-SNAPSHOT/utils/target/surefire-reports > --- > T E S T S > --- > Running org.apache.cloudstack.utils.auth.SAMLUtilsTest > Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.245 sec > Running com.cloud.utils.TestProfiler > Configure log4j with default properties > 2014-09-24 03:38:16,415 INFO [cloud.utils.TestProfiler] (main:) > testProfiler() started > 2014-09-24 03:38:17,417 INFO [cloud.utils.TestProfiler] (main:) Duration : > 1000 > 2014-09-24 03:38:17,419 INFO [cloud.utils.TestProfiler] (main:) > testProfiler() stopped > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.012 sec > Running com.cloud.utils.ScriptTest > 2014-09-24 03:38:17,526 DEBUG [utils.script.Script] (main:) Executing: > /bin/echo bar > 2014-09-24 03:38:17,537 DEBUG [utils.script.Script] (main:) Execution is > successful. > 2014-09-24 03:38:17,545 DEBUG [utils.script.Script] (main:) Looking for pwd > in the classpath > 2014-09-24 03:38:17,545 DEBUG [utils.script.Script] (main:) System resource: > null > 2014-09-24 03:38:17,546 DEBUG [utils.script.Script] (main:) Classpath > resource: null > 2014-09-24 03:38:17,549 DEBUG [utils.script.Script] (main:) Executing: > /bin/bash -c echo 'hello world!' > 2014-09-24 03:38:17,551 DEBUG [utils.script.Script] (main:) Execution is > successful. > 2014-09-24 03:38:17,551 WARN [utils.script.Script] (main:) Exception: > /bin/bash -c echo 'hello world!' > java.lang.IllegalArgumentException > at com.cloud.utils.ScriptTest$1.interpret(ScriptTest.java:107) > at com.cloud.utils.script.Script.execute(Script.java:220) > at > com.cloud.utils.ScriptTest.executeWithOutputInterpreter(ScriptTest.java:103) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at > org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134) > at > org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl
[jira] [Commented] (CLOUDSTACK-7313) Provisioning vpx in SDX from CS is failing
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169217#comment-14169217 ] ASF subversion and git services commented on CLOUDSTACK-7313: - Commit 0f528df228ac51581b8ff6f63e8ffb6db3d94d39 in cloudstack's branch refs/heads/master from [~rajesh_battala] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=0f528df ] CLOUDSTACK-7313 Fixed issues in provisioning vpx in SDX from CS > Provisioning vpx in SDX from CS is failing > -- > > Key: CLOUDSTACK-7313 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7313 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Devices >Affects Versions: 4.5.0 >Reporter: Rajesh Battala >Assignee: Rajesh Battala >Priority: Critical > Fix For: 4.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-6814) Detected overlapping subnets in differents vlans
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169213#comment-14169213 ] Andrija Panic commented on CLOUDSTACK-6814: --- Hi, any update on this ? True, this is similar issue, but it says in https://issues.apache.org/jira/browse/CLOUDSTACK-4282 that it is resolved in 4.2 verisons, which, for my case is not true - this is overlaping IP range between guest and Public network, not between 2 guest networks... Any plan on fixing this, or not - I would really appreciate info, to be able to proceed with another Cloudstack deployment... > Detected overlapping subnets in differents vlans > > > Key: CLOUDSTACK-6814 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6814 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Network Controller >Affects Versions: 4.3.0 > Environment: not relevant >Reporter: Andrija Panic >Priority: Critical > Labels: guestnetwork, network, overlap, publicip > > I have both Public IP(untagged) and Guest IP range (vlan 500) on same > physical network device eth1 (infrastrucure-zones-physical network-eth1public > tag...) Don't ask me how/why, but it works and it had worked from CS 4.0.0 > till now... > In previous versions I was able to add few additional IP addresses from the > /24 subnet to Guest IP range.. > In 4.3, there is an error message saying that Guest IP range and Public IP > range has overlaping subnets - which IS true - but since those networks ARE > on different vlans completely, I'm not sure why there is such check at all > (overlaping subnet check). Different vlans means different broadcast domains, > why checking IP parameters across different vlans... > Existing database records - first row is Public IP range, rest is all > smaller ranges of IP addresses added few times for Guest IP range. > mysql> select id,uuid,vlan_id,vlan_gateway,vlan_netmask,description from > cloud.vlan; > ++--+-+--+---+---+ > | id | uuid | vlan_id | vlan_gateway > | vlan_netmask | description | > ++--+-+--+---+---+ > | 1 | 10a1e453-7369-4645-9e0f-4936c18bfeac | vlan://untagged | 46.232.xxx.1 > | 255.255.255.0 | 46.232.xxx.240-46.232.xxx.248 | > | 3 | 76c30667-e4c9-4bfe-84cc-3c8e5c608770 | 500 | 46.232.xxx.1 > | 255.255.255.0 | 46.232.xxx.220-46.232.xxx.238 | > | 4 | e2b2b09b-81f2-4ec0-9323-b4c626fcd63b | 500 | 46.232.xxx.1 > | 255.255.255.0 | 46.232.xxx.210-46.232.xxx.219 | > | 5 | f810fd59-ea8a-44fb-850e-58eb791191f0 | 500 | 46.232.xxx.1 > | 255.255.255.0 | 46.232.xxx.202-46.232.xxx.209 | > | 8 | f0bec296-3ac8-483c-a23a-b36213fdf846 | 500 | 46.232.xxx.1 > | 255.255.255.0 | 46.232.xxx.131-46.232.xxx.201 | > ++--+-+--+---+---+ > Now when I want to add new range 46.232.xxx.100-46.232.xxx.130 to eather > Public or Guest network - I can't do that and getting folowing error (tried > adding it to Public range here): > "The IP range with tag: 500 in zone DC-ZURICH-GLATTBRUGG has overlapped with > the subnet. Please specify a different gateway/netmask." > This subnet check across differenet vlans should be removed, and I'm stuck > with over 90% used IP addresses, and can't add more from same /24 range that > we got... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7698) Don't (acquire IP/create NAT) by default while deploying VM if not necessary
Gaurav Aradhye created CLOUDSTACK-7698: -- Summary: Don't (acquire IP/create NAT) by default while deploying VM if not necessary Key: CLOUDSTACK-7698 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7698 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.6.0 Reporter: Gaurav Aradhye Assignee: Gaurav Aradhye Fix For: 4.5.0 In many instances, by default acuire IP/create NAT is done to enable SSH for VM after VM deployment when not required. Clear all such instances. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7648) There are new VM State Machine changes introduced which were missed to capture the usage events
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169131#comment-14169131 ] ASF subversion and git services commented on CLOUDSTACK-7648: - Commit 50185b7c3a1fd26e9a8635c28cee70fda32d3fc5 in cloudstack's branch refs/heads/master from [~damoder.reddy] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=50185b7 ] CLOUDSTACK-7648: There are new VM State Machine changes introduced which were missed to capture the usage events > There are new VM State Machine changes introduced which were missed to > capture the usage events > --- > > Key: CLOUDSTACK-7648 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7648 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.5.0 >Reporter: Damodar Reddy T >Assignee: Damodar Reddy T > Fix For: Future > > > There are new VM State Machine changes introduced while adding VM Sync > changes and these were missed to capture the usage events. > This is causing to get wrong usage statistics for a VM who's state is changed > by VM sync -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7654) createtmplt.sh (invoked by cloud-install-sys-tmplt) is not able to seed zipped templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajesh Battala resolved CLOUDSTACK-7654. Resolution: Fixed > createtmplt.sh (invoked by cloud-install-sys-tmplt) is not able to seed > zipped templates > > > Key: CLOUDSTACK-7654 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7654 > 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 >Reporter: Rajesh Battala >Assignee: Rajesh Battala >Priority: Critical > Fix For: 4.5.0 > > > I tried to seed the hyper-v template which is now in zipped format and the > script seems to be failing to do the same although there is no explicit error > message. > Template used : from jenkins job > Steps: > = > 1. Mount the secondary storage in a local mount point > 2. Seed the system vm template using > /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt > "/usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt > -m /temp -u > http://10.102.192.128/templates/systemvm64template-master-hyperv.vhd.zip -h > hyperv" > 3. Verify after the set up is brought up > Result > = > System VMs fail to come up since the system vm template in the secondary > storage is corrupted. Following is the error message from Hyper-V install: > "Failed to open attachment > '\\smb19\hyperv-share\sowmya-ps1\9e5ee642-ce2a-44fc-bb65-690936634b0f.vhd'. > Error: 'The file or directory is corrupted and unreadable" > The cloud-install-sys-tmplt seems to invoke the createtmplt.sh script to > uncompress and copy the template to secondary storage. But is probably > failing to uncompress. > While executing the script, I get the following message which implies that it > is failing to uncompress the zipped file: > "File > /usr/share/cloudstack-common/scripts/storage/secondary/2618f45e-c2fc-445b-81cd-b93906d23dda.vhd > does not appear to be compressed" > Further, when we manually unzip the above zipped template file and launch a > VM from the unzipped vhd, it launches the VM properly. This implies that it > is either not un compressed or somewhere corrupting the file before copying > over to the secondary storage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
