Instance can't use data disk in Devcloud
Hi all, I am trying to build cloudstack 4.2 using my laptop with Devcloud by following this guidehttp://www.leaseweblabs.com/2014/02/test-apache-cloudstack-4-2-local-machine/and, everything went smooth. But when I tried to create an instance with data disk offering I've got this following error : WARN [apache.cloudstack.alerts] (Job-Executor-1:job-11 = [ b3f84a36-095d-460d-a577-e8ef202cc218 ]) alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null // message:: Failed to deploy Vm with Id: 5, on Host with Id: null INFO [user.vm.DeployVMCmd] (Job-Executor-1:job-11 = [ b3f84a36-095d-460d-a577-e8ef202cc218 ]) com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|3ce1dd42-8daf-43b8-891c-3c05827ff159]Scope=interface com.cloud.dc.DataCenter; id=1 INFO [user.vm.DeployVMCmd] (Job-Executor-1:job-11 = [ b3f84a36-095d-460d-a577-e8ef202cc218 ]) Unable to create a deployment for VM[User|3ce1dd42-8daf-43b8-891c-3c05827ff159] com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|3ce1dd42-8daf-43b8-891c-3c05827ff159]Scope=interface com.cloud.dc.DataCenter; id=1 at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:209) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3412) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3000) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2986) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) According to what I've just read from here : http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201401.mbox/%3ccefd7abe.40328%25gprab...@juniper.net%3E Devcloud can't create an instance with data disk enabled, is it true? So I only allowed to create instance with no data disk? Please answer me.
Re: Mgmt server dows before complete its tasks
there was also a table called op_ha_work On Thu, Apr 10, 2014 at 9:57 PM, Rafael Weingartner rafaelweingart...@gmail.com wrote: thanks ;) On Thu, Apr 10, 2014 at 9:53 PM, Michael Phillips mphilli7...@hotmail.com wrote: I had a similar issue the other day and I had to manually remove the mgmt server from the DB. I found 3 tables mshostmshost_peerop_it_work. The tables are linked so you have to remove the data from the bottom two before you can remove the host from the mshost table. The tables are linked via the msid column. **Side note Reasons like yours are why I brought this up in the dev group as to why we need an option in the GUI to cleanly remove a mgmt server. Seems like we are gaining some traction on it so feel free to +1 this need to the dev group. Date: Thu, 10 Apr 2014 21:46:24 -0300 Subject: Re: Mgmt server dows before complete its tasks From: rafaelweingart...@gmail.com To: users@cloudstack.apache.org yeap On Thu, Apr 10, 2014 at 9:34 PM, Michael Phillips mphilli7...@hotmail.comwrote: Meaning how can you stop the other mgmt servers from looking for the disabled mgmt server? Date: Thu, 10 Apr 2014 21:00:12 -0300 Subject: Mgmt server dows before complete its tasks From: rafaelweingart...@gmail.com To: users@cloudstack.apache.org Hi folks, I have the following situation, one of my management server went down before completing some jobs that were assigned to it. It is not possible to recover that node, what can I do to make the others mgmt servers stop to try to connect into the mgmt server that is down? -- Rafael Weingärtner -- Rafael Weingärtner -- Rafael Weingärtner -- Rafael Weingärtner
Some problem registering ISO
Hi All,
I have installed cloudstack 4.1 on Ubuntu 12.04 LTS. The system vm's were
correctly created and are running.
I have also installed apache2 and configured it as shown below a few lines.
I copied the ubuntu iso file to /var/www dir.
I tried to Templates - Select View ISO, Register ISO, from the cloudstack GUI.
Name, Descrption : Ubuntu 12.04
URL : http://192.XXX.X.X:80/ubuntu-12.04.4-desktop-amd64.iso
And selected options : bootable, public and featured.
After pressing Ok button, and afer a while, cloud stack GUI, reports problem
as :
Status : Connection refused
Any clues, as to what is missing?
Thanks in advance.
Regards,
Giri
iptables -I INPUT -p tcp --dport 80 -m state --state NEW,ESTABLISHED -j ACCEPT
iptables -I OUTPUT -p tcp --sport 80 -m state --state ESTABLISHED -j ACCEPT
iptables -I INPUT -p tcp --dport 443 -m state --state NEW,ESTABLISHED -j ACCEPT
iptables -I OUTPUT -p tcp --sport 443 -m state --state ESTABLISHED -j ACCEPT
/etc/apache2/sites-available/default
VirtualHost 192.XXX.X.X:80
ServerAdmin webmaster@localhost
/VirtualHost
VirtualHost 192.XXX.X.X:443
ServerAdmin webmaster@localhost
/VirtualHost
/etc/apache2/ports.conf
#NameVirtualHost *:80
NameVirtualHost 192.XXX.X.X:80
Listen 80
NameVirtualHost 192.XXX.X.X:443
Listen 443
2014-04-11
18:53:01,908 DEBUG [cloud.api.ApiServlet] (catalina-exec-18:null)
===START=== 192.XXX.X.X -- GET
command=registerIsoresponse=jsonsessionkey=SOcwFO6T0PvHrpiFSRySjuDkC1w%3Dname=ubuntu+12.04displayText=ubuntu+12.04url=http%3A%2F%2F192.XXX.X.X%3A80%2Fubuntu-12.04.4-desktop-amd64.isozoneid=-1isextractable=falsebootable=trueosTypeId=bebeafbe-c09d-11e3-a09a-b8ac6fa54598ispublic=trueisfeatured=true_=1397222581864
2014-04-11
18:53:02,341 DEBUG [agent.transport.Request] (catalina-exec-18:null)
Seq 4-1716715535: Sending { Cmd , MgmtId: 3373003050, via: 4, Ver:
v1, Flags: 100011,
[{storage.DownloadCommand:{hvm:true,description:ubuntu
12.04,maxDownloadSizeInBytes:53687091200,id:209,resourceType:TEMPLATE,url:http://192.XXX.X.X:80/ubuntu-12.04.4-desktop-amd64.iso,format:ISO,accountId:2,name:209-2-9078c27c-aae3-3e83-acdd-29b177c2af41,secUrl:nfs://192.XXX.X.X/export/secondary,wait:0}}]
}
2014-04-11 18:53:02,762 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-8:null) Ping from 1
2014-04-11
18:53:02,955 DEBUG [cloud.api.ApiServlet] (catalina-exec-18:null)
===END=== 192.XXX.X.X -- GET
command=registerIsoresponse=jsonsessionkey=SOcwFO6T0PvHrpiFSRySjuDkC1w%3Dname=ubuntu+12.04displayText=ubuntu+12.04url=http%3A%2F%2F192.XXX.X.X%3A80%2Fubuntu-12.04.4-desktop-amd64.isozoneid=-1isextractable=falsebootable=trueosTypeId=bebeafbe-c09d-11e3-a09a-b8ac6fa54598ispublic=trueisfeatured=true_=1397222581864
2014-04-11
18:53:05,671 DEBUG [agent.transport.Request]
(AgentManager-Handler-10:null) Seq 4-1716715535: Processing: { Ans: ,
MgmtId: 3373003050, via: 4, Ver: v1, Flags: 10,
[{storage.DownloadAnswer:{jobId:e1062610-bb70-4946-a860-da3fe3b523f2,downloadPct:0,errorString:
,downloadStatus:NOT_DOWNLOADED,downloadPath:/mnt/SecStorage/8a818369-b841-3a4a-9b29-915c301f9a85/template/tmpl/2/209/dnld6474604236321162705tmp_,templateSize:0,templatePhySicalSize:0,result:false,details:
,wait:0}}] }
2014-04-11 18:53:06,109 DEBUG
[agent.manager.AgentManagerImpl] (AgentManager-Handler-11:null) SeqA
3-64: Processing Seq 3-64: { Cmd , MgmtId: -1, via: 3, Ver: v1, Flags:
11, [{ConsoleProxyLoadReportCommand:{_proxyVmId:2,_loadInfo:{\n
\connections\: []\n},wait:0}}] }
2014-04-11 18:53:06,190 DEBUG
[agent.manager.AgentManagerImpl] (AgentManager-Handler-11:null) SeqA
3-64: Sending Seq 3-64: { Ans: , MgmtId: 3373003050, via: 3, Ver:
v1, Flags: 100010, [{AgentControlAnswer:{result:true,wait:0}}] }
2014-04-11
18:53:10,965 DEBUG [cloud.api.ApiServlet] (catalina-exec-14:null)
===START=== 192.XXX.X.X -- GET
command=listIsosisofilter=selfid=e84e21d5-270f-4779-81a3-22f389221a15zoneid=76d51e53-15ca-4971-b03d-7bd8cbce453aresponse=jsonsessionkey=SOcwFO6T0PvHrpiFSRySjuDkC1w%3D_=1397222590952
2014-04-11
18:53:10,990 DEBUG [cloud.api.ApiServlet] (catalina-exec-14:null)
===END=== 192.XXX.X.X -- GET
command=listIsosisofilter=selfid=e84e21d5-270f-4779-81a3-22f389221a15zoneid=76d51e53-15ca-4971-b03d-7bd8cbce453aresponse=jsonsessionkey=SOcwFO6T0PvHrpiFSRySjuDkC1w%3D_=1397222590952
2014-04-11
18:53:11,083 DEBUG [cloud.api.ApiServlet] (catalina-exec-25:null)
===START=== 192.XXX.X.X -- GET
command=listOsTypesresponse=jsonsessionkey=SOcwFO6T0PvHrpiFSRySjuDkC1w%3D_=1397222591039
2014-04-11
18:53:11,083 DEBUG [cloud.api.ApiServlet] (catalina-exec-7:null)
===START=== 192.XXX.X.X -- GET
command=listTagsresponse=jsonsessionkey=SOcwFO6T0PvHrpiFSRySjuDkC1w%3DresourceId=e84e21d5-270f-4779-81a3-22f389221a15resourceType=ISOlistAll=true_=1397222591050
2014-04-11
18:53:11,102 DEBUG [cloud.api.ApiServlet] (catalina-exec-7:null)
===END=== 192.XXX.X.X -- GET
Re: Cloudstack 4.3 instances can't access outside world
Thanks Suresh, I tried your suggestion and I'm not able to access outside the VR router. I am stumped! please help! On Thu, Apr 10, 2014 at 7:21 AM, Suresh Sadhu suresh.sa...@citrix.comwrote: Ok then work around is manually append rule to cloudbr1 . Take the backup of iptables rules Manfully detach the eth interface from cloudbr0 and attach to cloudbr1 Apply the all exiting firewall rules manually on the interface gain After that your VMs will access the public network. Regards Sadhu -Original Message- From: motty cruz [mailto:motty.c...@gmail.com] Sent: 10 April 2014 19:40 To: users@cloudstack.apache.org Subject: Re: Cloudstack 4.3 instances can't access outside world yes, I'm am using traffic labels, everything was working fine before the upgrade to 4.3. did not change anything on the cloudbr0 or cloudbr1. On Thu, Apr 10, 2014 at 7:05 AM, Suresh Sadhu suresh.sa...@citrix.com wrote: Did you used traffic name labels? In 4.3 traffic labels are not considering ,by default its attaching to default traffic labels(eg:in KVM its cloudbr0 ...due to this unable to access public network i.r before upgrade if ieth2 attached cloudbr1 and after upgrade its attached to cloudbr0).maybe you are hitting this issue. Regards sadhu -Original Message- From: motty cruz [mailto:motty.c...@gmail.com] Sent: 10 April 2014 19:28 To: users@cloudstack.apache.org Subject: Re: Cloudstack 4.3 instances can't access outside world yes I can ping VR, also after the upgrade VR has four insterfaces, eth0 subnet for Instances, eth1, eth2 for public IP and eth3 for public IP. On Wed, Apr 9, 2014 at 10:35 PM, Erik Weber terbol...@gmail.com wrote: Can you ping the VR? Log on to the VR, and get the iptables rules. How do they look? Erik Weber 10. apr. 2014 00:21 skrev motty cruz motty.c...@gmail.com følgende: I did add egress rules, reboot network but no sucess, so I removed that rules and nothing. I am lost. On Wed, Apr 9, 2014 at 9:08 AM, Erik Weber terbol...@gmail.com wrote: Did you remove the egress rule again? If not, try that. Erik 9. apr. 2014 15:49 skrev motty cruz motty.c...@gmail.com følgende: yes I try adding the rule, restart network and router but no success! On Tue, Apr 8, 2014 at 11:16 PM, Erik Weber terbol...@gmail.com wrote: Try adding an egress rule, and removing it again. We experience the same, but has so far believed it was because we changed the default rule from deny to allow after accounts were made.. On Tue, Apr 8, 2014 at 11:14 PM, motty cruz motty.c...@gmail.com wrote: I have two isolated network both virtual routers can ping anywhere, but the Instances behind the virtual router can't ping or access the internet. On Tue, Apr 8, 2014 at 10:38 AM, motty cruz motty.c...@gmail.com wrote: Hello, I'm having issues with VMs unable to access outside world. I can ping gateway, also when I log in to virtual router, I am able to ping google.com or anywhere. in the Egress rules I am allowing all. reboot network and virtual router does not help. VMs were able to access outside before upgrading from 4.2 to 4.3. any ideas?
Fast primary storage migration
Hi, I would like to move my primary storage (5x1TB, CS 4.2) from GFS2 to NFS. I don't want to use cloudstack offline disk migration because it's too slow. What I plan to do : 1) Declare a new primary storage (NFS) 2) Stop all running VM on the cluster 3) Put GFS2 primary storage in maintenance mode 3) Rsync GFS2 mount point NFS mountpoint (excluding templates files) 4) Update DB : update volumes set folder=/xx/yy/zzz ,pool_type= NULL,pool_id=XXX where name=[ROOT|DATA]-XXX; Inputs are welcome Florent
VMs and volumes migration between clusters.
Hi folks, After VMs and/or volumes being migrated from one cluster to another, will Cloudstack delete the file from the storage of the old cluster? -- Rafael Weingärtner
Re: VMs and volumes migration between clusters.
Yes On Apr 11, 2014 10:51 AM, Rafael Weingartner rafaelweingart...@gmail.com wrote: Hi folks, After VMs and/or volumes being migrated from one cluster to another, will Cloudstack delete the file from the storage of the old cluster? -- Rafael Weingärtner
Re: VMs and volumes migration between clusters.
Right away, or is it an async job? I ask that because I had migrated all VMs and volumes that I have in one cluster to a new one. After the process completed, I noticed that the cluster that had the VMs migrated from was still with 84GB of VHDs files. On Fri, Apr 11, 2014 at 2:52 PM, Sanjeev Neelarapu sanjeev.neelar...@citrix.com wrote: Yes On Apr 11, 2014 10:51 AM, Rafael Weingartner rafaelweingart...@gmail.com wrote: Hi folks, After VMs and/or volumes being migrated from one cluster to another, will Cloudstack delete the file from the storage of the old cluster? -- Rafael Weingärtner -- Rafael Weingärtner
Re: VMs and volumes migration between clusters.
Files will be deleted after the successful VM/volume migration to new cluster/storage On Apr 11, 2014 10:58 AM, Rafael Weingartner rafaelweingart...@gmail.com wrote: Right away, or is it an async job? I ask that because I had migrated all VMs and volumes that I have in one cluster to a new one. After the process completed, I noticed that the cluster that had the VMs migrated from was still with 84GB of VHDs files. On Fri, Apr 11, 2014 at 2:52 PM, Sanjeev Neelarapu sanjeev.neelar...@citrix.com wrote: Yes On Apr 11, 2014 10:51 AM, Rafael Weingartner rafaelweingart...@gmail.com wrote: Hi folks, After VMs and/or volumes being migrated from one cluster to another, will Cloudstack delete the file from the storage of the old cluster? -- Rafael Weingärtner -- Rafael Weingärtner
Re: VMs and volumes migration between clusters.
the files were successfully migrate. In fact, those VMs are already running on the new cluster. Should I care about those VHD files on the old cluster? Will CS delete them ? On Fri, Apr 11, 2014 at 3:11 PM, Sanjeev Neelarapu sanjeev.neelar...@citrix.com wrote: Files will be deleted after the successful VM/volume migration to new cluster/storage On Apr 11, 2014 10:58 AM, Rafael Weingartner rafaelweingart...@gmail.com wrote: Right away, or is it an async job? I ask that because I had migrated all VMs and volumes that I have in one cluster to a new one. After the process completed, I noticed that the cluster that had the VMs migrated from was still with 84GB of VHDs files. On Fri, Apr 11, 2014 at 2:52 PM, Sanjeev Neelarapu sanjeev.neelar...@citrix.com wrote: Yes On Apr 11, 2014 10:51 AM, Rafael Weingartner rafaelweingart...@gmail.com wrote: Hi folks, After VMs and/or volumes being migrated from one cluster to another, will Cloudstack delete the file from the storage of the old cluster? -- Rafael Weingärtner -- Rafael Weingärtner -- Rafael Weingärtner
Re: unable to deploy instance
Dimas, I don't have a 4.2 version checked out at the moment so I can't give you a definite answer. It is best to try 4.3.0 or if it is a proof of concept that you can disgard build a system from the master branch of the repository. The InsufficientServerCapacityException can be kind of obscure but generally is what is seems to be. If you want to hunt the problem down in your env look at the host that the vm will be deployed on. Do the offerings for disk net and system fit on the host (isn't cpu more mHz then the cores support and those kind of things). good hunting, Daan On Thu, Apr 10, 2014 at 12:24 AM, dimas yoga pratama smid...@gmail.com wrote: Hi all, I am trying to build build cloudstack 4.2 using my laptop by following this guidehttp://www.leaseweblabs.com/2014/02/test-apache-cloudstack-4-2-local-machine/and, everything went smooth. But when I tried to create an instance I've got this following error : WARN [apache.cloudstack.alerts] (Job-Executor-1:job-11 = [ b3f84a36-095d-460d-a577-e8ef202cc218 ]) alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null // message:: Failed to deploy Vm with Id: 5, on Host with Id: null INFO [user.vm.DeployVMCmd] (Job-Executor-1:job-11 = [ b3f84a36-095d-460d-a577-e8ef202cc218 ]) com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|3ce1dd42-8daf-43b8-891c-3c05827ff159]Scope=interface com.cloud.dc.DataCenter; id=1 INFO [user.vm.DeployVMCmd] (Job-Executor-1:job-11 = [ b3f84a36-095d-460d-a577-e8ef202cc218 ]) Unable to create a deployment for VM[User|3ce1dd42-8daf-43b8-891c-3c05827ff159] com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|3ce1dd42-8daf-43b8-891c-3c05827ff159]Scope=interface com.cloud.dc.DataCenter; id=1 at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:209) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3412) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3000) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2986) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) This is happen when I create an Instance with Data Disk Offering enabled, why is this happen? I want to test Cloudstack with complete functionality. Is there any suggestion what version of Cloudstack I should use? -- Daan
Re: Cloudstack 4.3 instances can't access outside world
I have a testing cloudstack cluster, I destroyed it and rebuilding upgraded serveral times, each time I ran into the same problem, unable to access outside world from instances behind virtual router. here is iptables before upgrade, Cloudstack 4.2 # Generated by iptables-save v1.4.14 on Fri Apr 11 19:53:57 2014 *mangle :PREROUTING ACCEPT [2317:1282555] :INPUT ACCEPT [409:147015] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [189:29312] :POSTROUTING ACCEPT [189:29312] :FIREWALL_176.23.23.192 - [0:0] :VPN_176.23.23.192 - [0:0] -A PREROUTING -d 176.23.23.192/32 -j VPN_176.23.23.192 -A PREROUTING -d 176.23.23.192/32 -j FIREWALL_176.23.23.192 -A PREROUTING -m state --state RELATED,ESTABLISHED -j CONNMARK --restore-mark --nfmask 0x --ctmask 0x -A POSTROUTING -p udp -m udp --dport 68 -j CHECKSUM --checksum-fill -A FIREWALL_176.23.23.192 -m state --state RELATED,ESTABLISHED -j ACCEPT -A FIREWALL_176.23.23.192 -j DROP -A VPN_176.23.23.192 -m state --state RELATED,ESTABLISHED -j ACCEPT -A VPN_176.23.23.192 -j RETURN COMMIT # Completed on Fri Apr 11 19:53:57 2014 # Generated by iptables-save v1.4.14 on Fri Apr 11 19:53:57 2014 *filter :INPUT DROP [204:117504] :FORWARD DROP [0:0] :OUTPUT ACCEPT [150:22404] :FW_OUTBOUND - [0:0] :NETWORK_STATS - [0:0] -A INPUT -j NETWORK_STATS -A INPUT -d 224.0.0.18/32 -j ACCEPT -A INPUT -d 225.0.0.50/32 -j ACCEPT -A INPUT -i eth0 -m state --state RELATED,ESTABLISHED -j ACCEPT -A INPUT -i eth1 -m state --state RELATED,ESTABLISHED -j ACCEPT -A INPUT -i eth2 -m state --state RELATED,ESTABLISHED -j ACCEPT -A INPUT -p icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -i eth0 -p udp -m udp --dport 67 -j ACCEPT -A INPUT -i eth0 -p udp -m udp --dport 53 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 53 -j ACCEPT -A INPUT -i eth1 -p tcp -m state --state NEW -m tcp --dport 3922 -j ACCEPT -A INPUT -i eth0 -p tcp -m state --state NEW -m tcp --dport 80 -j ACCEPT -A INPUT -s 10.1.1.0/24 -i eth0 -p tcp -m state --state NEW -m tcp --dport 8080 -j ACCEPT -A FORWARD -j NETWORK_STATS -A FORWARD -i eth0 -o eth1 -m state --state RELATED,ESTABLISHED -j ACCEPT -A FORWARD -i eth0 -o eth0 -m state --state NEW -j ACCEPT -A FORWARD -i eth0 -o eth0 -m state --state RELATED,ESTABLISHED -j ACCEPT -A FORWARD -i eth2 -o eth0 -m state --state RELATED,ESTABLISHED -j ACCEPT -A FORWARD -i eth0 -o eth2 -j FW_OUTBOUND -A OUTPUT -j NETWORK_STATS -A FW_OUTBOUND -m state --state RELATED,ESTABLISHED -j ACCEPT -A NETWORK_STATS -i eth0 -o eth2 -A NETWORK_STATS -i eth2 -o eth0 -A NETWORK_STATS ! -i eth0 -o eth2 -p tcp -A NETWORK_STATS -i eth2 ! -o eth0 -p tcp COMMIT # Completed on Fri Apr 11 19:53:57 2014 # Generated by iptables-save v1.4.14 on Fri Apr 11 19:53:57 2014 *nat :PREROUTING ACCEPT [2078:1204416] :INPUT ACCEPT [10:964] :OUTPUT ACCEPT [1:338] :POSTROUTING ACCEPT [1:338] -A POSTROUTING -o eth2 -j SNAT --to-source 176.23.23.192 COMMIT # Completed on Fri Apr 11 19:53:57 2014 after upgrading to Cloudstack 4.3 :POSTROUTING ACCEPT [211:25828] :FIREWALL_176.23.23.192 - [0:0] :VPN_176.23.23.192 - [0:0] -A PREROUTING -d 176.23.23.192/32 -j VPN_176.23.23.192 -A PREROUTING -d 176.23.23.192/32 -j FIREWALL_176.23.23.192 -A PREROUTING -m state --state RELATED,ESTABLISHED -j CONNMARK --restore-mark --nfmask 0x --ctmask 0x -A POSTROUTING -p udp -m udp --dport 68 -j CHECKSUM --checksum-fill -A FIREWALL_176.23.23.192 -m state --state RELATED,ESTABLISHED -j ACCEPT -A FIREWALL_176.23.23.192 -j DROP -A VPN_176.23.23.192 -m state --state RELATED,ESTABLISHED -j ACCEPT -A VPN_176.23.23.192 -j RETURN COMMIT # Completed on Fri Apr 11 20:49:46 2014 # Generated by iptables-save v1.4.14 on Fri Apr 11 20:49:46 2014 *filter :INPUT DROP [68:32168] :FORWARD DROP [0:0] :OUTPUT ACCEPT [81:12516] :FW_EGRESS_RULES - [0:0] :FW_OUTBOUND - [0:0] :NETWORK_STATS - [0:0] -A INPUT -j NETWORK_STATS -A INPUT -d 224.0.0.18/32 -j ACCEPT -A INPUT -d 225.0.0.50/32 -j ACCEPT -A INPUT -i eth0 -m state --state RELATED,ESTABLISHED -j ACCEPT -A INPUT -i eth1 -m state --state RELATED,ESTABLISHED -j ACCEPT -A INPUT -i eth2 -m state --state RELATED,ESTABLISHED -j ACCEPT -A INPUT -p icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -i eth0 -p udp -m udp --dport 67 -j ACCEPT -A INPUT -i eth0 -p udp -m udp --dport 53 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 53 -j ACCEPT -A INPUT -i eth1 -p tcp -m state --state NEW -m tcp --dport 3922 -j ACCEPT -A INPUT -i eth0 -p tcp -m state --state NEW -m tcp --dport 80 -j ACCEPT -j ACCEPT -A FORWARD -j NETWORK_STATS -A FORWARD -i eth0 -o eth1 -m state --state RELATED,ESTABLISHED -j ACCEPT -A FORWARD -i eth2 -o eth0 -m state --state RELATED,ESTABLISHED -j ACCEPT -A FORWARD -i eth0 -o eth0 -m state --state NEW -j ACCEPT -A FORWARD -i eth0 -o eth0 -m state --state RELATED,ESTABLISHED -j ACCEPT -A FORWARD -i eth0 -o eth2 -j FW_OUTBOUND -A FORWARD -i eth3 -o eth0 -m state --state RELATED,ESTABLISHED -j ACCEPT -A FORWARD -i eth0 -o eth3 -j FW_OUTBOUND -A OUTPUT -j NETWORK_STATS -A FW_EGRESS_RULES -p udp -m udp
KVM, Re-create VR failed
Hi, It's can be some know bug? Possible it's already solved in new releases of CS but i need the work-around or fix before upgrade or reference to bug id. Environment: CS 4.1.1 libvirt-1.0.1 qemu-kvm-1.2 NFS Storage ( as primary for VR's ) Advanced VLAN isolation After hypervisor host crashing, one of VR's has failed to start in failover case, I have stopped it through UI with force, then was removed the VR for re-create it again by start/create VM API call. Try to start the Instance associated with this network, but failed because the VR can't be started when newly created. cloudstack-agent: 2014-04-11 07:05:34,546 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Failed to get dom xml: org.libvirt.LibvirtException: Domain not found: no domain with matching uuid '373ab4a9-cb8c-3275-a455-b9b4b963a983' 2014-04-11 07:05:34,547 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Failed to get dom xml: org.libvirt.LibvirtException: Domain not found: no domain with matching uuid '373ab4a9-cb8c-3275-a455-b9b4b963a983' 2014-04-11 07:05:34,548 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Failed to get dom xml: org.libvirt.LibvirtException: Domain not found: no domain with matching uuid '373ab4a9-cb8c-3275-a455-b9b4b963a983' 2014-04-11 07:05:34,548 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Executing: /usr/share/cloudstack-common/scripts/vm/network/security_group.py destroy_network_rules_for_vm --vmname r-377-VM 2014-04-11 07:05:34,663 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Execution is successful. 2014-04-11 07:05:34,664 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Try to stop the vm at first 2014-04-11 07:05:34,665 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Failed to stop VM :r-377-VM : org.libvirt.LibvirtException: Domain not found: no domain with matching uuid '373ab4a9-cb8c-3275-a455-b9b4b963a983' at org.libvirt.ErrorHandler.processError(Unknown Source) at org.libvirt.Connect.processError(Unknown Source) at org.libvirt.Connect.domainLookupByUUIDString(Unknown Source) at org.libvirt.Connect.domainLookupByUUID(Unknown Source) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.stopVM(LibvirtComputingResource.java:4021) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.stopVM(LibvirtComputingResource.java:3970) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:2894) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1032) at com.cloud.agent.Agent.processRequest(Agent.java:525) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852) at com.cloud.utils.nio.Task.run(Task.java:83) 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-04-11 07:05:34,666 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Failed to get vm status:Domain not found: no domain with matching uuid '373ab4a9-cb8c-3275-a455-b9b4b963a983' 2014-04-11 07:05:34,667 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Failed to get vm status:Domain not found: no domain with matching uuid '373ab4a9-cb8c-3275-a455-b9b4b963a983' 2014-04-11 07:05:34,668 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Failed to get vm status:Domain not found: no domain with matching uuid '373ab4a9-cb8c-3275-a455-b9b4b963a983' Management CS: 2014-04-11 07:05:40,503 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-114:job-3001) Found 5 ip(s) to apply as a part of domR VM[DomainRouter|r-377-VM] start. 2014-04-11 07:05:40,528 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-114:job-3001) Resending ipAssoc, port forwarding, load balancing rules as a part of Virtual router start 2014-04-11 07:05:40,542 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-114:job-3001) Found 1 firewall Egress rule(s) to apply as a part of domR VM[DomainRouter|r-377-VM] start. 2014-04-11 07:05:40,581 ERROR [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-114:job-3001) Failed to start instance VM[DomainRouter|r-377-VM] java.lang.NullPointerException at com.cloud.network.NetworkModelImpl.getIpInNetwork(NetworkModelImpl.java:763) at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.finalizeNetworkRulesForNetwork(VirtualNetworkApplianceManagerImpl.java:2346) at com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.finalizeNetworkRulesForNetwork(VpcVirtualNetworkApplianceManagerImpl.java:928) at
