[jira] [Created] (CLOUDSTACK-5865) Unable to use login API with api key and signature
Likitha Shetty created CLOUDSTACK-5865: -- Summary: Unable to use login API with api key and signature Key: CLOUDSTACK-5865 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5865 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: API Affects Versions: 4.3.0 Reporter: Likitha Shetty Assignee: Likitha Shetty Fix For: 4.4.0 Unable to use login API with if domainId parameter is id and not uuid. http://mgmt-server-ip:8080/client/api?command=loginusername=user1domainid=1apikey=apiKeysignature=signature API log 2013-11-18 13:33:17,263 INFO [cloud.api.ApiServer] (catalina-exec-1:null) 10.9.159.4 – GET command=login unknown exception writing api response Login is successful when the format is changed for domain id parameter in the API call from id format to UUID format. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5865) Unable to use login API
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty updated CLOUDSTACK-5865: --- Summary: Unable to use login API (was: Unable to use login API with api key and signature) Unable to use login API Key: CLOUDSTACK-5865 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5865 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Affects Versions: 4.3.0 Reporter: Likitha Shetty Assignee: Likitha Shetty Fix For: 4.4.0 Unable to use login API with if domainId parameter is id and not uuid. http://mgmt-server-ip:8080/client/api?command=loginusername=user1domainid=1apikey=apiKeysignature=signature API log 2013-11-18 13:33:17,263 INFO [cloud.api.ApiServer] (catalina-exec-1:null) 10.9.159.4 – GET command=login unknown exception writing api response Login is successful when the format is changed for domain id parameter in the API call from id format to UUID format. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5865) Unable to use login API if domainId parameter is id and not uuid
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty updated CLOUDSTACK-5865: --- Summary: Unable to use login API if domainId parameter is id and not uuid (was: Unable to use login API ) Unable to use login API if domainId parameter is id and not uuid Key: CLOUDSTACK-5865 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5865 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Affects Versions: 4.3.0 Reporter: Likitha Shetty Assignee: Likitha Shetty Fix For: 4.4.0 Unable to use login API with if domainId parameter is id and not uuid. http://mgmt-server-ip:8080/client/api?command=loginusername=user1domainid=1apikey=apiKeysignature=signature API log 2013-11-18 13:33:17,263 INFO [cloud.api.ApiServer] (catalina-exec-1:null) 10.9.159.4 – GET command=login unknown exception writing api response Login is successful when the format is changed for domain id parameter in the API call from id format to UUID format. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5865) Unable to use login API if domainId parameter is id and not uuid
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13870520#comment-13870520 ] ASF subversion and git services commented on CLOUDSTACK-5865: - Commit e5512960afa384245cfb9d012ac6482b2b7f8940 in branch refs/heads/master from [~likithas] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e551296 ] CLOUDSTACK-5865. Unable to use login API if domainId parameter is id and not uuid Unable to use login API if domainId parameter is id and not uuid Key: CLOUDSTACK-5865 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5865 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Affects Versions: 4.3.0 Reporter: Likitha Shetty Assignee: Likitha Shetty Fix For: 4.4.0 Unable to use login API with if domainId parameter is id and not uuid. http://mgmt-server-ip:8080/client/api?command=loginusername=user1domainid=1apikey=apiKeysignature=signature API log 2013-11-18 13:33:17,263 INFO [cloud.api.ApiServer] (catalina-exec-1:null) 10.9.159.4 – GET command=login unknown exception writing api response Login is successful when the format is changed for domain id parameter in the API call from id format to UUID format. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CLOUDSTACK-5865) Unable to use login API if domainId parameter is id and not uuid
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-5865. Resolution: Fixed Unable to use login API if domainId parameter is id and not uuid Key: CLOUDSTACK-5865 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5865 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Affects Versions: 4.3.0 Reporter: Likitha Shetty Assignee: Likitha Shetty Fix For: 4.4.0 Unable to use login API with if domainId parameter is id and not uuid. http://mgmt-server-ip:8080/client/api?command=loginusername=user1domainid=1apikey=apiKeysignature=signature API log 2013-11-18 13:33:17,263 INFO [cloud.api.ApiServer] (catalina-exec-1:null) 10.9.159.4 – GET command=login unknown exception writing api response Login is successful when the format is changed for domain id parameter in the API call from id format to UUID format. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-2237) Automation : Security Groups isolation in advanced Zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13870547#comment-13870547 ] ASF subversion and git services commented on CLOUDSTACK-2237: - Commit c108d7f0d0e1e1e746dd186e3153c2d8387da7e2 in branch refs/heads/master from [~ashutoshk] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c108d7f ] CLOUDSTACK-2237: Automation-Adding next set of test cases for feature - SG in advanced zone Automation : Security Groups isolation in advanced Zone --- Key: CLOUDSTACK-2237 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2237 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Reporter: Sudha Ponnaganti Assignee: Ashutosk Kelkar Fix For: 4.3.0 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5681) Contrail:MS:API: Create network fails with NPE due to missing CIDR
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13870554#comment-13870554
]
Vinod Nair commented on CLOUDSTACK-5681:
Root cause is that ACS is allowing to create a VN without a net mask value,
Whereas list networks command is checking for if cidr value is present or not
for a network while iterating all networks. If it finds a network without cidr
it throws Exception and returns empty
This issue exists in ACS4.3 also ..
Contrail:MS:API: Create network fails with NPE due to missing CIDR
--
Key: CLOUDSTACK-5681
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5681
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: API, Contrail, Management Server
Affects Versions: 4.2.0
Environment: Contrail
Reporter: Parth Jagirdar
Assignee: Santhosh Kumar Edukulla
Priority: Critical
CIDR is not required param in API, but without CIDR exceptions are thrown.
2013-12-27 16:44:14,088 ERROR [cloud.api.ApiServer] (catalina-exec-3:null)
unhandled exception executing api command: createNetwork
java.lang.NullPointerException
at
com.cloud.network.NetworkModelImpl.getAvailableIps(NetworkModelImpl.java:1694)
at
com.cloud.network.NetworkModelImpl.canUseForDeploy(NetworkModelImpl.java:585)
at com.cloud.api.ApiDBUtils.canUseForDeploy(ApiDBUtils.java:1147)
at
com.cloud.api.ApiResponseHelper.createNetworkResponse(ApiResponseHelper.java:2259)
at
org.apache.cloudstack.api.command.user.network.CreateNetworkCmd.execute(CreateNetworkCmd.java:288)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
at com.cloud.api.ApiServer.queueCommand(ApiServer.java:514)
at com.cloud.api.ApiServer.handleRequest(ApiServer.java:372)
at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:305)
at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
at
org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
at
org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2266)
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:724)
2013-12-27 16:44:14,093 DEBUG [cloud.api.ApiServlet] (catalina-exec-3:null)
===END=== 10.215.2.19 -- GET
command=createNetworkresponse=jsonsessionkey=ijYX%2B4fZ2EjdBMgdrTgGLJU2e60%3DnetworkOfferingId=c9298387-30ec-40be-a0b7-cf54829fa5f8name=tempdisplayText=tempzoneId=37b6d96d-5b66-429b-8e8e-b7bd6d12ae96_=1388191455496
2013-12-27 16:44:18,776 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-2:null) SeqA 2-11511: Processing Seq 2-11511: { Cmd ,
MgmtId: -1, via: 2, Ver: v1, Flags: 11,
[{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:2,_loadInfo:{\n
\connections\: []\n},wait:0}}] }
2013-12-27 16:44:18,780 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-2:null) SeqA 2-11511: Sending Seq 2-11511: { Ans: ,
MgmtId: 86780043846508, via: 2, Ver: v1, Flags: 100010,
[{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
2013-12-27 16:44:18,909 DEBUG [storage.secondary.SecondaryStorageManagerImpl]
(secstorage-1:null) Zone 1 is ready to launch secondary storage VM
2013-12-27 16:44:19,091 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl]
(consoleproxy-1:null) Zone 1 is ready to launch console proxy
2013-12-27 16:44:20,476 DEBUG
[jira] [Created] (CLOUDSTACK-5866) Remove maven profile used to configure zone
sebastien goasguen created CLOUDSTACK-5866: -- Summary: Remove maven profile used to configure zone Key: CLOUDSTACK-5866 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5866 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: marvin Affects Versions: 4.3.0 Reporter: sebastien goasguen When running the simulator, you can use a maven profile to configure a zone: mvn -Pdeveloper,marvin.setup -Dmarvin.config=setup/dev/basic.cfg -pl :cloud-marvin integration-test We need to investigate removing this marvin.setup profile all together. Discuss implications and make sure nothing is using it. When removing we also need to updated documentation. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5867) [Monitor] service monitor is failed to configure in mvm
Jayapal Reddy created CLOUDSTACK-5867: - Summary: [Monitor] service monitor is failed to configure in mvm Key: CLOUDSTACK-5867 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5867 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Jayapal Reddy service monitor command is failing in kvm -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5747) [Upgrade]Network restart failed after upgarding from 2.2.16 to 4.3 with External Firewall SRX added to CS.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13870698#comment-13870698 ] ASF subversion and git services commented on CLOUDSTACK-5747: - Commit ac539329251a4f8ddf77f7622de5beaae18c9eee in branch refs/heads/4.3 from [~jayapal] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ac53932 ] CLOUDSTACK-5747 Fixed network restart issue with SRX [Upgrade]Network restart failed after upgarding from 2.2.16 to 4.3 with External Firewall SRX added to CS. -- Key: CLOUDSTACK-5747 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5747 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller, Network Devices, Upgrade Affects Versions: 4.3.0 Environment: upgraded the CS2.2.16 with SRX to 4.3 Reporter: manasaveloori Assignee: Jayapal Reddy Fix For: 4.3.0 Attachments: management-server.log.rar, mysqldump2216.dmp, mysqldump4.3.dmp Steps: 1. Deploy CS 2.2 X.16 using Xen5.6 sp2 HV. 2. Add the External firewall SRX to CS. 3. Set the GC parameter firewall.rule.ui.enabled to true. 4. Now acquire the IP and configure firewall and PF rules. 5. Upgrade the CS to 4.3. 6. Stop and start all the System VMs and router VMs so that the new template is upgraded. 7. Now perform Network restart on which the firwall and PF rules are configured. Observation : Observed the follwoing exceptions in Ms logs and Network restart failed. 2014-01-03 17:43:32,329 DEBUG [c.c.n.r.JuniperSrxResource] (DirectAgent-76:ctx-2128a4a2) Added Egress firewall rule for guest network 965 2014-01-03 17:43:32,329 DEBUG [c.c.n.r.JuniperSrxResource] (DirectAgent-76:ctx-2128a4a2) Sending request: !--Licensed to the Apache Software Foundation (ASF) under oneor more contributor license agreements. See the NOTICE filedistributed with this work for additional informationregarding copyright ownership. The ASF licenses this fileto you under the Apache License, Version 2.0 (theLicense); you may not use this file except in compliancewith the License. You may obtain a copy of the License athttp://www.apache.org/licenses/LICENSE-2.0Unless required by applicable law or agreed to in writing,software distributed under the License is distributed on anAS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANYKIND, either express or implied. See the License for thespecific language governing permissions and limitationsunder the License.--rpccommit-configuration/commit-configuration/rpc 2014-01-03 17:43:33,966 DEBUG [c.c.n.r.JuniperSrxResource] (DirectAgent-76:ctx-2128a4a2) Checking response: rpc-reply xmlns:junos=http://xml.juniper.net/junos/10.4R6/junos;commit-resultsload-success/xnm:error xmlns=http://xml.juniper.net/xnm/1.1/xnm; xmlns:xnm=http://xml.juniper.net/xnm/1.1/xnm;source-daemonmgd/source-daemonedit-path[edit security policies from-zone trust to-zone untrust policy egress-trust-untrust-965]/edit-pathstatementmatch/statementmessageMissing mandatory statement: 'source-address'/message/xnm:errorxnm:error xmlns=http://xml.juniper.net/xnm/1.1/xnm; xmlns:xnm=http://xml.juniper.net/xnm/1.1/xnm;messagecommit failed: (missing statements)/message/xnm:error/commit-results/rpc-reply 2014-01-03 17:43:33,966 ERROR [c.c.n.r.JuniperSrxResource] (DirectAgent-76:ctx-2128a4a2) Request failed due to: Missing mandatory statement: 'source-address' 2014-01-03 17:43:33,967 ERROR [c.c.n.r.JuniperSrxResource] (DirectAgent-76:ctx-2128a4a2) com.cloud.utils.exception.ExecutionException: Failed to commit to global configuration. 2014-01-03 17:43:33,967 DEBUG [c.c.n.r.JuniperSrxResource] (DirectAgent-76:ctx-2128a4a2) Sending request: !--Licensed to the Apache Software Foundation (ASF) under oneor more contributor license agreements. See the NOTICE filedistributed with this work for additional informationregarding copyright ownership. The ASF licenses this fileto you under the Apache License, Version 2.0 (theLicense); you may not use this file except in compliancewith the License. You may obtain a copy of the License athttp://www.apache.org/licenses/LICENSE-2.0Unless required by applicable law or agreed to in writing,software distributed under the License is distributed on anAS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANYKIND, either express or implied. See the License for thespecific language governing permissions and limitationsunder the License.--rpcclose-configuration//rpc 2014-01-03 17:43:34,012 DEBUG [c.c.n.r.JuniperSrxResource] (DirectAgent-76:ctx-2128a4a2) Checking response: rpc-reply
[jira] [Commented] (CLOUDSTACK-5867) [Monitor] service monitor is failed to configure in mvm
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13870697#comment-13870697 ] ASF subversion and git services commented on CLOUDSTACK-5867: - Commit b177015121d784980df14fca57f2e01b6af8c1f7 in branch refs/heads/4.3 from [~jayapal] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b177015 ] CLOUDSTACK-5867 Fixed SetMonitorServiceCommand command path [Monitor] service monitor is failed to configure in mvm --- Key: CLOUDSTACK-5867 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5867 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Jayapal Reddy service monitor command is failing in kvm -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Assigned] (CLOUDSTACK-5867) [Monitor] service monitor is failed to configure in mvm
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayapal Reddy reassigned CLOUDSTACK-5867: - Assignee: Jayapal Reddy [Monitor] service monitor is failed to configure in mvm --- Key: CLOUDSTACK-5867 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5867 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Jayapal Reddy Assignee: Jayapal Reddy service monitor command is failing in kvm -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Assigned] (CLOUDSTACK-5342) [Automation] Add NIC to virtual machine fails in KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saksham Srivastava reassigned CLOUDSTACK-5342:
--
Assignee: (was: Saksham Srivastava)
[Automation] Add NIC to virtual machine fails in KVM
Key: CLOUDSTACK-5342
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5342
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Network Controller
Affects Versions: 4.3.0
Environment: KVM advanced
Reporter: Gaurav Aradhye
Fix For: 4.3.0
Add network to VM test cases fail in KVM with following error.
Execute cmd: asyncquery failed, due to: {errorcode : 530, errortext :
u'Unable to add NIC to VM[User|VM-e9350ee5-bf2e-418c-91d6-1535dcb4d488]'}
The same test cases execute successfully on XenServer. As per the feature
specification (see
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Add+Remove+Networks+to+VMs),
Add network to VM feature should be supported on KVM too.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5868) Default templates are still referring to 32 bit templates in DB
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-5868: - Assignee: Sateesh Chodapuneedi Default templates are still referring to 32 bit templates in DB --- Key: CLOUDSTACK-5868 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5868 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Template Affects Versions: 4.3.0 Environment: All HVs Reporter: Sudha Ponnaganti Assignee: Sateesh Chodapuneedi Priority: Blocker Fix For: 4.3.0 Default template location is referring to older templates. Need to switch to 4.3 ++---+--+++-+ | id | name | bits | url | type | hypervisor_type | ++---+--+++-+ | 1 | SystemVM Template (XenServer) | 32 | http://download.cloud.com/templates/4.2/systemvmtemplate-2013-07-12-master-xen.vhd.bz2 | SYSTEM | XenServer | | 8 | SystemVM Template (vSphere) | 32 | http://download.cloud.com/templates/4.2/systemvmtemplate-4.2-vh7.ova | SYSTEM | VMware | ++---+--+++-+ -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5868) Default templates are still referring to 32 bit templates in DB
Sudha Ponnaganti created CLOUDSTACK-5868: Summary: Default templates are still referring to 32 bit templates in DB Key: CLOUDSTACK-5868 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5868 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Template Affects Versions: 4.3.0 Environment: All HVs Reporter: Sudha Ponnaganti Priority: Blocker Fix For: 4.3.0 Default template location is referring to older templates. Need to switch to 4.3 ++---+--+++-+ | id | name | bits | url | type | hypervisor_type | ++---+--+++-+ | 1 | SystemVM Template (XenServer) | 32 | http://download.cloud.com/templates/4.2/systemvmtemplate-2013-07-12-master-xen.vhd.bz2 | SYSTEM | XenServer | | 8 | SystemVM Template (vSphere) | 32 | http://download.cloud.com/templates/4.2/systemvmtemplate-4.2-vh7.ova | SYSTEM | VMware | ++---+--+++-+ -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5869) [Hyper-V] VM creation on local storage is failing
Devdeep Singh created CLOUDSTACK-5869:
-
Summary: [Hyper-V] VM creation on local storage is failing
Key: CLOUDSTACK-5869
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5869
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Devdeep Singh
Assignee: Devdeep Singh
Priority: Blocker
System vms are not getting deployed on a Hyper-V setup. It fails with the
following stack trace
2014-01-14 13:29:57,627 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-162:ctx-59574cc6) POST response
is[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.,newData:null,contextMap:{}}}]
2014-01-14 13:29:57,628 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-162:ctx-59574cc6) executeRequest received response
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from \u0027UncPath\u0027 on
\u0027HypervResource.PrimaryDataStoreTO\u0027.,contextMap:{},wait:0}}]
2014-01-14 13:29:57,628 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-162:ctx-59574cc6) Seq 5-374407591: Response Received:
2014-01-14 13:29:57,628 DEBUG [c.c.a.t.Request] (DirectAgent-162:ctx-59574cc6)
Seq 5-374407591: Processing: { Ans: , MgmtId: 280320865129348, via: 5, Ver: v1,
Flags: 10,
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.,wait:0}}] }
2014-01-14 13:29:57,628 DEBUG [c.c.a.t.Request] (Job-Executor-41:ctx-20d66cbd
ctx-b360b710) Seq 5-374407591: Received: { Ans: , MgmtId: 280320865129348, via:
5, Ver: v1, Flags: 10,
{ CopyCmdAnswer }
}
2014-01-14 13:29:57,633 WARN [o.a.c.s.d.ObjectInDataStoreManagerImpl]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unsupported data object (VOLUME,
org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@5bf2f643), no need
to delete from object in store ref table
2014-01-14 13:29:57,633 DEBUG [o.a.c.e.o.VolumeOrchestrator]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unable to create
Vol[23|vm=20|ROOT]:org.apache.cloudstack.storage.command.CopyCommand failed on
exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.
2014-01-14 13:29:57,633 INFO [c.c.v.VirtualMachineManagerImpl]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unable to contact resource.
com.cloud.exception.StorageUnavailableException: Resource [StoragePool:3] is
unreachable: Unable to create
Vol[23|vm=20|ROOT]:org.apache.cloudstack.storage.command.CopyCommand failed on
exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.
at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.recreateVolume(VolumeOrchestrator.java:1174)
at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.prepare(VolumeOrchestrator.java:1216)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:944)
at
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:747)
at
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:593)
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:3572)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3152)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3138)
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:616)
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 com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:50)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
at
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
at
[jira] [Updated] (CLOUDSTACK-5869) [Hyper-V] System VM creation on local storage is failing
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh updated CLOUDSTACK-5869:
--
Summary: [Hyper-V] System VM creation on local storage is failing (was:
[Hyper-V] VM creation on local storage is failing)
[Hyper-V] System VM creation on local storage is failing
Key: CLOUDSTACK-5869
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5869
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Reporter: Devdeep Singh
Assignee: Devdeep Singh
Priority: Blocker
System vms are not getting deployed on a Hyper-V setup. It fails with the
following stack trace
2014-01-14 13:29:57,627 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-162:ctx-59574cc6) POST response
is[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.,newData:null,contextMap:{}}}]
2014-01-14 13:29:57,628 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-162:ctx-59574cc6) executeRequest received response
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from \u0027UncPath\u0027 on
\u0027HypervResource.PrimaryDataStoreTO\u0027.,contextMap:{},wait:0}}]
2014-01-14 13:29:57,628 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-162:ctx-59574cc6) Seq 5-374407591: Response Received:
2014-01-14 13:29:57,628 DEBUG [c.c.a.t.Request]
(DirectAgent-162:ctx-59574cc6) Seq 5-374407591: Processing: { Ans: , MgmtId:
280320865129348, via: 5, Ver: v1, Flags: 10,
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.,wait:0}}] }
2014-01-14 13:29:57,628 DEBUG [c.c.a.t.Request] (Job-Executor-41:ctx-20d66cbd
ctx-b360b710) Seq 5-374407591: Received: { Ans: , MgmtId: 280320865129348,
via: 5, Ver: v1, Flags: 10,
{ CopyCmdAnswer }
}
2014-01-14 13:29:57,633 WARN [o.a.c.s.d.ObjectInDataStoreManagerImpl]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unsupported data object (VOLUME,
org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@5bf2f643), no
need to delete from object in store ref table
2014-01-14 13:29:57,633 DEBUG [o.a.c.e.o.VolumeOrchestrator]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unable to create
Vol[23|vm=20|ROOT]:org.apache.cloudstack.storage.command.CopyCommand failed
on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.
2014-01-14 13:29:57,633 INFO [c.c.v.VirtualMachineManagerImpl]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unable to contact resource.
com.cloud.exception.StorageUnavailableException: Resource [StoragePool:3] is
unreachable: Unable to create
Vol[23|vm=20|ROOT]:org.apache.cloudstack.storage.command.CopyCommand failed
on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.
at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.recreateVolume(VolumeOrchestrator.java:1174)
at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.prepare(VolumeOrchestrator.java:1216)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:944)
at
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:747)
at
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:593)
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:3572)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3152)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3138)
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:616)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
[jira] [Commented] (CLOUDSTACK-5689) [Automation] component.test_vpc_network.TestVPCNetworkUpgrade.test_01_network_services_upgrade failing with SSH error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13870760#comment-13870760 ] ASF subversion and git services commented on CLOUDSTACK-5689: - Commit f58d77c8d1fd9eb2bee927f7d92e50ba1553c7b6 in branch refs/heads/master from [~devdeep] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f58d77c ] CLOUDSTACK-5689: System vm creation on local storage fails for hyper-v. A null pointer exception was getting generated when a VolumeTO object was serialized to create an answer object. If a local storage is used the uri field will be null. Added null checks for the same. [Automation] component.test_vpc_network.TestVPCNetworkUpgrade.test_01_network_services_upgrade failing with SSH error - Key: CLOUDSTACK-5689 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5689 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.3.0 Reporter: Gaurav Aradhye Assignee: Gaurav Aradhye Labels: automation Fix For: 4.3.0 test_01_network_services_upgrade (integration.component.test_vpc_network.TestVPCNetworkUpgrade): CRITICAL: FAILED: test_01_network_services_upgrade: Traceback (most recent call last): File /usr/local/lib/python2.7/unittest/case.py, line 318, in run testMethod() File /root/cloudstack/test/integration/component/test_vpc_network.py, line 1853, in test_01_network_services_upgrade (public_ip_1.ipaddress.ipaddress, e)) File /usr/local/lib/python2.7/unittest/case.py, line 393, in fail raise self.failureException(msg) AssertionError: Failed to SSH into VM - 10.147.53.36, SSH connection has Failed. Waited 600s. Error is Connection Failed -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5689) [Automation] component.test_vpc_network.TestVPCNetworkUpgrade.test_01_network_services_upgrade failing with SSH error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13870759#comment-13870759 ] ASF subversion and git services commented on CLOUDSTACK-5689: - Commit 5bf5d3669d22d48f4b2db01c76647c977fad7468 in branch refs/heads/4.3 from [~devdeep] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5bf5d36 ] CLOUDSTACK-5689: System vm creation on local storage fails for hyper-v. A null pointer exception was getting generated when a VolumeTO object was serialized to create an answer object. If a local storage is used the uri field will be null. Added null checks for the same. [Automation] component.test_vpc_network.TestVPCNetworkUpgrade.test_01_network_services_upgrade failing with SSH error - Key: CLOUDSTACK-5689 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5689 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.3.0 Reporter: Gaurav Aradhye Assignee: Gaurav Aradhye Labels: automation Fix For: 4.3.0 test_01_network_services_upgrade (integration.component.test_vpc_network.TestVPCNetworkUpgrade): CRITICAL: FAILED: test_01_network_services_upgrade: Traceback (most recent call last): File /usr/local/lib/python2.7/unittest/case.py, line 318, in run testMethod() File /root/cloudstack/test/integration/component/test_vpc_network.py, line 1853, in test_01_network_services_upgrade (public_ip_1.ipaddress.ipaddress, e)) File /usr/local/lib/python2.7/unittest/case.py, line 393, in fail raise self.failureException(msg) AssertionError: Failed to SSH into VM - 10.147.53.36, SSH connection has Failed. Waited 600s. Error is Connection Failed -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CLOUDSTACK-5869) [Hyper-V] System VM creation on local storage is failing
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh resolved CLOUDSTACK-5869.
---
Resolution: Fixed
Fixed in commits
Commit 5bf5d3669d22d48f4b2db01c76647c977fad7468 in branch refs/heads/4.3 from
Devdeep Singh
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5bf5d36 ]
CLOUDSTACK-5689: System vm creation on local storage fails for hyper-v. A
null pointer exception was getting generated when a VolumeTO object was
serialized to create an answer object. If a local storage is used the uri
field will be null. Added null checks for the same.
ASF subversion and git services added a comment - a minute ago
Commit f58d77c8d1fd9eb2bee927f7d92e50ba1553c7b6 in branch refs/heads/master
from Devdeep Singh
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f58d77c ]
CLOUDSTACK-5689: System vm creation on local storage fails for hyper-v. A
null pointer exception was getting generated when a VolumeTO object was
serialized to create an answer object. If a local storage is used the uri
field will be null. Added null checks for the same.
I gave the wrong bug id in the commit message.
[Hyper-V] System VM creation on local storage is failing
Key: CLOUDSTACK-5869
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5869
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Reporter: Devdeep Singh
Assignee: Devdeep Singh
Priority: Blocker
System vms are not getting deployed on a Hyper-V setup. It fails with the
following stack trace
2014-01-14 13:29:57,627 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-162:ctx-59574cc6) POST response
is[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.,newData:null,contextMap:{}}}]
2014-01-14 13:29:57,628 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-162:ctx-59574cc6) executeRequest received response
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from \u0027UncPath\u0027 on
\u0027HypervResource.PrimaryDataStoreTO\u0027.,contextMap:{},wait:0}}]
2014-01-14 13:29:57,628 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-162:ctx-59574cc6) Seq 5-374407591: Response Received:
2014-01-14 13:29:57,628 DEBUG [c.c.a.t.Request]
(DirectAgent-162:ctx-59574cc6) Seq 5-374407591: Processing: { Ans: , MgmtId:
280320865129348, via: 5, Ver: v1, Flags: 10,
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.,wait:0}}] }
2014-01-14 13:29:57,628 DEBUG [c.c.a.t.Request] (Job-Executor-41:ctx-20d66cbd
ctx-b360b710) Seq 5-374407591: Received: { Ans: , MgmtId: 280320865129348,
via: 5, Ver: v1, Flags: 10,
{ CopyCmdAnswer }
}
2014-01-14 13:29:57,633 WARN [o.a.c.s.d.ObjectInDataStoreManagerImpl]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unsupported data object (VOLUME,
org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@5bf2f643), no
need to delete from object in store ref table
2014-01-14 13:29:57,633 DEBUG [o.a.c.e.o.VolumeOrchestrator]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unable to create
Vol[23|vm=20|ROOT]:org.apache.cloudstack.storage.command.CopyCommand failed
on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.
2014-01-14 13:29:57,633 INFO [c.c.v.VirtualMachineManagerImpl]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unable to contact resource.
com.cloud.exception.StorageUnavailableException: Resource [StoragePool:3] is
unreachable: Unable to create
Vol[23|vm=20|ROOT]:org.apache.cloudstack.storage.command.CopyCommand failed
on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.
at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.recreateVolume(VolumeOrchestrator.java:1174)
at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.prepare(VolumeOrchestrator.java:1216)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:944)
at
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:747)
at
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:593)
at
org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:237)
at
[jira] [Updated] (CLOUDSTACK-5869) [Hyper-V] System VM creation on local storage is failing
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh updated CLOUDSTACK-5869:
--
Labels: hyper-V, (was: )
[Hyper-V] System VM creation on local storage is failing
Key: CLOUDSTACK-5869
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5869
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Affects Versions: 4.3.0
Reporter: Devdeep Singh
Assignee: Devdeep Singh
Priority: Blocker
Labels: hyper-V,
Fix For: 4.3.0
System vms are not getting deployed on a Hyper-V setup. It fails with the
following stack trace
2014-01-14 13:29:57,627 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-162:ctx-59574cc6) POST response
is[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.,newData:null,contextMap:{}}}]
2014-01-14 13:29:57,628 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-162:ctx-59574cc6) executeRequest received response
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from \u0027UncPath\u0027 on
\u0027HypervResource.PrimaryDataStoreTO\u0027.,contextMap:{},wait:0}}]
2014-01-14 13:29:57,628 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-162:ctx-59574cc6) Seq 5-374407591: Response Received:
2014-01-14 13:29:57,628 DEBUG [c.c.a.t.Request]
(DirectAgent-162:ctx-59574cc6) Seq 5-374407591: Processing: { Ans: , MgmtId:
280320865129348, via: 5, Ver: v1, Flags: 10,
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.,wait:0}}] }
2014-01-14 13:29:57,628 DEBUG [c.c.a.t.Request] (Job-Executor-41:ctx-20d66cbd
ctx-b360b710) Seq 5-374407591: Received: { Ans: , MgmtId: 280320865129348,
via: 5, Ver: v1, Flags: 10,
{ CopyCmdAnswer }
}
2014-01-14 13:29:57,633 WARN [o.a.c.s.d.ObjectInDataStoreManagerImpl]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unsupported data object (VOLUME,
org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@5bf2f643), no
need to delete from object in store ref table
2014-01-14 13:29:57,633 DEBUG [o.a.c.e.o.VolumeOrchestrator]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unable to create
Vol[23|vm=20|ROOT]:org.apache.cloudstack.storage.command.CopyCommand failed
on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.
2014-01-14 13:29:57,633 INFO [c.c.v.VirtualMachineManagerImpl]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unable to contact resource.
com.cloud.exception.StorageUnavailableException: Resource [StoragePool:3] is
unreachable: Unable to create
Vol[23|vm=20|ROOT]:org.apache.cloudstack.storage.command.CopyCommand failed
on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.
at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.recreateVolume(VolumeOrchestrator.java:1174)
at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.prepare(VolumeOrchestrator.java:1216)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:944)
at
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:747)
at
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:593)
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:3572)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3152)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3138)
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:616)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
[jira] [Updated] (CLOUDSTACK-5869) [Hyper-V] System VM creation on local storage is failing
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh updated CLOUDSTACK-5869:
--
Affects Version/s: 4.3.0
[Hyper-V] System VM creation on local storage is failing
Key: CLOUDSTACK-5869
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5869
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Affects Versions: 4.3.0
Reporter: Devdeep Singh
Assignee: Devdeep Singh
Priority: Blocker
Labels: hyper-V,
Fix For: 4.3.0
System vms are not getting deployed on a Hyper-V setup. It fails with the
following stack trace
2014-01-14 13:29:57,627 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-162:ctx-59574cc6) POST response
is[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.,newData:null,contextMap:{}}}]
2014-01-14 13:29:57,628 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-162:ctx-59574cc6) executeRequest received response
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from \u0027UncPath\u0027 on
\u0027HypervResource.PrimaryDataStoreTO\u0027.,contextMap:{},wait:0}}]
2014-01-14 13:29:57,628 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-162:ctx-59574cc6) Seq 5-374407591: Response Received:
2014-01-14 13:29:57,628 DEBUG [c.c.a.t.Request]
(DirectAgent-162:ctx-59574cc6) Seq 5-374407591: Processing: { Ans: , MgmtId:
280320865129348, via: 5, Ver: v1, Flags: 10,
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.,wait:0}}] }
2014-01-14 13:29:57,628 DEBUG [c.c.a.t.Request] (Job-Executor-41:ctx-20d66cbd
ctx-b360b710) Seq 5-374407591: Received: { Ans: , MgmtId: 280320865129348,
via: 5, Ver: v1, Flags: 10,
{ CopyCmdAnswer }
}
2014-01-14 13:29:57,633 WARN [o.a.c.s.d.ObjectInDataStoreManagerImpl]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unsupported data object (VOLUME,
org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@5bf2f643), no
need to delete from object in store ref table
2014-01-14 13:29:57,633 DEBUG [o.a.c.e.o.VolumeOrchestrator]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unable to create
Vol[23|vm=20|ROOT]:org.apache.cloudstack.storage.command.CopyCommand failed
on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.
2014-01-14 13:29:57,633 INFO [c.c.v.VirtualMachineManagerImpl]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unable to contact resource.
com.cloud.exception.StorageUnavailableException: Resource [StoragePool:3] is
unreachable: Unable to create
Vol[23|vm=20|ROOT]:org.apache.cloudstack.storage.command.CopyCommand failed
on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.
at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.recreateVolume(VolumeOrchestrator.java:1174)
at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.prepare(VolumeOrchestrator.java:1216)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:944)
at
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:747)
at
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:593)
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:3572)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3152)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3138)
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:616)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
[jira] [Updated] (CLOUDSTACK-5869) [Hyper-V] System VM creation on local storage is failing
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh updated CLOUDSTACK-5869:
--
Fix Version/s: 4.3.0
[Hyper-V] System VM creation on local storage is failing
Key: CLOUDSTACK-5869
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5869
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Affects Versions: 4.3.0
Reporter: Devdeep Singh
Assignee: Devdeep Singh
Priority: Blocker
Labels: hyper-V,
Fix For: 4.3.0
System vms are not getting deployed on a Hyper-V setup. It fails with the
following stack trace
2014-01-14 13:29:57,627 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-162:ctx-59574cc6) POST response
is[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.,newData:null,contextMap:{}}}]
2014-01-14 13:29:57,628 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-162:ctx-59574cc6) executeRequest received response
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from \u0027UncPath\u0027 on
\u0027HypervResource.PrimaryDataStoreTO\u0027.,contextMap:{},wait:0}}]
2014-01-14 13:29:57,628 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-162:ctx-59574cc6) Seq 5-374407591: Response Received:
2014-01-14 13:29:57,628 DEBUG [c.c.a.t.Request]
(DirectAgent-162:ctx-59574cc6) Seq 5-374407591: Processing: { Ans: , MgmtId:
280320865129348, via: 5, Ver: v1, Flags: 10,
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:org.apache.cloudstack.storage.command.CopyCommand
failed on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.,wait:0}}] }
2014-01-14 13:29:57,628 DEBUG [c.c.a.t.Request] (Job-Executor-41:ctx-20d66cbd
ctx-b360b710) Seq 5-374407591: Received: { Ans: , MgmtId: 280320865129348,
via: 5, Ver: v1, Flags: 10,
{ CopyCmdAnswer }
}
2014-01-14 13:29:57,633 WARN [o.a.c.s.d.ObjectInDataStoreManagerImpl]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unsupported data object (VOLUME,
org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@5bf2f643), no
need to delete from object in store ref table
2014-01-14 13:29:57,633 DEBUG [o.a.c.e.o.VolumeOrchestrator]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unable to create
Vol[23|vm=20|ROOT]:org.apache.cloudstack.storage.command.CopyCommand failed
on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.
2014-01-14 13:29:57,633 INFO [c.c.v.VirtualMachineManagerImpl]
(Job-Executor-41:ctx-20d66cbd ctx-b360b710) Unable to contact resource.
com.cloud.exception.StorageUnavailableException: Resource [StoragePool:3] is
unreachable: Unable to create
Vol[23|vm=20|ROOT]:org.apache.cloudstack.storage.command.CopyCommand failed
on exception, Error getting value from 'UncPath' on
'HypervResource.PrimaryDataStoreTO'.
at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.recreateVolume(VolumeOrchestrator.java:1174)
at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.prepare(VolumeOrchestrator.java:1216)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:944)
at
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:747)
at
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:593)
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:3572)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3152)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3138)
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:616)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
[jira] [Updated] (CLOUDSTACK-5868) Default templates are still referring to older templates in DB
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-5868: - Summary: Default templates are still referring to older templates in DB (was: Default templates are still referring to 32 bit templates in DB) Default templates are still referring to older templates in DB -- Key: CLOUDSTACK-5868 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5868 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Template Affects Versions: 4.3.0 Environment: All HVs Reporter: Sudha Ponnaganti Assignee: Sateesh Chodapuneedi Priority: Blocker Fix For: 4.3.0 Default template location is referring to older templates. Need to switch to 4.3 ++---+--+++-+ | id | name | bits | url | type | hypervisor_type | ++---+--+++-+ | 1 | SystemVM Template (XenServer) | 32 | http://download.cloud.com/templates/4.2/systemvmtemplate-2013-07-12-master-xen.vhd.bz2 | SYSTEM | XenServer | | 8 | SystemVM Template (vSphere) | 32 | http://download.cloud.com/templates/4.2/systemvmtemplate-4.2-vh7.ova | SYSTEM | VMware | ++---+--+++-+ -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5870) API support for retrieving UserData
Alena Prokharchyk created CLOUDSTACK-5870: - Summary: API support for retrieving UserData Key: CLOUDSTACK-5870 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5870 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.3.0 Reporter: Alena Prokharchyk Assignee: Alena Prokharchyk Fix For: 4.4.0 Current UserData behavior: * userData is passed to the deployVm/updateVm call * its stored in CS db and on the VR * the only one way to retrieve the data, is to request it from the user vm inside the network by sending http request to the Virtual Router. We've adopted this model from Amazon EC2 APIs. But along the way I've noticed that some third party integrators needed to read UserData by Admin to get the information about all vms in the system/network. To solve the problem, people were using different kinds of workarounds - db scripts to read userData from cloudstack DB, or writing CS API extensions: https://github.com/jasonhancock/cloudstack-api-extension. So the API I'm proposing, will let you to retrieve User Data via Web API. API will be available to admin as well as end user. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5871) Value of cpuallocated is twice the expected value
Nitin Mehta created CLOUDSTACK-5871: --- Summary: Value of cpuallocated is twice the expected value Key: CLOUDSTACK-5871 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5871 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.2.1 Reporter: Nitin Mehta 1. Create a few VMs in a 4.2.1 env 2. Spin up the VMs 3. Power down the VMs 4. Check the CPU allocated information. listhosts shows twice the value in cpuallocated field in the api as well as GUI. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Assigned] (CLOUDSTACK-5023) Deleting Port Forwarding Rule fails when generating usage events are enabled
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Grizzanti reassigned CLOUDSTACK-5023:
---
Assignee: David Grizzanti
Deleting Port Forwarding Rule fails when generating usage events are enabled
Key: CLOUDSTACK-5023
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5023
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Affects Versions: 4.2.0
Reporter: David Grizzanti
Assignee: David Grizzanti
Fix For: 4.1.1, Future
When generating usage events are enabled (using RabbitMQEventBus bean
configuration), deleting a port forwarding rule fails to delete the rule.
What you see as a response from the API call is:
{ queryasyncjobresultresponse :
{accountid:3f91b297-26e4-11e3-96f6-9e300504069a,userid:3f91e743-26e4-11e3-96f6-9e300504069a,cmd:org.apache.cloudstack.api.command.user.firewall.DeletePortForwardingRuleCmd,jobstatus:2,jobprocstatus:0,jobresultcode:530,jobresulttype:object,jobresult:{errorcode:530,errortext:Command
failed due to Internal Server
Error},created:2013-11-01T11:31:02-0400,jobid:a82a2ecb-2bcd-4f86-9d40-c4c9f0d85f6f}
}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5023) Deleting Port Forwarding Rule fails when generating usage events are enabled
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Grizzanti updated CLOUDSTACK-5023:
Assignee: (was: David Grizzanti)
Deleting Port Forwarding Rule fails when generating usage events are enabled
Key: CLOUDSTACK-5023
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5023
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Affects Versions: 4.2.0
Reporter: David Grizzanti
Fix For: 4.1.1, Future
When generating usage events are enabled (using RabbitMQEventBus bean
configuration), deleting a port forwarding rule fails to delete the rule.
What you see as a response from the API call is:
{ queryasyncjobresultresponse :
{accountid:3f91b297-26e4-11e3-96f6-9e300504069a,userid:3f91e743-26e4-11e3-96f6-9e300504069a,cmd:org.apache.cloudstack.api.command.user.firewall.DeletePortForwardingRuleCmd,jobstatus:2,jobprocstatus:0,jobresultcode:530,jobresulttype:object,jobresult:{errorcode:530,errortext:Command
failed due to Internal Server
Error},created:2013-11-01T11:31:02-0400,jobid:a82a2ecb-2bcd-4f86-9d40-c4c9f0d85f6f}
}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5872) Async response from addAccountToProject doesn't contain useful information
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Jones updated CLOUDSTACK-5872: --- Attachment: unnamed.patch A patch that modifies these responses to include a resource description. Async response from addAccountToProject doesn't contain useful information -- Key: CLOUDSTACK-5872 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5872 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Affects Versions: 4.2.0 Reporter: Bill Jones Fix For: 4.4.0 Attachments: unnamed.patch The async response from addAccountToProject doesn't contain useful information. Generally async responses for commands that modify resources include the resource ID and/or description in the async response. This is not true of addAccountToProject or deleteAccountFromProject. Consequently the response is not so useful to clients that do not have access to the context of the request. Also, it seems inconsistent with the general design of the API. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Comment Edited] (CLOUDSTACK-5872) Async response from addAccountToProject doesn't contain useful information
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871102#comment-13871102 ] Bill Jones edited comment on CLOUDSTACK-5872 at 1/14/14 8:25 PM: - A patch (against master) that modifies these responses to include a resource description. was (Author: sungardbill): A patch that modifies these responses to include a resource description. Async response from addAccountToProject doesn't contain useful information -- Key: CLOUDSTACK-5872 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5872 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Reporter: Bill Jones Fix For: 4.4.0 Attachments: unnamed.patch The async response from addAccountToProject doesn't contain useful information. Generally async responses for commands that modify resources include the resource ID and/or description in the async response. This is not true of addAccountToProject or deleteAccountFromProject. Consequently the response is not so useful to clients that do not have access to the context of the request. Also, it seems inconsistent with the general design of the API. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5873) [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rayees Namathponnan updated CLOUDSTACK-5873:
Description:
Regression automation failure
test_stopped_vm.py:test_04_deploy_startvm_false_attach_volume
Steps to reproduce
Validate the following:
1. deploy Vm with the startvm=false. Attach volume to the instance
2. listVM command should return the deployed VM.State of this VM should be
Stopped.
3. Attach volume should be successful
Attach volume failed with NPE
2014-01-08 18:58:19,204 INFO [c.c.s.VolumeApiServiceImpl]
(Job-Executor-84:ctx-b175478d ctx-1c48338d) Trying to attaching volume 60 to vm
instance:44, update async job-265 progress status
2014-01-08 18:58:19,204 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-84:ctx-b175478d ctx-1c48338d) Update async-job attachment,
job-265, instanceType: volume, instanceId: 60
2014-01-08 18:58:19,218 ERROR [c.c.a.ApiAsyncJobDispatcher]
(Job-Executor-84:ctx-b175478d) Unexpected exception while executing
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
java.lang.NullPointerException
at
com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:1964)
at
com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1304)
at
com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1129)
at
com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1104)
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:616)
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 $Proxy195.attachVolumeToVM(Unknown Source)
at
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:123)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
at
com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109)
at com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66)
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.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:524)
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$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-01-08 18:58:19,219 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-84:ctx-b175478d) Complete async job-265, jobStatus: FAILED,
resultCode: 530, result:
org.apache.cloudstack.api.response.ExceptionResponse/null/
{uuidList:[],errorcode:530}
2014-01-08 18:58:19,232 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-84:ctx-b175478d) Done executing
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for job-265
2014-01-08 18:58:19,236 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(Job-Executor-84:ctx-b175478d) Remove job-265 from job monitoring
2014-01-08 18:58:20,597 DEBUG [c.c.a.ApiServlet]
[jira] [Created] (CLOUDSTACK-5873) [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false
Rayees Namathponnan created CLOUDSTACK-5873: --- Summary: [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false Key: CLOUDSTACK-5873 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5873 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server, Volumes Affects Versions: 4.3.0 Environment: KVM Build RHEL 6.3 Reporter: Rayees Namathponnan Priority: Critical Fix For: 4.3.0 Regression automation failure test_stopped_vm.py:test_04_deploy_startvm_false_attach_volume Steps to reproduce Validate the following: 1. deploy Vm with the startvm=false. Attach volume to the instance 2. listVM command should return the deployed VM.State of this VM should be Stopped. 3. Attach volume should be successful Attach volume failed with NPE 2014-01-08 18:58:19,204 INFO [c.c.s.VolumeApiServiceImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Trying to attaching volume 60 to vm instance:44, update async job-265 progress status 2014-01-08 18:58:19,204 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Update async-job attachment, job-265, instanceType: volume, instanceId: 60 2014-01-08 18:58:19,218 ERROR [c.c.a.ApiAsyncJobDispatcher] (Job-Executor-84:ctx-b175478d) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd java.lang.NullPointerException at com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:1964) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1304) at com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1129) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1104) 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:616) 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 $Proxy195.attachVolumeToVM(Unknown Source) at org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:123) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161) at com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109) at com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66) 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.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:524) 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$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) 2014-01-08 18:58:19,219 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Job-Executor-84:ctx-b175478d) Complete async job-265, jobStatus: FAILED, resultCode: 530, result:
[jira] [Updated] (CLOUDSTACK-5872) Async response from addAccountToProject doesn't contain useful information
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Jones updated CLOUDSTACK-5872: --- Affects Version/s: (was: 4.2.0) Async response from addAccountToProject doesn't contain useful information -- Key: CLOUDSTACK-5872 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5872 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Reporter: Bill Jones Fix For: 4.4.0 Attachments: unnamed.patch The async response from addAccountToProject doesn't contain useful information. Generally async responses for commands that modify resources include the resource ID and/or description in the async response. This is not true of addAccountToProject or deleteAccountFromProject. Consequently the response is not so useful to clients that do not have access to the context of the request. Also, it seems inconsistent with the general design of the API. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5873) [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan updated CLOUDSTACK-5873: Attachment: Regression_basic_KVM.rar [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false -- Key: CLOUDSTACK-5873 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5873 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, Volumes Affects Versions: 4.3.0 Environment: KVM Build RHEL 6.3 Reporter: Rayees Namathponnan Priority: Critical Fix For: 4.3.0 Attachments: Regression_basic_KVM.rar Regression automation failure test_stopped_vm.py:test_04_deploy_startvm_false_attach_volume Steps to reproduce Validate the following: 1. deploy Vm with the startvm=false. Attach volume to the instance 2. listVM command should return the deployed VM.State of this VM should be Stopped. 3. Attach volume should be successful Attach volume failed with NPE 2014-01-08 18:58:19,204 INFO [c.c.s.VolumeApiServiceImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Trying to attaching volume 60 to vm instance:44, update async job-265 progress status 2014-01-08 18:58:19,204 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Update async-job attachment, job-265, instanceType: volume, instanceId: 60 2014-01-08 18:58:19,218 ERROR [c.c.a.ApiAsyncJobDispatcher] (Job-Executor-84:ctx-b175478d) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd java.lang.NullPointerException at com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:1964) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1304) at com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1129) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1104) 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:616) 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 $Proxy195.attachVolumeToVM(Unknown Source) at org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:123) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161) at com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109) at com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66) 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.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:524) 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$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at
[jira] [Commented] (CLOUDSTACK-5873) [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871115#comment-13871115 ] Rayees Namathponnan commented on CLOUDSTACK-5873: - Mike can you please check is regressed while fixing ? https://issues.apache.org/jira/browse/CLOUDSTACK-4810 [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false -- Key: CLOUDSTACK-5873 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5873 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, Volumes Affects Versions: 4.3.0 Environment: KVM Build RHEL 6.3 Reporter: Rayees Namathponnan Priority: Critical Fix For: 4.3.0 Attachments: Regression_basic_KVM.rar Regression automation failure test_stopped_vm.py:test_04_deploy_startvm_false_attach_volume Steps to reproduce Validate the following: 1. deploy Vm with the startvm=false. Attach volume to the instance 2. listVM command should return the deployed VM.State of this VM should be Stopped. 3. Attach volume should be successful Attach volume failed with NPE 2014-01-08 18:58:19,204 INFO [c.c.s.VolumeApiServiceImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Trying to attaching volume 60 to vm instance:44, update async job-265 progress status 2014-01-08 18:58:19,204 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Update async-job attachment, job-265, instanceType: volume, instanceId: 60 2014-01-08 18:58:19,218 ERROR [c.c.a.ApiAsyncJobDispatcher] (Job-Executor-84:ctx-b175478d) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd java.lang.NullPointerException at com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:1964) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1304) at com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1129) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1104) 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:616) 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 $Proxy195.attachVolumeToVM(Unknown Source) at org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:123) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161) at com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109) at com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66) 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.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:524) 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
[jira] [Commented] (CLOUDSTACK-5557) [UI] Invalid UI for Network-Guest Network-AnyVPCN/w.Able to see all configuration(FW/PF/LB)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871251#comment-13871251 ] Jessica Wang commented on CLOUDSTACK-5557: -- Author: Jessica Wang jessicaw...@apache.org#mailto:jessicaw...@apache.org Author date:2 hours ago (Tue Jan 14 10:54:49 2014) Commit date:2 hours ago (Tue Jan 14 10:56:06 2014) Commit hash:6282e8e9ca8906952b9d710ad1e439c965e0a0b0 CLOUDSTACK-5557: UI Network VPC Router Public IP Address fix a bug that Configuration tab was wrongly hidden. Contained in branches: master Contained in no tag [UI] Invalid UI for Network-Guest Network-AnyVPCN/w.Able to see all configuration(FW/PF/LB) --- Key: CLOUDSTACK-5557 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5557 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: manasaveloori Assignee: Jessica Wang Priority: Critical Fix For: 4.3.0 Attachments: VPCTierNW.jpg, management-server.log Steps: 1. Create a VPC. 2. Create a tier network and VM using that network. 3. Acquire IP and enable PF/LB rule. Obseravation: Under Network-GuestNetworks-Click on VPC tier network-IPaddresses. Able to view the IP address and all the configurable items in UI(firewall,PF,LB)like for normal networks. Also user is allowed to configure the rules which results in exception Attaching the SC -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5874) Cannot delete events for deleted accounts
Francois Gaudreault created CLOUDSTACK-5874: --- Summary: Cannot delete events for deleted accounts Key: CLOUDSTACK-5874 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5874 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Reporter: Francois Gaudreault Priority: Minor If there are events for a deleted account, you cannot remove them. I see this error in the logs : 530 Unable to delete Events, one or more parameters has invalid values To reproduce: - Create an account - Generate an event using this account - Delete the account - Try to delete the event. It will fail with 530 Unable to delete Events, one or more parameters has invalid values When you delete an account, it should either ask if you want to delete/archive events or just allow deleting the events regardless. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5777) Contrail:MS: Rebooting Xen host results in disconnected SR
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871269#comment-13871269 ] Anirban Chakraborty commented on CLOUDSTACK-5777: - This issue was not seen with CS4.3 and contrail bits. All the SRs are accessible after xen server reboot. Please verify. Contrail:MS: Rebooting Xen host results in disconnected SR -- Key: CLOUDSTACK-5777 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5777 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Contrail, XenServer Affects Versions: 4.2.0 Environment: Contrail, Xen 6.1 Reporter: Parth Jagirdar Reboot a host and SR results in disconnected state. This was also observed after installing Contrail RPM's on Xen host. Admin can manually repair SR from Xen-center. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5874) Cannot delete events for deleted accounts
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francois Gaudreault updated CLOUDSTACK-5874: Affects Version/s: (was: 4.2.0) 4.2.1 Cannot delete events for deleted accounts - Key: CLOUDSTACK-5874 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5874 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.1 Reporter: Francois Gaudreault Priority: Minor If there are events for a deleted account, you cannot remove them. I see this error in the logs : 530 Unable to delete Events, one or more parameters has invalid values To reproduce: - Create an account - Generate an event using this account - Delete the account - Try to delete the event. It will fail with 530 Unable to delete Events, one or more parameters has invalid values When you delete an account, it should either ask if you want to delete/archive events or just allow deleting the events regardless. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5809) Not able to deploy Vm becasue of crossing pool.storage.allocate d.capacity.disablethreshold even though the threshold has not been reached in the primary store.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871299#comment-13871299 ] Sangeetha Hariharan commented on CLOUDSTACK-5809: - There is another use case where we are not allowed to deploy Vms because of Maximum number of resources of type 'primary_storage' for account name=test-TestParallelVolumeSnasohots-M2LYLO in domain id=1 has been exceeded. Set up - Advanced zone set up with 2 Xenserver hosts. The default value for 'primary_storage' is 200 gb for account. I tried to deploy 11 user Vms using the default CentOS 5.6 template which has virtual size = 20 GB and actual size=1.7 G. Only 10 Vms get deployed. When I try to deploy another VM it fails because of Maximum number of resources of type 'primary_storage' for account name=test-TestParallelVolumeSnasohots-M2LYLO in domain id=1 has been exceeded. mysql select * from resource_count where account_id=3 - ; +++---+---+--+ | id | account_id | domain_id | type | count| +++---+---+--+ | 41 | 3 | NULL | user_vm | 10 | | 42 | 3 | NULL | public_ip | 11 | | 43 | 3 | NULL | volume| 10 | | 44 | 3 | NULL | snapshot |0 | | 45 | 3 | NULL | template |0 | | 46 | 3 | NULL | project |0 | | 47 | 3 | NULL | network |1 | | 48 | 3 | NULL | vpc |0 | | 49 | 3 | NULL | cpu | 10 | | 50 | 3 | NULL | memory| 1280 | | 51 | 3 | NULL | primary_storage | 214748364800 | | 52 | 3 | NULL | secondary_storage |0 | +++---+---+--+ 12 rows in set (0.00 sec) Actual Space taken up on the primary: [root@Rack3Host5 primary]# ls -lth total 4.4G -rw-r--r--. 1 root root 119M Jan 14 21:30 af626686-9040-44f4-8c41-85d7e51407c9.vhd -rw-r--r--. 1 root root 192M Jan 14 21:30 f6a2debe-2989-497b-9cfd-801687d45df6.vhd -rw-r--r--. 1 root root 195M Jan 14 21:30 7641171e-0b2b-437b-b4c0-912f6230f45c.vhd -rw-r--r--. 1 root root 115M Jan 14 21:30 882d7487-af73-4bd1-93f4-28bd0ce8b053.vhd -rw-r--r--. 1 root root 119M Jan 14 21:30 330936b3-a0e7-42bc-91ee-d90e4caa0bf5.vhd -rw-r--r--. 1 root root 11 Jan 14 21:30 hb-78964203-a98f-4359-ac6c-923241ed838a -rw-r--r--. 1 root root 119M Jan 14 21:30 7f2aa352-3535-4504-a75c-3392b380fef0.vhd -rw-r--r--. 1 root root 115M Jan 14 21:30 a588f9ec-8f9c-4ff4-8c5a-fe426c041f74.vhd -rw-r--r--. 1 root root 119M Jan 14 21:30 0aa24cbb-7565-4d61-be1d-ca9dbb5e48f2.vhd -rw-r--r--. 1 root root 11 Jan 14 21:30 hb-419fed86-8a7f-4a2a-9d29-cae55fa9232d -rw-r--r--. 1 root root 119M Jan 14 21:30 92f7aef7-2f69-43cf-8fb1-447a630c381b.vhd -rw-r--r--. 1 root root 118M Jan 14 21:30 bcc373e4-df48-41b4-99e6-1a50da63019d.vhd -rw-r--r--. 1 root root 119M Jan 14 21:30 2acdb609-a6b4-4997-84a8-f9664c0377ad.vhd -rw-r--r--. 1 root root 121M Jan 14 21:30 b4ee0eaa-78e0-473c-8642-acf8a64aa267.vhd -rw-r--r--. 1 root root 93M Jan 14 21:30 c26d3c46-80d1-4284-b23e-911939f0431e.vhd -rw-r--r--. 1 root root 46K Jan 14 20:53 a36b2afa-a588-43f6-9bd6-62f665a27397.vhd -rw-r--r--. 1 root root 7.3K Jan 14 20:53 filelog.txt -rw-r--r--. 1 root root 1.7G Jan 14 20:48 63959b05-1e9b-41b5-a7a8-7ad691ce706a.vhd -rw-r--r--. 1 root root 9.5K Jan 14 20:46 3b872148-72f9-4426-8faa-b38c1fbaac8c.vhd -rw-r--r--. 1 root root 2.5G Jan 14 19:38 8226938d-a816-47c1-8545-cae1f8a9ccba.vhd Not able to deploy Vm becasue of crossing pool.storage.allocate d.capacity.disablethreshold even though the threshold has not been reached in the primary store. Key: CLOUDSTACK-5809 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5809 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: Build from 4.3 Reporter: Sangeetha Hariharan Fix For: 4.3.0 Not able to deploy Vm because of crossing pool.storage.allocate d.capacity.disablethreshold even though the threshold has not been reached in the primary store. Steps to reproduce the problem: Xenserver set up with 2 Xensserver hosts: In my case , Primary storage NFS has 222GB . (storage.overprovisioning.factor is set to 2). I tried to deploy 20 Vms
[jira] [Updated] (CLOUDSTACK-5873) [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Animesh Chaturvedi updated CLOUDSTACK-5873: --- Assignee: Mike Tutkowski [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false -- Key: CLOUDSTACK-5873 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5873 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, Volumes Affects Versions: 4.3.0 Environment: KVM Build RHEL 6.3 Reporter: Rayees Namathponnan Assignee: Mike Tutkowski Priority: Critical Fix For: 4.3.0 Attachments: Regression_basic_KVM.rar Regression automation failure test_stopped_vm.py:test_04_deploy_startvm_false_attach_volume Steps to reproduce Validate the following: 1. deploy Vm with the startvm=false. Attach volume to the instance 2. listVM command should return the deployed VM.State of this VM should be Stopped. 3. Attach volume should be successful Attach volume failed with NPE 2014-01-08 18:58:19,204 INFO [c.c.s.VolumeApiServiceImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Trying to attaching volume 60 to vm instance:44, update async job-265 progress status 2014-01-08 18:58:19,204 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Update async-job attachment, job-265, instanceType: volume, instanceId: 60 2014-01-08 18:58:19,218 ERROR [c.c.a.ApiAsyncJobDispatcher] (Job-Executor-84:ctx-b175478d) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd java.lang.NullPointerException at com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:1964) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1304) at com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1129) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1104) 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:616) 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 $Proxy195.attachVolumeToVM(Unknown Source) at org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:123) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161) at com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109) at com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66) 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.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:524) 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$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at
[jira] [Commented] (CLOUDSTACK-5873) [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871369#comment-13871369 ] Animesh Chaturvedi commented on CLOUDSTACK-5873: Mike can you check on this [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false -- Key: CLOUDSTACK-5873 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5873 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, Volumes Affects Versions: 4.3.0 Environment: KVM Build RHEL 6.3 Reporter: Rayees Namathponnan Assignee: Mike Tutkowski Priority: Critical Fix For: 4.3.0 Attachments: Regression_basic_KVM.rar Regression automation failure test_stopped_vm.py:test_04_deploy_startvm_false_attach_volume Steps to reproduce Validate the following: 1. deploy Vm with the startvm=false. Attach volume to the instance 2. listVM command should return the deployed VM.State of this VM should be Stopped. 3. Attach volume should be successful Attach volume failed with NPE 2014-01-08 18:58:19,204 INFO [c.c.s.VolumeApiServiceImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Trying to attaching volume 60 to vm instance:44, update async job-265 progress status 2014-01-08 18:58:19,204 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Update async-job attachment, job-265, instanceType: volume, instanceId: 60 2014-01-08 18:58:19,218 ERROR [c.c.a.ApiAsyncJobDispatcher] (Job-Executor-84:ctx-b175478d) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd java.lang.NullPointerException at com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:1964) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1304) at com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1129) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1104) 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:616) 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 $Proxy195.attachVolumeToVM(Unknown Source) at org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:123) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161) at com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109) at com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66) 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.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:524) 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$Sync.innerRun(FutureTask.java:334) at
[jira] [Resolved] (CLOUDSTACK-5747) [Upgrade]Network restart failed after upgarding from 2.2.16 to 4.3 with External Firewall SRX added to CS.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Animesh Chaturvedi resolved CLOUDSTACK-5747. Resolution: Fixed [Upgrade]Network restart failed after upgarding from 2.2.16 to 4.3 with External Firewall SRX added to CS. -- Key: CLOUDSTACK-5747 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5747 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller, Network Devices, Upgrade Affects Versions: 4.3.0 Environment: upgraded the CS2.2.16 with SRX to 4.3 Reporter: manasaveloori Assignee: Jayapal Reddy Fix For: 4.3.0 Attachments: management-server.log.rar, mysqldump2216.dmp, mysqldump4.3.dmp Steps: 1. Deploy CS 2.2 X.16 using Xen5.6 sp2 HV. 2. Add the External firewall SRX to CS. 3. Set the GC parameter firewall.rule.ui.enabled to true. 4. Now acquire the IP and configure firewall and PF rules. 5. Upgrade the CS to 4.3. 6. Stop and start all the System VMs and router VMs so that the new template is upgraded. 7. Now perform Network restart on which the firwall and PF rules are configured. Observation : Observed the follwoing exceptions in Ms logs and Network restart failed. 2014-01-03 17:43:32,329 DEBUG [c.c.n.r.JuniperSrxResource] (DirectAgent-76:ctx-2128a4a2) Added Egress firewall rule for guest network 965 2014-01-03 17:43:32,329 DEBUG [c.c.n.r.JuniperSrxResource] (DirectAgent-76:ctx-2128a4a2) Sending request: !--Licensed to the Apache Software Foundation (ASF) under oneor more contributor license agreements. See the NOTICE filedistributed with this work for additional informationregarding copyright ownership. The ASF licenses this fileto you under the Apache License, Version 2.0 (theLicense); you may not use this file except in compliancewith the License. You may obtain a copy of the License athttp://www.apache.org/licenses/LICENSE-2.0Unless required by applicable law or agreed to in writing,software distributed under the License is distributed on anAS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANYKIND, either express or implied. See the License for thespecific language governing permissions and limitationsunder the License.--rpccommit-configuration/commit-configuration/rpc 2014-01-03 17:43:33,966 DEBUG [c.c.n.r.JuniperSrxResource] (DirectAgent-76:ctx-2128a4a2) Checking response: rpc-reply xmlns:junos=http://xml.juniper.net/junos/10.4R6/junos;commit-resultsload-success/xnm:error xmlns=http://xml.juniper.net/xnm/1.1/xnm; xmlns:xnm=http://xml.juniper.net/xnm/1.1/xnm;source-daemonmgd/source-daemonedit-path[edit security policies from-zone trust to-zone untrust policy egress-trust-untrust-965]/edit-pathstatementmatch/statementmessageMissing mandatory statement: 'source-address'/message/xnm:errorxnm:error xmlns=http://xml.juniper.net/xnm/1.1/xnm; xmlns:xnm=http://xml.juniper.net/xnm/1.1/xnm;messagecommit failed: (missing statements)/message/xnm:error/commit-results/rpc-reply 2014-01-03 17:43:33,966 ERROR [c.c.n.r.JuniperSrxResource] (DirectAgent-76:ctx-2128a4a2) Request failed due to: Missing mandatory statement: 'source-address' 2014-01-03 17:43:33,967 ERROR [c.c.n.r.JuniperSrxResource] (DirectAgent-76:ctx-2128a4a2) com.cloud.utils.exception.ExecutionException: Failed to commit to global configuration. 2014-01-03 17:43:33,967 DEBUG [c.c.n.r.JuniperSrxResource] (DirectAgent-76:ctx-2128a4a2) Sending request: !--Licensed to the Apache Software Foundation (ASF) under oneor more contributor license agreements. See the NOTICE filedistributed with this work for additional informationregarding copyright ownership. The ASF licenses this fileto you under the Apache License, Version 2.0 (theLicense); you may not use this file except in compliancewith the License. You may obtain a copy of the License athttp://www.apache.org/licenses/LICENSE-2.0Unless required by applicable law or agreed to in writing,software distributed under the License is distributed on anAS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANYKIND, either express or implied. See the License for thespecific language governing permissions and limitationsunder the License.--rpcclose-configuration//rpc 2014-01-03 17:43:34,012 DEBUG [c.c.n.r.JuniperSrxResource] (DirectAgent-76:ctx-2128a4a2) Checking response: rpc-reply xmlns:junos=http://xml.juniper.net/junos/10.4R6/junos;/rpc-reply 2014-01-03 17:43:34,012 DEBUG [c.c.n.r.JuniperSrxResource] (DirectAgent-76:ctx-2128a4a2) Closed private configuration. 2014-01-03 17:43:34,013 DEBUG [c.c.a.m.DirectAgentAttache]
[jira] [Commented] (CLOUDSTACK-5873) [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871397#comment-13871397
]
Mike Tutkowski commented on CLOUDSTACK-5873:
Looking into this now.
The last instruction here throws a NPE:
HostVO host = null;
StoragePoolVO volumeToAttachStoragePool =
_storagePoolDao.findById(volumeToAttach.getPoolId());
if (hostId != null) {
host = _hostDao.findById(hostId);
if (host != null host.getHypervisorType() ==
HypervisorType.XenServer volumeToAttachStoragePool.isManaged()) {
sendCommand = true;
}
}
DataStore dataStore =
dataStoreMgr.getDataStore(volumeToAttachStoragePool.getId(),
DataStoreRole.Primary);
Off hand this seems strange b/c it would seem volumeToAttachStoragePool would
have to be null, which means volumeToAttach.getPoolId() would have to had
returned null.
By this point in execution, there should be a storage pool associated with the
volume to attach.
[Automation] Failed to attach volume to VM, if the vm is created with option
startvm=false
--
Key: CLOUDSTACK-5873
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5873
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server, Volumes
Affects Versions: 4.3.0
Environment: KVM
Build RHEL 6.3
Reporter: Rayees Namathponnan
Assignee: Mike Tutkowski
Priority: Critical
Fix For: 4.3.0
Attachments: Regression_basic_KVM.rar
Regression automation failure
test_stopped_vm.py:test_04_deploy_startvm_false_attach_volume
Steps to reproduce
Validate the following:
1. deploy Vm with the startvm=false. Attach volume to the instance
2. listVM command should return the deployed VM.State of this VM should be
Stopped.
3. Attach volume should be successful
Attach volume failed with NPE
2014-01-08 18:58:19,204 INFO [c.c.s.VolumeApiServiceImpl]
(Job-Executor-84:ctx-b175478d ctx-1c48338d) Trying to attaching volume 60 to
vm instance:44, update async job-265 progress status
2014-01-08 18:58:19,204 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-84:ctx-b175478d ctx-1c48338d) Update async-job attachment,
job-265, instanceType: volume, instanceId: 60
2014-01-08 18:58:19,218 ERROR [c.c.a.ApiAsyncJobDispatcher]
(Job-Executor-84:ctx-b175478d) Unexpected exception while executing
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
java.lang.NullPointerException
at
com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:1964)
at
com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1304)
at
com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1129)
at
com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1104)
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:616)
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 $Proxy195.attachVolumeToVM(Unknown Source)
at
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:123)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
at
com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109)
at com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66)
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.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63)
at
[jira] [Commented] (CLOUDSTACK-5873) [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871400#comment-13871400 ] Mike Tutkowski commented on CLOUDSTACK-5873: Can someone clarify this for me? deploy Vm with the startvm=false. Attach volume to the instance Is this something I can do via the GUI or do I have to use the CLI or my own way of submitting API calls to CS? Thanks! [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false -- Key: CLOUDSTACK-5873 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5873 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, Volumes Affects Versions: 4.3.0 Environment: KVM Build RHEL 6.3 Reporter: Rayees Namathponnan Assignee: Mike Tutkowski Priority: Critical Fix For: 4.3.0 Attachments: Regression_basic_KVM.rar Regression automation failure test_stopped_vm.py:test_04_deploy_startvm_false_attach_volume Steps to reproduce Validate the following: 1. deploy Vm with the startvm=false. Attach volume to the instance 2. listVM command should return the deployed VM.State of this VM should be Stopped. 3. Attach volume should be successful Attach volume failed with NPE 2014-01-08 18:58:19,204 INFO [c.c.s.VolumeApiServiceImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Trying to attaching volume 60 to vm instance:44, update async job-265 progress status 2014-01-08 18:58:19,204 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Update async-job attachment, job-265, instanceType: volume, instanceId: 60 2014-01-08 18:58:19,218 ERROR [c.c.a.ApiAsyncJobDispatcher] (Job-Executor-84:ctx-b175478d) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd java.lang.NullPointerException at com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:1964) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1304) at com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1129) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1104) 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:616) 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 $Proxy195.attachVolumeToVM(Unknown Source) at org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:123) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161) at com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109) at com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66) 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.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:524) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at
[jira] [Comment Edited] (CLOUDSTACK-5873) [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871397#comment-13871397
]
Mike Tutkowski edited comment on CLOUDSTACK-5873 at 1/14/14 11:55 PM:
--
Looking into this now.
The last instruction here throws a NPE:
HostVO host = null;
StoragePoolVO volumeToAttachStoragePool =
_storagePoolDao.findById(volumeToAttach.getPoolId());
if (hostId != null) {
host = _hostDao.findById(hostId);
if (host != null host.getHypervisorType() ==
HypervisorType.XenServer volumeToAttachStoragePool.isManaged()) {
sendCommand = true;
}
}
DataStore dataStore =
dataStoreMgr.getDataStore(volumeToAttachStoragePool.getId(),
DataStoreRole.Primary);
Off hand this seems strange b/c it would seem volumeToAttachStoragePool would
have to be null, which means volumeToAttach.getPoolId() would have to had
returned null (or the ID of a storage pool that doesn't exist).
By this point in execution, there should be a storage pool associated with the
volume to attach.
was (Author: mike-tutkowski):
Looking into this now.
The last instruction here throws a NPE:
HostVO host = null;
StoragePoolVO volumeToAttachStoragePool =
_storagePoolDao.findById(volumeToAttach.getPoolId());
if (hostId != null) {
host = _hostDao.findById(hostId);
if (host != null host.getHypervisorType() ==
HypervisorType.XenServer volumeToAttachStoragePool.isManaged()) {
sendCommand = true;
}
}
DataStore dataStore =
dataStoreMgr.getDataStore(volumeToAttachStoragePool.getId(),
DataStoreRole.Primary);
Off hand this seems strange b/c it would seem volumeToAttachStoragePool would
have to be null, which means volumeToAttach.getPoolId() would have to had
returned null.
By this point in execution, there should be a storage pool associated with the
volume to attach.
[Automation] Failed to attach volume to VM, if the vm is created with option
startvm=false
--
Key: CLOUDSTACK-5873
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5873
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server, Volumes
Affects Versions: 4.3.0
Environment: KVM
Build RHEL 6.3
Reporter: Rayees Namathponnan
Assignee: Mike Tutkowski
Priority: Critical
Fix For: 4.3.0
Attachments: Regression_basic_KVM.rar
Regression automation failure
test_stopped_vm.py:test_04_deploy_startvm_false_attach_volume
Steps to reproduce
Validate the following:
1. deploy Vm with the startvm=false. Attach volume to the instance
2. listVM command should return the deployed VM.State of this VM should be
Stopped.
3. Attach volume should be successful
Attach volume failed with NPE
2014-01-08 18:58:19,204 INFO [c.c.s.VolumeApiServiceImpl]
(Job-Executor-84:ctx-b175478d ctx-1c48338d) Trying to attaching volume 60 to
vm instance:44, update async job-265 progress status
2014-01-08 18:58:19,204 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-84:ctx-b175478d ctx-1c48338d) Update async-job attachment,
job-265, instanceType: volume, instanceId: 60
2014-01-08 18:58:19,218 ERROR [c.c.a.ApiAsyncJobDispatcher]
(Job-Executor-84:ctx-b175478d) Unexpected exception while executing
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
java.lang.NullPointerException
at
com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:1964)
at
com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1304)
at
com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1129)
at
com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1104)
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:616)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
at
[jira] [Comment Edited] (CLOUDSTACK-5873) [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871400#comment-13871400 ] Mike Tutkowski edited comment on CLOUDSTACK-5873 at 1/14/14 11:57 PM: -- Can someone clarify this for me? deploy Vm with the startvm=false. Is this something I can do via the GUI or do I have to use the CLI or my own way of submitting API calls to CS? Thanks! was (Author: mike-tutkowski): Can someone clarify this for me? deploy Vm with the startvm=false. Attach volume to the instance Is this something I can do via the GUI or do I have to use the CLI or my own way of submitting API calls to CS? Thanks! [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false -- Key: CLOUDSTACK-5873 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5873 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, Volumes Affects Versions: 4.3.0 Environment: KVM Build RHEL 6.3 Reporter: Rayees Namathponnan Assignee: Mike Tutkowski Priority: Critical Fix For: 4.3.0 Attachments: Regression_basic_KVM.rar Regression automation failure test_stopped_vm.py:test_04_deploy_startvm_false_attach_volume Steps to reproduce Validate the following: 1. deploy Vm with the startvm=false. Attach volume to the instance 2. listVM command should return the deployed VM.State of this VM should be Stopped. 3. Attach volume should be successful Attach volume failed with NPE 2014-01-08 18:58:19,204 INFO [c.c.s.VolumeApiServiceImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Trying to attaching volume 60 to vm instance:44, update async job-265 progress status 2014-01-08 18:58:19,204 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Update async-job attachment, job-265, instanceType: volume, instanceId: 60 2014-01-08 18:58:19,218 ERROR [c.c.a.ApiAsyncJobDispatcher] (Job-Executor-84:ctx-b175478d) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd java.lang.NullPointerException at com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:1964) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1304) at com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1129) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1104) 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:616) 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 $Proxy195.attachVolumeToVM(Unknown Source) at org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:123) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161) at com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109) at com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66) 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.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:524) 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] [Commented] (CLOUDSTACK-5873) [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871415#comment-13871415 ] Rayees Namathponnan commented on CLOUDSTACK-5873: - its cannot be execute from UI; you need to submit API call If you have automation environment, then you can try from there test/component/integration/test_stopped_vm.py:test_04_deploy_startvm_false_attach_volume [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false -- Key: CLOUDSTACK-5873 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5873 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, Volumes Affects Versions: 4.3.0 Environment: KVM Build RHEL 6.3 Reporter: Rayees Namathponnan Assignee: Mike Tutkowski Priority: Critical Fix For: 4.3.0 Attachments: Regression_basic_KVM.rar Regression automation failure test_stopped_vm.py:test_04_deploy_startvm_false_attach_volume Steps to reproduce Validate the following: 1. deploy Vm with the startvm=false. Attach volume to the instance 2. listVM command should return the deployed VM.State of this VM should be Stopped. 3. Attach volume should be successful Attach volume failed with NPE 2014-01-08 18:58:19,204 INFO [c.c.s.VolumeApiServiceImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Trying to attaching volume 60 to vm instance:44, update async job-265 progress status 2014-01-08 18:58:19,204 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Update async-job attachment, job-265, instanceType: volume, instanceId: 60 2014-01-08 18:58:19,218 ERROR [c.c.a.ApiAsyncJobDispatcher] (Job-Executor-84:ctx-b175478d) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd java.lang.NullPointerException at com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:1964) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1304) at com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1129) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1104) 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:616) 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 $Proxy195.attachVolumeToVM(Unknown Source) at org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:123) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161) at com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109) at com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66) 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.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:524) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at
[jira] [Comment Edited] (CLOUDSTACK-5873) [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871414#comment-13871414 ] Mike Tutkowski edited comment on CLOUDSTACK-5873 at 1/15/14 12:12 AM: -- I think the trick here is that the VM was never in the started state (which means it was probably never assoicated with a host). I have an e-mail out to Marcus to ask him about this, but I suspect in this situation that such a volume might not be associated with a storage pool. If this is true, I can correct the problem by disallowing such an action for managed storage (which is why this new logic is in here), but allowing it for non-managed (regular) storage. was (Author: mike-tutkowski): I think the trick here is that the VM was never in the started state. I have an e-mail out to Marcus to ask him about this, but I suspect in this situation that such a volume might not be associated with a storage pool. If this is true, I can correct the problem by disallowing such an action for managed storage (which is why this new logic is in here), but allowing it for non-managed (regular) storage. [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false -- Key: CLOUDSTACK-5873 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5873 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, Volumes Affects Versions: 4.3.0 Environment: KVM Build RHEL 6.3 Reporter: Rayees Namathponnan Assignee: Mike Tutkowski Priority: Critical Fix For: 4.3.0 Attachments: Regression_basic_KVM.rar Regression automation failure test_stopped_vm.py:test_04_deploy_startvm_false_attach_volume Steps to reproduce Validate the following: 1. deploy Vm with the startvm=false. Attach volume to the instance 2. listVM command should return the deployed VM.State of this VM should be Stopped. 3. Attach volume should be successful Attach volume failed with NPE 2014-01-08 18:58:19,204 INFO [c.c.s.VolumeApiServiceImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Trying to attaching volume 60 to vm instance:44, update async job-265 progress status 2014-01-08 18:58:19,204 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Update async-job attachment, job-265, instanceType: volume, instanceId: 60 2014-01-08 18:58:19,218 ERROR [c.c.a.ApiAsyncJobDispatcher] (Job-Executor-84:ctx-b175478d) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd java.lang.NullPointerException at com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:1964) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1304) at com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1129) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1104) 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:616) 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 $Proxy195.attachVolumeToVM(Unknown Source) at org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:123) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161) at com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109) at com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66) 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
[jira] [Commented] (CLOUDSTACK-5873) [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871414#comment-13871414 ] Mike Tutkowski commented on CLOUDSTACK-5873: I think the trick here is that the VM was never in the started state. I have an e-mail out to Marcus to ask him about this, but I suspect in this situation that such a volume might not be associated with a storage pool. If this is true, I can correct the problem by disallowing such an action for managed storage (which is why this new logic is in here), but allowing it for non-managed (regular) storage. [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false -- Key: CLOUDSTACK-5873 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5873 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, Volumes Affects Versions: 4.3.0 Environment: KVM Build RHEL 6.3 Reporter: Rayees Namathponnan Assignee: Mike Tutkowski Priority: Critical Fix For: 4.3.0 Attachments: Regression_basic_KVM.rar Regression automation failure test_stopped_vm.py:test_04_deploy_startvm_false_attach_volume Steps to reproduce Validate the following: 1. deploy Vm with the startvm=false. Attach volume to the instance 2. listVM command should return the deployed VM.State of this VM should be Stopped. 3. Attach volume should be successful Attach volume failed with NPE 2014-01-08 18:58:19,204 INFO [c.c.s.VolumeApiServiceImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Trying to attaching volume 60 to vm instance:44, update async job-265 progress status 2014-01-08 18:58:19,204 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Update async-job attachment, job-265, instanceType: volume, instanceId: 60 2014-01-08 18:58:19,218 ERROR [c.c.a.ApiAsyncJobDispatcher] (Job-Executor-84:ctx-b175478d) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd java.lang.NullPointerException at com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:1964) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1304) at com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1129) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1104) 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:616) 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 $Proxy195.attachVolumeToVM(Unknown Source) at org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:123) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161) at com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109) at com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66) 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.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:524) 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
[jira] [Commented] (CLOUDSTACK-5342) [Automation] Add NIC to virtual machine fails in KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871422#comment-13871422
]
Rayees Namathponnan commented on CLOUDSTACK-5342:
-
Moving type bug to test, since we are going to fix in test
[Automation] Add NIC to virtual machine fails in KVM
Key: CLOUDSTACK-5342
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5342
Project: CloudStack
Issue Type: Test
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Network Controller
Affects Versions: 4.3.0
Environment: KVM advanced
Reporter: Gaurav Aradhye
Fix For: 4.3.0
Add network to VM test cases fail in KVM with following error.
Execute cmd: asyncquery failed, due to: {errorcode : 530, errortext :
u'Unable to add NIC to VM[User|VM-e9350ee5-bf2e-418c-91d6-1535dcb4d488]'}
The same test cases execute successfully on XenServer. As per the feature
specification (see
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Add+Remove+Networks+to+VMs),
Add network to VM feature should be supported on KVM too.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5342) [Automation] Add NIC to virtual machine fails in KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rayees Namathponnan updated CLOUDSTACK-5342:
Issue Type: Test (was: Bug)
[Automation] Add NIC to virtual machine fails in KVM
Key: CLOUDSTACK-5342
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5342
Project: CloudStack
Issue Type: Test
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Network Controller
Affects Versions: 4.3.0
Environment: KVM advanced
Reporter: Gaurav Aradhye
Fix For: 4.3.0
Add network to VM test cases fail in KVM with following error.
Execute cmd: asyncquery failed, due to: {errorcode : 530, errortext :
u'Unable to add NIC to VM[User|VM-e9350ee5-bf2e-418c-91d6-1535dcb4d488]'}
The same test cases execute successfully on XenServer. As per the feature
specification (see
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Add+Remove+Networks+to+VMs),
Add network to VM feature should be supported on KVM too.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5815) [Hyper-v] Two SNAT rules for one isolated network if acquired ip is from different vlan
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ram Ganesh updated CLOUDSTACK-5815:
---
Assignee: Rajesh Battala
[Hyper-v] Two SNAT rules for one isolated network if acquired ip is from
different vlan
---
Key: CLOUDSTACK-5815
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5815
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Hypervisor Controller, Network Controller
Affects Versions: 4.3.0
Environment: Latest build from 4.3 branch with
commit:6f309b8a87d3376950a60234d399c6e3749ad1c7
Reporter: Sanjeev N
Assignee: Rajesh Battala
Labels: hyper-V,, hyper-v, hyperv
Fix For: 4.3.0
[Hyper-v] Two SNAT rules for one isolated network if acquired ip is from
different vlan
Steps to Reproduce:
=
1.Bring up CS in advanced zone with hyper-v cluster
2.Create isolated guest network and deploy few vms in the network
3.Exhaust all the public IP addresses present in the zone (in user_ip_address
table set the allocated=now())
4.Add new public IP range in new vlan and new subnet
5.Acquire one ip address from the new ip range and configure PF and assign
one vm deployed at step2
Expected Result:
==
In isolated network there is only one SNAT ip address for the entire network.
So even the acquired IP address is from different vlan, new SNAT rule should
not be configured with the acquired ip address.
Actual Result:
Since the ip address acquired at step5 is from new vlan and is the ip address
from that vlan additional SNAT rule got configured on VR with the acquired ip
address.
Following is the output from iptables on VR:
root@r-4-VM:~# iptables -t nat -L -nv
Chain PREROUTING (policy ACCEPT 279 packets, 28169 bytes)
pkts bytes target prot opt in out source
destination
0 0 DNAT tcp -- eth2 * 0.0.0.0/0
10.147.31.240tcp dpt:22 to:10.1.1.26:22
0 0 DNAT tcp -- eth0 * 0.0.0.0/0
10.147.31.240tcp dpt:22 to:10.1.1.26:22
Chain INPUT (policy ACCEPT 4 packets, 240 bytes)
pkts bytes target prot opt in out source
destination
Chain OUTPUT (policy ACCEPT 4 packets, 304 bytes)
pkts bytes target prot opt in out source
destination
0 0 DNAT tcp -- * * 0.0.0.0/0
10.147.31.240tcp dpt:22 to:10.1.1.26:22
Chain POSTROUTING (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination
0 0 SNAT tcp -- * eth010.1.1.0/24 10.1.1.26
tcp dpt:22 to:10.1.1.1
4 304 SNAT all -- * eth20.0.0.0/00.0.0.0/0
to:10.147.48.5
0 0 SNAT all -- * eth20.0.0.0/00.0.0.0/0
to:10.147.31.240
ip address configuration on eth2 as follows:
root@r-4-VM:~# ip addr show eth2
4: eth2: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP
qlen 1000
link/ether 06:78:3c:00:00:17 brd ff:ff:ff:ff:ff:ff
inet 10.147.48.5/24 brd 10.147.48.255 scope global eth2
inet 10.147.31.240/24 brd 10.147.31.255 scope global eth2
inet6 fe80::478:3cff:fe00:17/64 scope link
valid_lft forever preferred_lft forever
Following is the IpAssocCmd got executed after configuring PF rule on the
acquired ip address:
2014-01-07 11:30:39,274 DEBUG [c.c.a.t.Request] (Job-Executor-31:ctx-26e587af
ctx-d423299a) Seq 4-2034961238: Sending { Cmd , MgmtId: 132129494109518,
via: 4(10.147.40.31), Ver: v1, Flags: 11,
[{com.cloud.agent.api.routing.IpAssocCommand:{ipAddresses:[{accountId:2,publicIp:10.147.48.5,sourceNat:true,add:true,oneToOneNat:false,firstIP:true,broadcastUri:vlan://48,vlanGateway:10.147.48.1,vlanNetmask:255.255.255.0,vifMacAddress:06:88:76:00:00:17,networkRate:200,trafficType:Public}],accessDetails:{router.guest.ip:10.1.1.1,zone.network.type:Advanced,router.ip:10.147.40.230,router.name:r-4-VM},wait:0}},{com.cloud.agent.api.routing.IpAssocCommand:{ipAddresses:[{accountId:2,publicIp:10.147.31.240,sourceNat:true,add:true,oneToOneNat:false,firstIP:true,broadcastUri:vlan://31,vlanGateway:10.147.31.1,vlanNetmask:255.255.255.0,vifMacAddress:06:78:3e:00:00:17,networkRate:200,trafficType:Public}],accessDetails:{router.guest.ip:10.1.1.1,zone.network.type:Advanced,router.ip:10.147.40.230,router.name:r-4-VM},wait:0}}]
}
2014-01-07 11:30:39,275 DEBUG [c.c.a.t.Request] (Job-Executor-31:ctx-26e587af
ctx-d423299a) Seq 4-2034961238: Executing:
[jira] [Commented] (CLOUDSTACK-5873) [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871478#comment-13871478 ] Mike Tutkowski commented on CLOUDSTACK-5873: I should have the fix in by tonight. [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false -- Key: CLOUDSTACK-5873 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5873 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, Volumes Affects Versions: 4.3.0 Environment: KVM Build RHEL 6.3 Reporter: Rayees Namathponnan Assignee: Mike Tutkowski Priority: Critical Fix For: 4.3.0 Attachments: Regression_basic_KVM.rar Regression automation failure test_stopped_vm.py:test_04_deploy_startvm_false_attach_volume Steps to reproduce Validate the following: 1. deploy Vm with the startvm=false. Attach volume to the instance 2. listVM command should return the deployed VM.State of this VM should be Stopped. 3. Attach volume should be successful Attach volume failed with NPE 2014-01-08 18:58:19,204 INFO [c.c.s.VolumeApiServiceImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Trying to attaching volume 60 to vm instance:44, update async job-265 progress status 2014-01-08 18:58:19,204 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Update async-job attachment, job-265, instanceType: volume, instanceId: 60 2014-01-08 18:58:19,218 ERROR [c.c.a.ApiAsyncJobDispatcher] (Job-Executor-84:ctx-b175478d) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd java.lang.NullPointerException at com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:1964) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1304) at com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1129) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1104) 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:616) 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 $Proxy195.attachVolumeToVM(Unknown Source) at org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:123) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161) at com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109) at com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66) 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.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:524) 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$Sync.innerRun(FutureTask.java:334) at
[jira] [Commented] (CLOUDSTACK-5873) [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871477#comment-13871477 ] Mike Tutkowski commented on CLOUDSTACK-5873: Just confirmed this: The problem is if you deploy a VM and make sure it has never been started. At this point, if you attach a data disk to it, the storage pool of the data disk will be null. My logic believed at this point in execution that the storage pool would be non-null and reference a legitimate storage pool. I will change the code to detect this state and throw an exception for CloudStack-managed storage (in that situation, you cannot attach a disk that depends on managed storage to a VM that has never been started) and for standard storage (which is what this JIRA ticket refers to) I will allow the action. [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false -- Key: CLOUDSTACK-5873 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5873 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, Volumes Affects Versions: 4.3.0 Environment: KVM Build RHEL 6.3 Reporter: Rayees Namathponnan Assignee: Mike Tutkowski Priority: Critical Fix For: 4.3.0 Attachments: Regression_basic_KVM.rar Regression automation failure test_stopped_vm.py:test_04_deploy_startvm_false_attach_volume Steps to reproduce Validate the following: 1. deploy Vm with the startvm=false. Attach volume to the instance 2. listVM command should return the deployed VM.State of this VM should be Stopped. 3. Attach volume should be successful Attach volume failed with NPE 2014-01-08 18:58:19,204 INFO [c.c.s.VolumeApiServiceImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Trying to attaching volume 60 to vm instance:44, update async job-265 progress status 2014-01-08 18:58:19,204 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Update async-job attachment, job-265, instanceType: volume, instanceId: 60 2014-01-08 18:58:19,218 ERROR [c.c.a.ApiAsyncJobDispatcher] (Job-Executor-84:ctx-b175478d) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd java.lang.NullPointerException at com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:1964) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1304) at com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1129) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1104) 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:616) 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 $Proxy195.attachVolumeToVM(Unknown Source) at org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:123) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161) at com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109) at com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66) 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.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:524) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at
[jira] [Comment Edited] (CLOUDSTACK-5873) [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871477#comment-13871477 ] Mike Tutkowski edited comment on CLOUDSTACK-5873 at 1/15/14 1:15 AM: - Just confirmed this: The problem is if you deploy a VM and make sure it has never been started. At this point, if you attach a data disk to it, the storage pool of the data disk will be null. My logic believed at this point in execution that the storage pool would be non-null and reference a legitimate storage pool. I will change the code to detect this state and throw an exception for CloudStack-managed storage (in that situation, you cannot attach a disk that depends on managed storage to a VM that has never been started before) and for standard storage (which is what this JIRA ticket refers to) I will allow the action. was (Author: mike-tutkowski): Just confirmed this: The problem is if you deploy a VM and make sure it has never been started. At this point, if you attach a data disk to it, the storage pool of the data disk will be null. My logic believed at this point in execution that the storage pool would be non-null and reference a legitimate storage pool. I will change the code to detect this state and throw an exception for CloudStack-managed storage (in that situation, you cannot attach a disk that depends on managed storage to a VM that has never been started) and for standard storage (which is what this JIRA ticket refers to) I will allow the action. [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false -- Key: CLOUDSTACK-5873 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5873 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, Volumes Affects Versions: 4.3.0 Environment: KVM Build RHEL 6.3 Reporter: Rayees Namathponnan Assignee: Mike Tutkowski Priority: Critical Fix For: 4.3.0 Attachments: Regression_basic_KVM.rar Regression automation failure test_stopped_vm.py:test_04_deploy_startvm_false_attach_volume Steps to reproduce Validate the following: 1. deploy Vm with the startvm=false. Attach volume to the instance 2. listVM command should return the deployed VM.State of this VM should be Stopped. 3. Attach volume should be successful Attach volume failed with NPE 2014-01-08 18:58:19,204 INFO [c.c.s.VolumeApiServiceImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Trying to attaching volume 60 to vm instance:44, update async job-265 progress status 2014-01-08 18:58:19,204 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Update async-job attachment, job-265, instanceType: volume, instanceId: 60 2014-01-08 18:58:19,218 ERROR [c.c.a.ApiAsyncJobDispatcher] (Job-Executor-84:ctx-b175478d) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd java.lang.NullPointerException at com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:1964) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1304) at com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1129) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1104) 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:616) 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 $Proxy195.attachVolumeToVM(Unknown Source) at org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:123) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161) at com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109) at
[jira] [Commented] (CLOUDSTACK-5408) [Automation] Failed to deploy vm in vmware environment with error due to java.io.IOException: Cannot run program mount: java.io.IOException: error=12, Cannot al
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871496#comment-13871496
]
ASF subversion and git services commented on CLOUDSTACK-5408:
-
Commit 032888c46ca70096423ff84b31ce5d99c12442b9 in branch refs/heads/4.3 from
[~sateeshc]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=032888c ]
CLOUDSTACK-5408 [Automation] Failed to deploy vm in vmware environment with
error due to java.io.IOException: Cannot run program mount:
java.io.IOException: error=12, Cannot allocate memory
Bump up RAM size of system offering for SSVM to 512MB
Signed-off-by: Sateesh Chodapuneedi sate...@apache.org
[Automation] Failed to deploy vm in vmware environment with error due to
java.io.IOException: Cannot run program mount: java.io.IOException:
error=12, Cannot allocate memory
--
Key: CLOUDSTACK-5408
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5408
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: VMware
Affects Versions: 4.3.0
Environment: vmware 5.0 update 3
64 bit template
Reporter: Rayees Namathponnan
Assignee: Sateesh Chodapuneedi
Priority: Critical
Fix For: 4.3.0
Attachments: CLOUDSTACK-5408.rar
Steps to reproduce
Create advanced zone in vmware
use 64 bit template
deploy VM
Result
SSVM are crated
Routers are created
VM deployment failed with below error
yStorageResource.mountUri(NfsSecondaryStorageResource.java:2293)\n\tat
org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.getRootDir(NfsSecondaryStorageResource.java:1934)\n\tat
com.cloud.storage.resource.VmwareSecondaryStorageResourceHandler.getMountPoint(VmwareSecondaryStorageResourceHandler.java:311)\n\tat
com.cloud.storage.resource.VmwareStorageProcessor.copyTemplateFromSecondaryToPrimary(VmwareStorageProcessor.java:131)\n\tat
com.cloud.storage.resource.VmwareStorageProcessor.copyTemplateToPrimaryStorage(VmwareStorageProcessor.java:221)\n\tat
com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:75)\n\tat
com.cloud.storage.resource.VmwareStorageSubsystemCommandHandler.execute(VmwareStorageSubsystemCommandHandler.java:155)\n\tat
com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:50)\n\tat
com.cloud.storage.resource.VmwareSecondaryStorageResourceHandler.executeRequest(VmwareSecondaryStorageResourceHandler.java:101)\n\tat
com.cloud.storage.resource.PremiumSecondaryStorageResource.executeRequest(PremiumSecondaryStorageResource.java:56)\n\tat
com.cloud.agent.Agent.processRequest(Agent.java:498)\n\tat
com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:806)\n\tat
com.cloud.utils.nio.Task.run(Task.java:83)\n\tat
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)\n\tat
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)\n\tat
java.lang.Thread.run(Thread.java:679)\nCaused by: java.io.IOException:
java.io.IOException: error=12, Cannot allocate memory\n\tat
java.lang.UNIXProcess.init(UNIXProcess.java:164)\n\tat
java.lang.ProcessImpl.start(ProcessImpl.java:81)\n\tat
java.lang.ProcessBuilder.start(ProcessBuilder.java:470)\n\t... 20
more\n\n,wait:0}}] }
2013-12-07 14:07:59,776 DEBUG [c.c.a.t.Request] (Job-Executor-23:ctx-f22d6e84
ctx-b6c94672) Seq 5-137756744: Received: { Ans: , MgmtId: 90928106758026,
via: 5, Ver: v1, Flags: 10, { CopyCmdAnswer } }
2013-12-07 14:07:59,791 INFO [o.a.c.s.v.VolumeServiceImpl]
(Job-Executor-23:ctx-f22d6e84 ctx-b6c94672) releasing lock for
VMTemplateStoragePool 9
2013-12-07 14:07:59,791 WARN [c.c.u.d.Merovingian2]
(Job-Executor-23:ctx-f22d6e84 ctx-b6c94672) Was unable to find lock for the
key template_spool_ref9 and thread id 1402045270
2013-12-07 14:07:59,791 DEBUG [o.a.c.e.o.VolumeOrchestrator]
(Job-Executor-23:ctx-f22d6e84 ctx-b6c94672) Unable to create
Vol[8|vm=8|ROOT]:Unable to copy template to primary storage due to
exception:Exception: com.cloud.utils.exception.CloudRuntimeException
Message: GetRootDir for
nfs://10.223.240.164:/home/common/automation/SC-CLOUD-QA03/secondary1 failed
due to com.cloud.utils.exception.CloudRuntimeException: Unable to mount
10.223.240.164:/home/common/automation/SC-CLOUD-QA03/secondary1 at
/mnt/SecStorage/c6ec0966-00ab-3817-8a96-e8f4c3e03269 due to
java.io.IOException: Cannot run program mount: java.io.IOException:
[jira] [Resolved] (CLOUDSTACK-5408) [Automation] Failed to deploy vm in vmware environment with error due to java.io.IOException: Cannot run program mount: java.io.IOException: error=12, Cannot all
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sateesh Chodapuneedi resolved CLOUDSTACK-5408.
--
Resolution: Fixed
[Automation] Failed to deploy vm in vmware environment with error due to
java.io.IOException: Cannot run program mount: java.io.IOException:
error=12, Cannot allocate memory
--
Key: CLOUDSTACK-5408
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5408
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: VMware
Affects Versions: 4.3.0
Environment: vmware 5.0 update 3
64 bit template
Reporter: Rayees Namathponnan
Assignee: Sateesh Chodapuneedi
Priority: Critical
Fix For: 4.3.0
Attachments: CLOUDSTACK-5408.rar
Steps to reproduce
Create advanced zone in vmware
use 64 bit template
deploy VM
Result
SSVM are crated
Routers are created
VM deployment failed with below error
yStorageResource.mountUri(NfsSecondaryStorageResource.java:2293)\n\tat
org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.getRootDir(NfsSecondaryStorageResource.java:1934)\n\tat
com.cloud.storage.resource.VmwareSecondaryStorageResourceHandler.getMountPoint(VmwareSecondaryStorageResourceHandler.java:311)\n\tat
com.cloud.storage.resource.VmwareStorageProcessor.copyTemplateFromSecondaryToPrimary(VmwareStorageProcessor.java:131)\n\tat
com.cloud.storage.resource.VmwareStorageProcessor.copyTemplateToPrimaryStorage(VmwareStorageProcessor.java:221)\n\tat
com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:75)\n\tat
com.cloud.storage.resource.VmwareStorageSubsystemCommandHandler.execute(VmwareStorageSubsystemCommandHandler.java:155)\n\tat
com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:50)\n\tat
com.cloud.storage.resource.VmwareSecondaryStorageResourceHandler.executeRequest(VmwareSecondaryStorageResourceHandler.java:101)\n\tat
com.cloud.storage.resource.PremiumSecondaryStorageResource.executeRequest(PremiumSecondaryStorageResource.java:56)\n\tat
com.cloud.agent.Agent.processRequest(Agent.java:498)\n\tat
com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:806)\n\tat
com.cloud.utils.nio.Task.run(Task.java:83)\n\tat
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)\n\tat
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)\n\tat
java.lang.Thread.run(Thread.java:679)\nCaused by: java.io.IOException:
java.io.IOException: error=12, Cannot allocate memory\n\tat
java.lang.UNIXProcess.init(UNIXProcess.java:164)\n\tat
java.lang.ProcessImpl.start(ProcessImpl.java:81)\n\tat
java.lang.ProcessBuilder.start(ProcessBuilder.java:470)\n\t... 20
more\n\n,wait:0}}] }
2013-12-07 14:07:59,776 DEBUG [c.c.a.t.Request] (Job-Executor-23:ctx-f22d6e84
ctx-b6c94672) Seq 5-137756744: Received: { Ans: , MgmtId: 90928106758026,
via: 5, Ver: v1, Flags: 10, { CopyCmdAnswer } }
2013-12-07 14:07:59,791 INFO [o.a.c.s.v.VolumeServiceImpl]
(Job-Executor-23:ctx-f22d6e84 ctx-b6c94672) releasing lock for
VMTemplateStoragePool 9
2013-12-07 14:07:59,791 WARN [c.c.u.d.Merovingian2]
(Job-Executor-23:ctx-f22d6e84 ctx-b6c94672) Was unable to find lock for the
key template_spool_ref9 and thread id 1402045270
2013-12-07 14:07:59,791 DEBUG [o.a.c.e.o.VolumeOrchestrator]
(Job-Executor-23:ctx-f22d6e84 ctx-b6c94672) Unable to create
Vol[8|vm=8|ROOT]:Unable to copy template to primary storage due to
exception:Exception: com.cloud.utils.exception.CloudRuntimeException
Message: GetRootDir for
nfs://10.223.240.164:/home/common/automation/SC-CLOUD-QA03/secondary1 failed
due to com.cloud.utils.exception.CloudRuntimeException: Unable to mount
10.223.240.164:/home/common/automation/SC-CLOUD-QA03/secondary1 at
/mnt/SecStorage/c6ec0966-00ab-3817-8a96-e8f4c3e03269 due to
java.io.IOException: Cannot run program mount: java.io.IOException:
error=12, Cannot allocate memory
at java.lang.ProcessBuilder.start(ProcessBuilder.java:488)
at com.cloud.utils.script.Script.execute(Script.java:177)
at com.cloud.utils.script.Script.execute(Script.java:155)
at
org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.attemptMount(NfsSecondaryStorageResource.java:2374)
at
org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.mount(NfsSecondaryStorageResource.java:2331)
at
[jira] [Closed] (CLOUDSTACK-5545) Xenserver - After HA , ssvm fails to start on the new host . Also not able to deploy new Vms in this host.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangeetha Hariharan closed CLOUDSTACK-5545.
---
Tested with latest build from 4.3.
Steps to reproduce the problem:
Advanced Zone with 1 cluster having 2 Xenserver 6.2 hosts.
Deploy Vms in both the hosts.
Bring down the master host - host1.
Host is marked as Down and all the HA enabled Vms successfully get HA-ed to
other host- host2 in the cluster.
Bring up host1.
Bring down host2.
Host is marked as Down and all the HA enabled Vms successfully get HA-ed to
other host- host1 in the cluster.
Repeated the above steps few times and did not see the issue mentioned in the
bug.
SSVM always starts successfully and I am able to deploy new vms successfully.
Xenserver - After HA , ssvm fails to start on the new host . Also not able to
deploy new Vms in this host.
--
Key: CLOUDSTACK-5545
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5545
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: Build from 4.3
Reporter: Sangeetha Hariharan
Assignee: Koushik Das
Priority: Critical
Fix For: 4.3.0
Attachments: hostdownssvmnotup.rar, management-server.log.rar
Xenserver - After HA , ssvm fails to start on the new host . Also not able to
deploy new Vms in this host.
Steps to reproduce the problem:
Set up - Advanced zone with 2 hots (Xenserver 6.2) , host1 and host2.
All user Vms (~11) and system Vms were running on host1.
power down host1.
All the HA enabled user Vms and system Vms were able to successfully start on
host2 and are reported as Running except for SSVM.
As part of HA process , seems like there were 2 threads that were trying to
work on the SSVM ( one trying to stop Vm and other trying to start Vm).
SSVM fails to start. I see that ssvm getting destroyed and trying to get
recreated over and over again with no success.
Following exception seen in management server logs:
com.cloud.utils.exception.CloudRuntimeException: We cannot proceed with stop
VM VM[SecondaryStorageVm|s-52-VM] since it is not in 'Stopping' state,
current state: Stop
ped
at
com.cloud.vm.VirtualMachineManagerImpl.advanceStop(VirtualMachineManagerImpl.java:1358)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStop(VirtualMachineManagerImpl.java:1258)
at
com.cloud.vm.VirtualMachineManagerImpl.advanceStop(VirtualMachineManagerImpl.java:1231)
at
com.cloud.ha.HighAvailabilityManagerImpl.restart(HighAvailabilityManagerImpl.java:485)
at
com.cloud.ha.HighAvailabilityManagerImpl$WorkerThread.runWithContext(HighAvailabilityManagerImpl.java:842)
at
com.cloud.ha.HighAvailabilityManagerImpl$WorkerThread.access$000(HighAvailabilityManagerImpl.java:797)
at
com.cloud.ha.HighAvailabilityManagerImpl$WorkerThread$1.run(HighAvailabilityManagerImpl.java:809)
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.ha.HighAvailabilityManagerImpl$WorkerThread.run(HighAvailabilityManagerImpl.java:806)
2013-12-17 18:36:47,986 WARN [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-13:ctx-fdae8cdf) Task failed! Task record: uuid:
f06cf2cc-6583-83aa-516e-6ea2
04d8dffe
nameLabel: Async.VM.start_on
nameDescription:
allowedOperations: []
currentOperations: {}
created: Tue Dec 17 18:36:45 EST 2013
finished: Tue Dec 17 18:36:59 EST 2013
status: failure
residentOn: com.xensource.xenapi.Host@a6594848
progress: 1.0
type: none/
result:
errorInfo: [HANDLE_INVALID, VM,
OpaqueRef:92a6a974-3e40-3acb-a633-cb2a40f5ad6f]
otherConfig: {debug_info:cancel_points_seen=27}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
2013-12-17 18:36:48,022 WARN [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-13:ctx-fdae8cdf) Unable to start VM(s-52-VM) on
host(eb0add58-3df6-4870-8937-ac21abe5471b) due to Task failed! Task record:
uuid: f06cf2cc-6583-83aa-516e-6ea204d8dffe
nameLabel: Async.VM.start_on
nameDescription:
allowedOperations: []
currentOperations: {}
[jira] [Commented] (CLOUDSTACK-5408) [Automation] Failed to deploy vm in vmware environment with error due to java.io.IOException: Cannot run program mount: java.io.IOException: error=12, Cannot al
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871507#comment-13871507
]
ASF subversion and git services commented on CLOUDSTACK-5408:
-
Commit ba96c8cadfa4b1dc7ee74fdb26ba5cea87e29b91 in branch refs/heads/master
from [~sateeshc]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ba96c8c ]
CLOUDSTACK-5408 [Automation] Failed to deploy vm in vmware environment with
error due to java.io.IOException: Cannot run program mount:
java.io.IOException: error=12, Cannot allocate memory
Bump up RAM size of system offering for SSVM to 512MB
Signed-off-by: Sateesh Chodapuneedi sate...@apache.org
[Automation] Failed to deploy vm in vmware environment with error due to
java.io.IOException: Cannot run program mount: java.io.IOException:
error=12, Cannot allocate memory
--
Key: CLOUDSTACK-5408
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5408
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: VMware
Affects Versions: 4.3.0
Environment: vmware 5.0 update 3
64 bit template
Reporter: Rayees Namathponnan
Assignee: Sateesh Chodapuneedi
Priority: Critical
Fix For: 4.3.0
Attachments: CLOUDSTACK-5408.rar
Steps to reproduce
Create advanced zone in vmware
use 64 bit template
deploy VM
Result
SSVM are crated
Routers are created
VM deployment failed with below error
yStorageResource.mountUri(NfsSecondaryStorageResource.java:2293)\n\tat
org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.getRootDir(NfsSecondaryStorageResource.java:1934)\n\tat
com.cloud.storage.resource.VmwareSecondaryStorageResourceHandler.getMountPoint(VmwareSecondaryStorageResourceHandler.java:311)\n\tat
com.cloud.storage.resource.VmwareStorageProcessor.copyTemplateFromSecondaryToPrimary(VmwareStorageProcessor.java:131)\n\tat
com.cloud.storage.resource.VmwareStorageProcessor.copyTemplateToPrimaryStorage(VmwareStorageProcessor.java:221)\n\tat
com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:75)\n\tat
com.cloud.storage.resource.VmwareStorageSubsystemCommandHandler.execute(VmwareStorageSubsystemCommandHandler.java:155)\n\tat
com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:50)\n\tat
com.cloud.storage.resource.VmwareSecondaryStorageResourceHandler.executeRequest(VmwareSecondaryStorageResourceHandler.java:101)\n\tat
com.cloud.storage.resource.PremiumSecondaryStorageResource.executeRequest(PremiumSecondaryStorageResource.java:56)\n\tat
com.cloud.agent.Agent.processRequest(Agent.java:498)\n\tat
com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:806)\n\tat
com.cloud.utils.nio.Task.run(Task.java:83)\n\tat
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)\n\tat
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)\n\tat
java.lang.Thread.run(Thread.java:679)\nCaused by: java.io.IOException:
java.io.IOException: error=12, Cannot allocate memory\n\tat
java.lang.UNIXProcess.init(UNIXProcess.java:164)\n\tat
java.lang.ProcessImpl.start(ProcessImpl.java:81)\n\tat
java.lang.ProcessBuilder.start(ProcessBuilder.java:470)\n\t... 20
more\n\n,wait:0}}] }
2013-12-07 14:07:59,776 DEBUG [c.c.a.t.Request] (Job-Executor-23:ctx-f22d6e84
ctx-b6c94672) Seq 5-137756744: Received: { Ans: , MgmtId: 90928106758026,
via: 5, Ver: v1, Flags: 10, { CopyCmdAnswer } }
2013-12-07 14:07:59,791 INFO [o.a.c.s.v.VolumeServiceImpl]
(Job-Executor-23:ctx-f22d6e84 ctx-b6c94672) releasing lock for
VMTemplateStoragePool 9
2013-12-07 14:07:59,791 WARN [c.c.u.d.Merovingian2]
(Job-Executor-23:ctx-f22d6e84 ctx-b6c94672) Was unable to find lock for the
key template_spool_ref9 and thread id 1402045270
2013-12-07 14:07:59,791 DEBUG [o.a.c.e.o.VolumeOrchestrator]
(Job-Executor-23:ctx-f22d6e84 ctx-b6c94672) Unable to create
Vol[8|vm=8|ROOT]:Unable to copy template to primary storage due to
exception:Exception: com.cloud.utils.exception.CloudRuntimeException
Message: GetRootDir for
nfs://10.223.240.164:/home/common/automation/SC-CLOUD-QA03/secondary1 failed
due to com.cloud.utils.exception.CloudRuntimeException: Unable to mount
10.223.240.164:/home/common/automation/SC-CLOUD-QA03/secondary1 at
/mnt/SecStorage/c6ec0966-00ab-3817-8a96-e8f4c3e03269 due to
java.io.IOException: Cannot run program mount: java.io.IOException:
[jira] [Commented] (CLOUDSTACK-5144) [Automation]: Basic Zone Security Groups - SSH to VM is allowed even when there is no ingress rule defined for the security group
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871509#comment-13871509 ] Anthony Xu commented on CLOUDSTACK-5144: rules look good, seems linux doesn't go though the rules, can you check value of below configs? cat /proc/sys/net/bridge/bridge-nf-call-iptables cat /proc/sys/net/bridge/bridge-nf-call-arptables They should be 1, if not execute following, echo 1 /proc/sys/net/bridge/bridge-nf-call-iptables echo 1 /proc/sys/net/bridge/bridge-nf-call-arptables Anthony [Automation]: Basic Zone Security Groups - SSH to VM is allowed even when there is no ingress rule defined for the security group - Key: CLOUDSTACK-5144 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5144 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.3.0 Reporter: Gaurav Aradhye Assignee: Wei Zhou Priority: Blocker Labels: automation Fix For: 4.3.0 Attachments: MS-Log.txt, agent.log, agent.log, ipset-L output.txt, iptables-rules.txt, log.zip, management-server.log, management-server.zip In Basic Zone Setup: 1. Create an account 2. Deploy a VM in that account 3. Verify that any ingress rule is not defined for the security group belonging to the account 4. Try SSH to VM using the nic ipaddress from external client SSH is successful to the VM where as it should fail when the ingress rule is not defined. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-703) Site-to-Site VPN 2.0 Enhancements
[ https://issues.apache.org/jira/browse/CLOUDSTACK-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871524#comment-13871524 ] Animesh Chaturvedi commented on CLOUDSTACK-703: --- Folks can we close out the subtasks and resolve the parent tasks Site-to-Site VPN 2.0 Enhancements - Key: CLOUDSTACK-703 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-703 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Reporter: Manan Shah Assignee: Sheng Yang Fix For: 4.3.0 Requirements described at: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Site-to-Site+VPN+2.0 Requirements discussion email thread link: http://markmail.org/search/?q=[ASFCS41]+Site-to-Site+2.0+enhancements+list%3Aorg.apache.incubator.cloudstack-dev -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5103) Documentation for DB HA
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Animesh Chaturvedi updated CLOUDSTACK-5103: --- Issue Type: Task (was: New Feature) Documentation for DB HA --- Key: CLOUDSTACK-5103 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5103 Project: CloudStack Issue Type: Task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.3.0 Reporter: Damodar Reddy T Fix For: 4.3.0 Please go through https://cwiki.apache.org/confluence/display/CLOUDSTACK/Database+High+Availability+%28DB+HA%29#DatabaseHighAvailability%28DBHA%29-ProposedSolution -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5103) Documentation for DB HA
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Animesh Chaturvedi updated CLOUDSTACK-5103: --- Issue Type: New Feature (was: Task) Documentation for DB HA --- Key: CLOUDSTACK-5103 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5103 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.3.0 Reporter: Damodar Reddy T Fix For: 4.3.0 Please go through https://cwiki.apache.org/confluence/display/CLOUDSTACK/Database+High+Availability+%28DB+HA%29#DatabaseHighAvailability%28DBHA%29-ProposedSolution -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-1770) Ability to delete Events and Alerts: Select multiple alerts and events.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Animesh Chaturvedi updated CLOUDSTACK-1770: --- Assignee: Brian Federle Ability to delete Events and Alerts: Select multiple alerts and events. --- Key: CLOUDSTACK-1770 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1770 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: UI Environment: NA Reporter: Parth Jagirdar Assignee: Brian Federle Fix For: 4.3.0 API handles multiple ID's. UI should also have an ability to select multiple alerts and events. And perform an action on them (Say delete) in one go. If we can get this to work in harmony with CLOUDSTACK 662 and CLOUDSTACK 1769 then that would be really great. Here is a use case from top of my head:: Admin wants to delete all login INFO in domain XYZ. So he searched LEVEL = INFO, domain ROOT with description text contains Logged in Once results appeared he selected all (by check boxes) the ADMIN in account and left SYSTEM behind. And deleted them at once. If this is too complicated then please log your comments and we can discuss this further. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5820) [Automation] SSH to portable public IP fails
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871653#comment-13871653
]
Rayees Namathponnan commented on CLOUDSTACK-5820:
-
I can see portable test cases getting passed in KVM, in VM ware there are
failure with below error mostly its test case issue,
Pe5EY4YSd6mECLicjfpGK4qempMWYwcDUVUiAfGTQEAcommand=createPortableIpRangesignature=BzYe7eSSXtnUrca1dcK7WLgzOfA%3Dgateway=10.223.243.1
Response: { createportableiprangeresponse :
{uuidList:[],errorcode:431,cserrorcode:4350,errortext:Ip range:
10.223.243.55-10.223.243.56 overlaps with a portable IP range already
configured in the region 1} }
test_delete_portable_ip_range
(integration.component.test_portable_ip.TestDeletePortablePublicIpRanges):
CRITICAL: EXCEPTION: test_delete_portable_ip_range: Traceback (most recent call
last):
File /usr/local/lib/python2.7/unittest/case.py, line 311, in run
self.setUp()
File
/data/Repo2/qa/cloudstack/test/integration/component/test_portable_ip.py,
line 316, in setUp
portable_ip_range_services)
File /usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py,
line 2408, in create
return PortablePublicIpRange(apiclient.createPortableIpRange(cmd).__dict__)
File
/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py,
line 2777, in createPortableIpRange
response = self.connection.marvinRequest(command, response_type=response,
method=method)
File /usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
line 272, in marvinRequest
response = jsonHelper.getResultObj(response.json(), response_type)
File /usr/local/lib/python2.7/site-packages/marvin/jsonHelper.py, line 148,
in getResultObj
raise cloudstackException.cloudstackAPIException(respname, errMsg)
cloudstackAPIException: Execute cmd: createportableiprange failed, due to:
errorCode: 431, errorText:Ip range: 10.223.243.55-10.223.243.56 overlaps with
a portable IP range already configured in the region 1
- end captured logging -
[Automation] SSH to portable public IP fails
Key: CLOUDSTACK-5820
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5820
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Network Controller
Affects Versions: 4.3.0
Environment: Observed on KVM and Xen, yet to check on VMware
Reporter: Gaurav Aradhye
Assignee: Murali Reddy
Priority: Critical
Labels: automation, network
Fix For: 4.3.0
Steps to reproduce:
1. Deploy a VM in isolated network
2. Acquire portable IP for the network
3. Create NAT rule for portable IP associating deployed VM
4. Try to SSH to the VM using the portable IP
SSH fails.
Same above steps for a non portable ip work fine for SSH.
Please let me know which additional info you require. I don't think
management server logs will help in this case. Let me know if you want to see
any iptables.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5820) [Automation] SSH to portable public IP fails
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan updated CLOUDSTACK-5820: Assignee: Gaurav Aradhye (was: Murali Reddy) [Automation] SSH to portable public IP fails Key: CLOUDSTACK-5820 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5820 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.3.0 Environment: Observed on KVM and Xen, yet to check on VMware Reporter: Gaurav Aradhye Assignee: Gaurav Aradhye Priority: Critical Labels: automation, network Fix For: 4.3.0 Steps to reproduce: 1. Deploy a VM in isolated network 2. Acquire portable IP for the network 3. Create NAT rule for portable IP associating deployed VM 4. Try to SSH to the VM using the portable IP SSH fails. Same above steps for a non portable ip work fine for SSH. Please let me know which additional info you require. I don't think management server logs will help in this case. Let me know if you want to see any iptables. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5820) [Automation] SSH to portable public IP fails
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan updated CLOUDSTACK-5820: Issue Type: Test (was: Bug) [Automation] SSH to portable public IP fails Key: CLOUDSTACK-5820 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5820 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.3.0 Environment: Observed on KVM and Xen, yet to check on VMware Reporter: Gaurav Aradhye Assignee: Murali Reddy Priority: Critical Labels: automation, network Fix For: 4.3.0 Steps to reproduce: 1. Deploy a VM in isolated network 2. Acquire portable IP for the network 3. Create NAT rule for portable IP associating deployed VM 4. Try to SSH to the VM using the portable IP SSH fails. Same above steps for a non portable ip work fine for SSH. Please let me know which additional info you require. I don't think management server logs will help in this case. Let me know if you want to see any iptables. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5873) [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871664#comment-13871664 ] Mike Tutkowski commented on CLOUDSTACK-5873: I have a fix in place that would put the functionality here back the way it was. HOWEVER: My testing has uncovered a problem with starting a VM after you attach a disk to the VM (when the VM has never been started before). I have observed this on XenServer. These steps fail (likely this is nothing new in 4.3): 1) Deploy a VM in the stopped state. 2) Attach a disk to the VM. 3) Start the VM Step 3 fails with an InsufficientServerCapacityException. If you detach the disk, then start the VM, it works. You may then attach the disk either while the VM is running or stopped and it works. The problem appears to be only when you attach a disk to a VM that has never been started before, then start the VM. I plan to test this on VMware and KVM soon. [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false -- Key: CLOUDSTACK-5873 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5873 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, Volumes Affects Versions: 4.3.0 Environment: KVM Build RHEL 6.3 Reporter: Rayees Namathponnan Assignee: Mike Tutkowski Priority: Critical Fix For: 4.3.0 Attachments: Regression_basic_KVM.rar Regression automation failure test_stopped_vm.py:test_04_deploy_startvm_false_attach_volume Steps to reproduce Validate the following: 1. deploy Vm with the startvm=false. Attach volume to the instance 2. listVM command should return the deployed VM.State of this VM should be Stopped. 3. Attach volume should be successful Attach volume failed with NPE 2014-01-08 18:58:19,204 INFO [c.c.s.VolumeApiServiceImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Trying to attaching volume 60 to vm instance:44, update async job-265 progress status 2014-01-08 18:58:19,204 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Update async-job attachment, job-265, instanceType: volume, instanceId: 60 2014-01-08 18:58:19,218 ERROR [c.c.a.ApiAsyncJobDispatcher] (Job-Executor-84:ctx-b175478d) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd java.lang.NullPointerException at com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:1964) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1304) at com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1129) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1104) 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:616) 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 $Proxy195.attachVolumeToVM(Unknown Source) at org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:123) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161) at com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109) at com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66) 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.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63) at
[jira] [Assigned] (CLOUDSTACK-5820) [Automation] SSH to portable public IP fails
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Girish Shilamkar reassigned CLOUDSTACK-5820: Assignee: Girish Shilamkar (was: Gaurav Aradhye) [Automation] SSH to portable public IP fails Key: CLOUDSTACK-5820 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5820 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.3.0 Environment: Observed on KVM and Xen, yet to check on VMware Reporter: Gaurav Aradhye Assignee: Girish Shilamkar Priority: Critical Labels: automation, network Fix For: 4.3.0 Steps to reproduce: 1. Deploy a VM in isolated network 2. Acquire portable IP for the network 3. Create NAT rule for portable IP associating deployed VM 4. Try to SSH to the VM using the portable IP SSH fails. Same above steps for a non portable ip work fine for SSH. Please let me know which additional info you require. I don't think management server logs will help in this case. Let me know if you want to see any iptables. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5873) [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871742#comment-13871742 ] Mike Tutkowski commented on CLOUDSTACK-5873: Step 3 (above) only fails if the data disk is on a different SR than the root disk. I believe this is an issue Marcus and I noticed a week ago (Marcus logged a JIRA ticket for it). If the root and data disk of a VM that's never been started before are on the same SR, the VM can start now. Step 3 also works for VMware (only tried this on a datastore that housed both the root and data disks). [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false -- Key: CLOUDSTACK-5873 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5873 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, Volumes Affects Versions: 4.3.0 Environment: KVM Build RHEL 6.3 Reporter: Rayees Namathponnan Assignee: Mike Tutkowski Priority: Critical Fix For: 4.3.0 Attachments: Regression_basic_KVM.rar Regression automation failure test_stopped_vm.py:test_04_deploy_startvm_false_attach_volume Steps to reproduce Validate the following: 1. deploy Vm with the startvm=false. Attach volume to the instance 2. listVM command should return the deployed VM.State of this VM should be Stopped. 3. Attach volume should be successful Attach volume failed with NPE 2014-01-08 18:58:19,204 INFO [c.c.s.VolumeApiServiceImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Trying to attaching volume 60 to vm instance:44, update async job-265 progress status 2014-01-08 18:58:19,204 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Update async-job attachment, job-265, instanceType: volume, instanceId: 60 2014-01-08 18:58:19,218 ERROR [c.c.a.ApiAsyncJobDispatcher] (Job-Executor-84:ctx-b175478d) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd java.lang.NullPointerException at com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:1964) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1304) at com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1129) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1104) 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:616) 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 $Proxy195.attachVolumeToVM(Unknown Source) at org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:123) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161) at com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109) at com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66) 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.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:524) 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
[jira] [Comment Edited] (CLOUDSTACK-5873) [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871742#comment-13871742 ] Mike Tutkowski edited comment on CLOUDSTACK-5873 at 1/15/14 7:05 AM: - Step 3 (above) only fails if the data disk is on a different SR than the root disk. I believe this is an issue Marcus and I noticed a week ago (Marcus logged a JIRA ticket for it). If the root and data disks of a VM that's never been started before are on the same SR, the VM can start now. Step 3 also works for VMware (only tried this on a datastore that housed both the root and data disks). was (Author: mike-tutkowski): Step 3 (above) only fails if the data disk is on a different SR than the root disk. I believe this is an issue Marcus and I noticed a week ago (Marcus logged a JIRA ticket for it). If the root and data disk of a VM that's never been started before are on the same SR, the VM can start now. Step 3 also works for VMware (only tried this on a datastore that housed both the root and data disks). [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false -- Key: CLOUDSTACK-5873 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5873 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, Volumes Affects Versions: 4.3.0 Environment: KVM Build RHEL 6.3 Reporter: Rayees Namathponnan Assignee: Mike Tutkowski Priority: Critical Fix For: 4.3.0 Attachments: Regression_basic_KVM.rar Regression automation failure test_stopped_vm.py:test_04_deploy_startvm_false_attach_volume Steps to reproduce Validate the following: 1. deploy Vm with the startvm=false. Attach volume to the instance 2. listVM command should return the deployed VM.State of this VM should be Stopped. 3. Attach volume should be successful Attach volume failed with NPE 2014-01-08 18:58:19,204 INFO [c.c.s.VolumeApiServiceImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Trying to attaching volume 60 to vm instance:44, update async job-265 progress status 2014-01-08 18:58:19,204 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Update async-job attachment, job-265, instanceType: volume, instanceId: 60 2014-01-08 18:58:19,218 ERROR [c.c.a.ApiAsyncJobDispatcher] (Job-Executor-84:ctx-b175478d) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd java.lang.NullPointerException at com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:1964) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1304) at com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1129) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1104) 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:616) 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 $Proxy195.attachVolumeToVM(Unknown Source) at org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:123) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161) at com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109) at com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at
[jira] [Commented] (CLOUDSTACK-5820) [Automation] SSH to portable public IP fails
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871747#comment-13871747 ] Girish Shilamkar commented on CLOUDSTACK-5820: -- Animesh, Yes it is manually reproducible. Rayees, In Portable IP testsuite test_list_portable_ip_range_non_root_admin has never passed any build, therefore we filed this issue. [Automation] SSH to portable public IP fails Key: CLOUDSTACK-5820 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5820 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.3.0 Environment: Observed on KVM and Xen, yet to check on VMware Reporter: Gaurav Aradhye Assignee: Girish Shilamkar Priority: Critical Labels: automation, network Fix For: 4.3.0 Steps to reproduce: 1. Deploy a VM in isolated network 2. Acquire portable IP for the network 3. Create NAT rule for portable IP associating deployed VM 4. Try to SSH to the VM using the portable IP SSH fails. Same above steps for a non portable ip work fine for SSH. Please let me know which additional info you require. I don't think management server logs will help in this case. Let me know if you want to see any iptables. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5873) [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871763#comment-13871763 ] Mike Tutkowski commented on CLOUDSTACK-5873: OK, I have checked in a fix. The moral is that the test should run fine now. We still have an issue if the root and data disks are on different SRs (for XenServer) or datastores (for VMware), but this is in JIRA as a separate ticket that Marcus opened last week. [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false -- Key: CLOUDSTACK-5873 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5873 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, Volumes Affects Versions: 4.3.0 Environment: KVM Build RHEL 6.3 Reporter: Rayees Namathponnan Assignee: Mike Tutkowski Priority: Critical Fix For: 4.3.0 Attachments: Regression_basic_KVM.rar Regression automation failure test_stopped_vm.py:test_04_deploy_startvm_false_attach_volume Steps to reproduce Validate the following: 1. deploy Vm with the startvm=false. Attach volume to the instance 2. listVM command should return the deployed VM.State of this VM should be Stopped. 3. Attach volume should be successful Attach volume failed with NPE 2014-01-08 18:58:19,204 INFO [c.c.s.VolumeApiServiceImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Trying to attaching volume 60 to vm instance:44, update async job-265 progress status 2014-01-08 18:58:19,204 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Update async-job attachment, job-265, instanceType: volume, instanceId: 60 2014-01-08 18:58:19,218 ERROR [c.c.a.ApiAsyncJobDispatcher] (Job-Executor-84:ctx-b175478d) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd java.lang.NullPointerException at com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:1964) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1304) at com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1129) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1104) 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:616) 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 $Proxy195.attachVolumeToVM(Unknown Source) at org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:123) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161) at com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109) at com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66) 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.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:524) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at
[jira] [Resolved] (CLOUDSTACK-5873) [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Tutkowski resolved CLOUDSTACK-5873. Resolution: Fixed [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false -- Key: CLOUDSTACK-5873 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5873 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, Volumes Affects Versions: 4.3.0 Environment: KVM Build RHEL 6.3 Reporter: Rayees Namathponnan Assignee: Mike Tutkowski Priority: Critical Fix For: 4.3.0 Attachments: Regression_basic_KVM.rar Regression automation failure test_stopped_vm.py:test_04_deploy_startvm_false_attach_volume Steps to reproduce Validate the following: 1. deploy Vm with the startvm=false. Attach volume to the instance 2. listVM command should return the deployed VM.State of this VM should be Stopped. 3. Attach volume should be successful Attach volume failed with NPE 2014-01-08 18:58:19,204 INFO [c.c.s.VolumeApiServiceImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Trying to attaching volume 60 to vm instance:44, update async job-265 progress status 2014-01-08 18:58:19,204 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Job-Executor-84:ctx-b175478d ctx-1c48338d) Update async-job attachment, job-265, instanceType: volume, instanceId: 60 2014-01-08 18:58:19,218 ERROR [c.c.a.ApiAsyncJobDispatcher] (Job-Executor-84:ctx-b175478d) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd java.lang.NullPointerException at com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:1964) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1304) at com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1129) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1104) 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:616) 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 $Proxy195.attachVolumeToVM(Unknown Source) at org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:123) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161) at com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109) at com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66) 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.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:524) 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$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at
