[jira] [Updated] (CLOUDSTACK-3174) Making SDN controller work with XCP 1.6
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tuna updated CLOUDSTACK-3174: - Description: Fix errors when the controller interacts with XCP hosts (was: Fix tag error when the controller interacts with XCP hosts) Making SDN controller work with XCP 1.6 --- Key: CLOUDSTACK-3174 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3174 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Reporter: tuna Assignee: tuna Fix For: 4.2.0 Fix errors when the controller interacts with XCP hosts -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-3174) Making SDN controller work with XCP 1.6
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tuna resolved CLOUDSTACK-3174. -- Resolution: Fixed SDN native controller now already works with XCP1.6 at my branch. There are some issues when trying to make OVS guest network work with XCP I found: + network name-label: CS have to check network available with the defined name-label. + script enableXenServerNetwork doesn't work with XCP. The dom0vif.plug function leads to an error: INTERNAL_ERROR: Object with type extra and id 296e988a-fdd0-4a98-825a-0d728135f78a does not exist in xenopsd + ovstunnel plugin doesn't know where cloudstack_pluginlib is. + setup_ovs_bridge function in ovstunnel doesn't know what product_version is. I'll make a document about how to fix them and submit patch to review board asap. Making SDN controller work with XCP 1.6 --- Key: CLOUDSTACK-3174 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3174 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Reporter: tuna Assignee: tuna Fix For: 4.2.0 Fix tag error when the controller interacts with XCP hosts -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3316) the cpvm and ssvm can not start ,the state is still starting
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701714#comment-13701714 ] terryye commented on CLOUDSTACK-3316: - virsh list Id 名称 状态 -- 1 v-13-VM running 2 s-327-VM running cat /var/log/libvirt/qemu/s-327-VM.log 2013-07-08 01:07:32.959+: starting up LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-1.0 -enable-kvm -m 256 -smp 1,sockets=1,cores=1,threads=1 -name s-327-VM -uuid 3cc13717-ef14-4b06-96b2-3c215a712354 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/s-327-VM.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -no-shutdown -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x7 -drive file=/mnt/d7934658-3c3d-3417-8937-35e1c83a5c3a/20129033-e696-4163-b31b-69bc0e11bb0c,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,bus=pci.0,addr=0x8,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2 -drive file=/usr/share/cloudstack-common/vms/systemvm.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw,cache=none -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 -netdev tap,fd=19,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=0e:00:a9:fe:00:ec,bus=pci.0,addr=0x3 -netdev tap,fd=21,id=hostnet1 -device virtio-net-pci,netdev=hostnet1,id=net1,mac=06:47:6a:00:00:10,bus=pci.0,addr=0x4 -netdev tap,fd=22,id=hostnet2 -device virtio-net-pci,netdev=hostnet2,id=net2,mac=06:61:bc:00:00:1f,bus=pci.0,addr=0x5 -netdev tap,fd=23,id=hostnet3 -device virtio-net-pci,netdev=hostnet3,id=net3,mac=06:18:5a:00:00:15,bus=pci.0,addr=0x6 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/s-327-VM.agent,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=s-327-VM.vport -usb -device usb-tablet,id=input0 -vnc 0.0.0.0:1,password -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x9 Domain id=2 is tainted: high-privileges char device redirected to /dev/pts/1 cat /var/log/libvirt/qemu/v-13-VM.log LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-1.0 -enable-kvm -m 1024 -smp 1,sockets=1,cores=1,threads=1 -name v-13-VM -uuid d8847232-7a1c-4042-9b2c-608f0acb5123 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/v-13-VM.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -no-shutdown -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive file=/mnt/d7934658-3c3d-3417-8937-35e1c83a5c3a/f235b35d-771e-43c7-a423-25f36842bdd2,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2 -drive file=/usr/share/cloudstack-common/vms/systemvm.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw,cache=none -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 -netdev tap,fd=19,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=0e:00:a9:fe:02:59,bus=pci.0,addr=0x3 -netdev tap,fd=20,id=hostnet1 -device virtio-net-pci,netdev=hostnet1,id=net1,mac=06:51:ec:00:00:11,bus=pci.0,addr=0x4 -netdev tap,fd=21,id=hostnet2 -device virtio-net-pci,netdev=hostnet2,id=net2,mac=06:66:9a:00:00:20,bus=pci.0,addr=0x5 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/v-13-VM.agent,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=v-13-VM.vport -usb -device usb-tablet,id=input0 -vnc 0.0.0.0:0,password -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 Domain id=1 is tainted: high-privileges char device redirected to /dev/pts/0 Some ERROR at the vnet. the cpvm and ssvm can not start ,the state is still starting Key: CLOUDSTACK-3316 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3316 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller, Install and Setup, KVM, Management Server Affects Versions: 4.2.0 Environment: ubuntu12.04 kvm Reporter: terryye Fix For: 4.2.0 Original Estimate: 72h Remaining Estimate: 72h the cpvm and ssvm can not start ,the state is still starting.
[jira] [Comment Edited] (CLOUDSTACK-3316) the cpvm and ssvm can not start ,the state is still starting
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13699680#comment-13699680 ] terryye edited comment on CLOUDSTACK-3316 at 7/8/13 1:18 AM: - Next replay was (Author: terryye): 2013-07-04 09:17:52,845 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:null) Hosts's actual total CPU: 14392 and CPU after applying overprovisioning: 14392 2013-07-04 09:17:52,845 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:null) Hosts's actual total RAM: 33657663488 and RAM after applying overprovisioning: 33657663488 2013-07-04 09:17:52,845 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:null) release cpu from host: 2, old used: 1000,reserved: 0, actual total: 14392, total with overprovisioning: 14392; new used: 500,reserved:0; movedfromreserved: false,moveToReserveredfalse 2013-07-04 09:17:52,845 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:null) release mem from host: 2, old used: 1342177280,reserved: 0, total: 33657663488; new used: 1073741824,reserved:0; movedfromreserved: false,moveToReserveredfalse 2013-07-04 09:17:52,848 WARN [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Exception while trying to start secondary storage vm com.cloud.exception.AgentUnavailableException: Resource [Host:2] is unreachable: Host 2: Unable to start instance due to Unable to start VM[SecondaryStorageVm|s-15-VM] due to error in finalizeStart, not retrying at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:944) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:557) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:550) at com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(SecondaryStorageManagerImpl.java:260) at com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:683) at com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1290) at com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:123) at com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:50) at com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:104) at com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33) at com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81) at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) Caused by: com.cloud.utils.exception.ExecutionException: Unable to start VM[SecondaryStorageVm|s-15-VM] due to error in finalizeStart, not retrying at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:911) ... 20 more 2013-07-04 09:17:52,849 INFO [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Unable to start secondary storage vm for standby capacity, secStorageVm vm Id : 15, will recycle it and start a new one 2013-07-04 09:17:52,849 INFO [cloud.secstorage.PremiumSecondaryStorageManagerImpl] (secstorage-1:null) Primary secondary storage is not even started, wait until next turn 2013-07-04 09:17:52,868 DEBUG [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone 1 is ready to launch secondary storage VM the cpvm and ssvm can not start ,the state is still starting Key: CLOUDSTACK-3316 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3316 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller, Install and Setup, KVM, Management Server Affects Versions: 4.2.0 Environment: ubuntu12.04 kvm Reporter: terryye Fix For: 4.2.0 Original
[jira] [Commented] (CLOUDSTACK-3316) the cpvm and ssvm can not start ,the state is still starting
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701716#comment-13701716 ] terryye commented on CLOUDSTACK-3316: - 2013-07-08 00:09:24.871+: 2553: error : qemuMonitorIO:603 : internal error End of file from monitor 2013-07-08 00:19:02.151+: 2555: warning : qemuDomainObjTaint:1134 : Domain id=467 name='v-13-VM' uuid=d8847232-7a1c-4042-9b2c-608f0acb5123 is tainted: high-privileges 2013-07-08 00:27:07.459+: 2553: error : qemuMonitorIO:603 : internal error End of file from monitor 2013-07-08 01:07:30.064+: 2777: info : libvirt version: 0.9.8 2013-07-08 01:07:30.064+: 2777: warning : qemuDomainObjTaint:1134 : Domain id=1 name='v-13-VM' uuid=d8847232-7a1c-4042-9b2c-608f0acb5123 is tainted: high-privileges 2013-07-08 01:07:32.960+: 2778: warning : qemuDomainObjTaint:1134 : Domain id=2 name='s-327-VM' uuid=3cc13717-ef14-4b06-96b2-3c215a712354 is tainted: high-privileges 2013-07-08 01:15:38.516+: 2776: error : qemuMonitorIO:603 : internal error End of file from monitor 2013-07-08 01:15:38.820+: 2776: error : qemuMonitorIO:603 : internal error End of file from monitor 2013-07-08 01:15:40.996+: 2778: warning : qemuDomainObjTaint:1134 : Domain id=3 name='v-13-VM' uuid=d8847232-7a1c-4042-9b2c-608f0acb5123 is tainted: high-privileges 2013-07-08 01:15:43.540+: 2779: warning : qemuDomainObjTaint:1134 : Domain id=4 name='s-328-VM' uuid=00de637f-dc30-4a00-b298-e357d98b7932 is tainted: high-privileges the cpvm and ssvm can not start ,the state is still starting Key: CLOUDSTACK-3316 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3316 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller, Install and Setup, KVM, Management Server Affects Versions: 4.2.0 Environment: ubuntu12.04 kvm Reporter: terryye Fix For: 4.2.0 Original Estimate: 72h Remaining Estimate: 72h the cpvm and ssvm can not start ,the state is still starting. It seems the host can not start vm. no errors in the log. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3388) No error message shows when a dedicate operation failed during the creation of a pod/cluster
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isaac Chiang updated CLOUDSTACK-3388: - Attachment: Screenshot-3.png Screenshot-2.png Screenshot-1.png No error message shows when a dedicate operation failed during the creation of a pod/cluster Key: CLOUDSTACK-3388 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3388 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Environment: Master Reporter: Isaac Chiang Labels: ui Attachments: Screenshot-1.png, Screenshot-2.png, Screenshot-3.png There should be a error message when trying to make an explicit dedication to a nonexistent account during the creation of a pod/cluster. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-3388) No error message shows when a dedicate operation failed during the creation of a pod/cluster
Isaac Chiang created CLOUDSTACK-3388: Summary: No error message shows when a dedicate operation failed during the creation of a pod/cluster Key: CLOUDSTACK-3388 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3388 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Environment: Master Reporter: Isaac Chiang Attachments: Screenshot-1.png, Screenshot-2.png, Screenshot-3.png There should be a error message when trying to make an explicit dedication to a nonexistent account during the creation of a pod/cluster. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-2779) [VPC N/W ACL UI]:Unable to define the port range if we specify the protocol number while defining the network ACL rules.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek reassigned CLOUDSTACK-2779: -- Assignee: Pranav Saxena Can you verify this ? [VPC N/W ACL UI]:Unable to define the port range if we specify the protocol number while defining the network ACL rules. Key: CLOUDSTACK-2779 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2779 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Reporter: manasaveloori Assignee: Pranav Saxena Priority: Blocker Fix For: 4.2.0 Steps: 1.Have a CS with advanced zone. 2.Create a VPC and a tier. 3.Create a network ACL list . 4.Try to add the network ACL by specifying the protocol number. Observation: If we select protocol number from “protocol” drop down---there is no option to specify the port range. With API able to specify the port range using protocol number API fired: http://10.147.38.154:8096/client/api?command=createNetworkACLcidrlist=10.10.0.0%2F24action=Allowprotocol=6startport=22endport=22traffictype=Egressaclid=b6508349-26b8-4fe8-9c9d-612a1a28cd2f_=1369977283724. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
