[jira] [Commented] (CLOUDSTACK-6464) [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14525924#comment-14525924 ] Aleksandr commented on CLOUDSTACK-6464: --- I'm very sorry but it was another issue ( i thougth that simptoms are the same at first but no ) I've opened new issue https://issues.apache.org/jira/browse/CLOUDSTACK-8428 [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used -- Key: CLOUDSTACK-6464 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6464 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: sadhu suresh Priority: Critical Fix For: 4.4.0, 4.3.1 Steps: 1. create a KVM basic zone with 2 nics on host (pre 4.3 build) 2.use cloudbr0 for management and cloudbr1 for guest by specifying the traffic labels in the physical networks. 3.deploy few vms 4.upgrade to felton GA build as per the Upgrade instructions. actual result: Upgrade successful but all the vnets that were attached to cloudbr1 before upgrade are attached to cloudbr0. Due to this network connectivity is lost. Expected result: Even after upgrade ,all the vnets should be attached to the same bridge as before upgrade. ex: before Upgrade : this vms(i-5-616-VM) nic was attached to cloudbr1 and after upgrade and VM stop/start. the network rules are getting programmed in cloudbr0 .check below output ,984 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Executing: /usr/share/cloudstack-common/scripts/vm/network/security_group.py default_network_rules --vmname i-5-616-VM --vmid 616 --vmip 10.x.x245 --vmmac 06:14:48:00:00:7f --vif vnet15 --brname cloudbr0 --nicsecips 0: dumpxml output for i-5-616-VM after upgrade( after VM restart) * virsh # dumpxml 38 domain type='kvm' id='38' namei-5-616-VM/name uuid87557942-1393-49b3-a73e-ae24c40541d1/uuid descriptionOther CentOS (64-bit)/description memory unit='KiB'2097152/memory currentMemory unit='KiB'2097152/currentMemory vcpu placement='static'1/vcpu cputune shares1000/shares /cputune os type arch='x86_64' machine='rhel6.2.0'hvm/type boot dev='cdrom'/ boot dev='hd'/ /os features acpi/ apic/ pae/ /features cpu /cpu clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices emulator/usr/libexec/qemu-kvm/emulator disk type='file' device='disk' driver name='qemu' type='qcow2' cache='none'/ source file='/mnt/041e5d8e-d9c1-346d-aea9-cd9c7b80a211/75544e9d-a4c9-4a94-943e-b20827676a27'/ target dev='hda' bus='ide'/ alias name='ide0-0-0'/ address type='drive' controller='0' bus='0' target='0' unit='0'/ /disk disk type='file' device='cdrom' driver name='qemu' type='raw' cache='none'/ target dev='hdc' bus='ide'/ readonly/ alias name='ide0-1-0'/ address type='drive' controller='0' bus='1' target='0' unit='0'/ /disk controller type='usb' index='0' alias name='usb0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x2'/ /controller controller type='ide' index='0' alias name='ide0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x1'/ /controller interface type='bridge' mac address='06:14:48:00:00:7f'/ source bridge='cloudbr0'/ target dev='vnet15'/ model type='e1000'/ bandwidth inbound average='25600' peak='25600'/ outbound average='25600' peak='25600'/ /bandwidth alias name='net0'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /interface serial type='pty' source path='/dev/pts/12'/ target port='0'/ alias name='serial0'/ /serial console type='pty' tty='/dev/pts/12' source path='/dev/pts/12'/ target type='serial' port='0'/ alias name='serial0'/ /console input type='tablet' bus='usb' alias name='input0'/ /input input type='mouse' bus='ps2'/ graphics type='vnc' port='5912' autoport='yes' listen='10.x.x.3' listen type='address' address='10.147.37.3'/ /graphics video model type='cirrus' vram='9216' heads='1'/ alias name='video0'/ address type='pci' domain='0x' bus='0x00' slot='0x02' function='0x0'/ /video memballoon model='virtio' alias name='balloon0'/ address type='pci' domain='0x' bus='0x00' slot='0x04' function='0x0'/ /memballoon /devices seclabel type='none'/ /domain its also applicable to new vm deployments. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-6464) [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14512689#comment-14512689 ] Aleksandr commented on CLOUDSTACK-6464: --- Hi Issue still here... Cloudstack ver 4.4.2, VR ver 4.4.1, clean install, new instance with default network offering : default isolated with source nat. Just after VR goes up a host logs in and adds another public interface with the same ip and same mac as 1st public interface ( eth2 ) : root@r-28-VM:~# cat /etc/network/interfaces auto lo eth0 eth1 eth2 iface lo inet loopback iface eth0 inet static address 172.17.150.1 netmask 255.255.255.0 iface eth1 inet static address 169.254.1.48 netmask 255.255.0.0 iface eth2 inet static public iface address 185.22.***.*** netmask 255.255.255.0 root@r-28-VM:~# cat /var/log/auth.log | grep eth3 Apr 25 20:00:50 r-28-VM sudo: root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/sbin/ip link show eth3 Apr 25 20:00:50 r-28-VM sudo: root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/sbin/ip addr add dev eth3 185.22.***.***/24 brd + And after that all iptables rules are based on this eth3 Looks like Cloudstack doesnt know that VR already has public iface assigned and he logs in to create it and all iptables rules. [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used -- Key: CLOUDSTACK-6464 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6464 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: sadhu suresh Priority: Critical Fix For: 4.4.0, 4.3.1 Steps: 1. create a KVM basic zone with 2 nics on host (pre 4.3 build) 2.use cloudbr0 for management and cloudbr1 for guest by specifying the traffic labels in the physical networks. 3.deploy few vms 4.upgrade to felton GA build as per the Upgrade instructions. actual result: Upgrade successful but all the vnets that were attached to cloudbr1 before upgrade are attached to cloudbr0. Due to this network connectivity is lost. Expected result: Even after upgrade ,all the vnets should be attached to the same bridge as before upgrade. ex: before Upgrade : this vms(i-5-616-VM) nic was attached to cloudbr1 and after upgrade and VM stop/start. the network rules are getting programmed in cloudbr0 .check below output ,984 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Executing: /usr/share/cloudstack-common/scripts/vm/network/security_group.py default_network_rules --vmname i-5-616-VM --vmid 616 --vmip 10.x.x245 --vmmac 06:14:48:00:00:7f --vif vnet15 --brname cloudbr0 --nicsecips 0: dumpxml output for i-5-616-VM after upgrade( after VM restart) * virsh # dumpxml 38 domain type='kvm' id='38' namei-5-616-VM/name uuid87557942-1393-49b3-a73e-ae24c40541d1/uuid descriptionOther CentOS (64-bit)/description memory unit='KiB'2097152/memory currentMemory unit='KiB'2097152/currentMemory vcpu placement='static'1/vcpu cputune shares1000/shares /cputune os type arch='x86_64' machine='rhel6.2.0'hvm/type boot dev='cdrom'/ boot dev='hd'/ /os features acpi/ apic/ pae/ /features cpu /cpu clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices emulator/usr/libexec/qemu-kvm/emulator disk type='file' device='disk' driver name='qemu' type='qcow2' cache='none'/ source file='/mnt/041e5d8e-d9c1-346d-aea9-cd9c7b80a211/75544e9d-a4c9-4a94-943e-b20827676a27'/ target dev='hda' bus='ide'/ alias name='ide0-0-0'/ address type='drive' controller='0' bus='0' target='0' unit='0'/ /disk disk type='file' device='cdrom' driver name='qemu' type='raw' cache='none'/ target dev='hdc' bus='ide'/ readonly/ alias name='ide0-1-0'/ address type='drive' controller='0' bus='1' target='0' unit='0'/ /disk controller type='usb' index='0' alias name='usb0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x2'/ /controller controller type='ide' index='0' alias name='ide0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x1'/ /controller interface type='bridge' mac address='06:14:48:00:00:7f'/ source bridge='cloudbr0'/ target dev='vnet15'/ model type='e1000'/ bandwidth inbound average='25600' peak='25600'/ outbound average='25600' peak='25600'/ /bandwidth alias name='net0'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /interface
[jira] [Commented] (CLOUDSTACK-6464) [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14019740#comment-14019740 ] Gerolamo Valcamonica commented on CLOUDSTACK-6464: -- Hi, it tooks a bit to me to complete tests, but yes, I can confirm that adding vlan:// in vlan table for untagged rows (as suggested by Marcus Sorensen) and the same fix also for monitoring lan (as suggested by Simon Weller) works for me! After modifying database, I needed to restart management console and each virtual router (starting from monitoring's one) and the problem for me is gone. Thank you all so much [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used -- Key: CLOUDSTACK-6464 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6464 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: sadhu suresh Priority: Critical Fix For: 4.4.0 Steps: 1. create a KVM basic zone with 2 nics on host (pre 4.3 build) 2.use cloudbr0 for management and cloudbr1 for guest by specifying the traffic labels in the physical networks. 3.deploy few vms 4.upgrade to felton GA build as per the Upgrade instructions. actual result: Upgrade successful but all the vnets that were attached to cloudbr1 before upgrade are attached to cloudbr0. Due to this network connectivity is lost. Expected result: Even after upgrade ,all the vnets should be attached to the same bridge as before upgrade. ex: before Upgrade : this vms(i-5-616-VM) nic was attached to cloudbr1 and after upgrade and VM stop/start. the network rules are getting programmed in cloudbr0 .check below output ,984 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Executing: /usr/share/cloudstack-common/scripts/vm/network/security_group.py default_network_rules --vmname i-5-616-VM --vmid 616 --vmip 10.x.x245 --vmmac 06:14:48:00:00:7f --vif vnet15 --brname cloudbr0 --nicsecips 0: dumpxml output for i-5-616-VM after upgrade( after VM restart) * virsh # dumpxml 38 domain type='kvm' id='38' namei-5-616-VM/name uuid87557942-1393-49b3-a73e-ae24c40541d1/uuid descriptionOther CentOS (64-bit)/description memory unit='KiB'2097152/memory currentMemory unit='KiB'2097152/currentMemory vcpu placement='static'1/vcpu cputune shares1000/shares /cputune os type arch='x86_64' machine='rhel6.2.0'hvm/type boot dev='cdrom'/ boot dev='hd'/ /os features acpi/ apic/ pae/ /features cpu /cpu clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices emulator/usr/libexec/qemu-kvm/emulator disk type='file' device='disk' driver name='qemu' type='qcow2' cache='none'/ source file='/mnt/041e5d8e-d9c1-346d-aea9-cd9c7b80a211/75544e9d-a4c9-4a94-943e-b20827676a27'/ target dev='hda' bus='ide'/ alias name='ide0-0-0'/ address type='drive' controller='0' bus='0' target='0' unit='0'/ /disk disk type='file' device='cdrom' driver name='qemu' type='raw' cache='none'/ target dev='hdc' bus='ide'/ readonly/ alias name='ide0-1-0'/ address type='drive' controller='0' bus='1' target='0' unit='0'/ /disk controller type='usb' index='0' alias name='usb0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x2'/ /controller controller type='ide' index='0' alias name='ide0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x1'/ /controller interface type='bridge' mac address='06:14:48:00:00:7f'/ source bridge='cloudbr0'/ target dev='vnet15'/ model type='e1000'/ bandwidth inbound average='25600' peak='25600'/ outbound average='25600' peak='25600'/ /bandwidth alias name='net0'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /interface serial type='pty' source path='/dev/pts/12'/ target port='0'/ alias name='serial0'/ /serial console type='pty' tty='/dev/pts/12' source path='/dev/pts/12'/ target type='serial' port='0'/ alias name='serial0'/ /console input type='tablet' bus='usb' alias name='input0'/ /input input type='mouse' bus='ps2'/ graphics type='vnc' port='5912' autoport='yes' listen='10.x.x.3' listen type='address' address='10.147.37.3'/ /graphics video model type='cirrus' vram='9216' heads='1'/ alias name='video0'/ address type='pci' domain='0x' bus='0x00' slot='0x02' function='0x0'/ /video memballoon model='virtio' alias name='balloon0'/ address type='pci'
[jira] [Commented] (CLOUDSTACK-6464) [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14017734#comment-14017734 ] ASF subversion and git services commented on CLOUDSTACK-6464: - Commit 91391e6779bd25b91a3ca4d014656e24592187eb in cloudstack's branch refs/heads/4.4 from Edison Su [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=91391e6 ] CLOUDSTACK-6464: if guest network type is vlan://untagged, and traffic label is used, kvm agent needs to honor traffic label (cherry picked from commit dfb59cd6cc0292a88cb619e53f34cdb713879ffd) [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used -- Key: CLOUDSTACK-6464 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6464 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: sadhu suresh Priority: Critical Fix For: 4.4.0 Steps: 1. create a KVM basic zone with 2 nics on host (pre 4.3 build) 2.use cloudbr0 for management and cloudbr1 for guest by specifying the traffic labels in the physical networks. 3.deploy few vms 4.upgrade to felton GA build as per the Upgrade instructions. actual result: Upgrade successful but all the vnets that were attached to cloudbr1 before upgrade are attached to cloudbr0. Due to this network connectivity is lost. Expected result: Even after upgrade ,all the vnets should be attached to the same bridge as before upgrade. ex: before Upgrade : this vms(i-5-616-VM) nic was attached to cloudbr1 and after upgrade and VM stop/start. the network rules are getting programmed in cloudbr0 .check below output ,984 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Executing: /usr/share/cloudstack-common/scripts/vm/network/security_group.py default_network_rules --vmname i-5-616-VM --vmid 616 --vmip 10.x.x245 --vmmac 06:14:48:00:00:7f --vif vnet15 --brname cloudbr0 --nicsecips 0: dumpxml output for i-5-616-VM after upgrade( after VM restart) * virsh # dumpxml 38 domain type='kvm' id='38' namei-5-616-VM/name uuid87557942-1393-49b3-a73e-ae24c40541d1/uuid descriptionOther CentOS (64-bit)/description memory unit='KiB'2097152/memory currentMemory unit='KiB'2097152/currentMemory vcpu placement='static'1/vcpu cputune shares1000/shares /cputune os type arch='x86_64' machine='rhel6.2.0'hvm/type boot dev='cdrom'/ boot dev='hd'/ /os features acpi/ apic/ pae/ /features cpu /cpu clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices emulator/usr/libexec/qemu-kvm/emulator disk type='file' device='disk' driver name='qemu' type='qcow2' cache='none'/ source file='/mnt/041e5d8e-d9c1-346d-aea9-cd9c7b80a211/75544e9d-a4c9-4a94-943e-b20827676a27'/ target dev='hda' bus='ide'/ alias name='ide0-0-0'/ address type='drive' controller='0' bus='0' target='0' unit='0'/ /disk disk type='file' device='cdrom' driver name='qemu' type='raw' cache='none'/ target dev='hdc' bus='ide'/ readonly/ alias name='ide0-1-0'/ address type='drive' controller='0' bus='1' target='0' unit='0'/ /disk controller type='usb' index='0' alias name='usb0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x2'/ /controller controller type='ide' index='0' alias name='ide0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x1'/ /controller interface type='bridge' mac address='06:14:48:00:00:7f'/ source bridge='cloudbr0'/ target dev='vnet15'/ model type='e1000'/ bandwidth inbound average='25600' peak='25600'/ outbound average='25600' peak='25600'/ /bandwidth alias name='net0'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /interface serial type='pty' source path='/dev/pts/12'/ target port='0'/ alias name='serial0'/ /serial console type='pty' tty='/dev/pts/12' source path='/dev/pts/12'/ target type='serial' port='0'/ alias name='serial0'/ /console input type='tablet' bus='usb' alias name='input0'/ /input input type='mouse' bus='ps2'/ graphics type='vnc' port='5912' autoport='yes' listen='10.x.x.3' listen type='address' address='10.147.37.3'/ /graphics video model type='cirrus' vram='9216' heads='1'/ alias name='video0'/ address type='pci' domain='0x' bus='0x00' slot='0x02' function='0x0'/ /video memballoon model='virtio' alias name='balloon0'/ address type='pci' domain='0x' bus='0x00'
[jira] [Commented] (CLOUDSTACK-6464) [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14018355#comment-14018355 ] ASF subversion and git services commented on CLOUDSTACK-6464: - Commit 15385948dcdf4c69136e99bf3c602f95fd018f39 in cloudstack's branch refs/heads/4.3 from Edison Su [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=1538594 ] CLOUDSTACK-6464: if guest network type is vlan://untagged, and traffic label is used, kvm agent needs to honor traffic label [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used -- Key: CLOUDSTACK-6464 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6464 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: sadhu suresh Priority: Critical Fix For: 4.4.0 Steps: 1. create a KVM basic zone with 2 nics on host (pre 4.3 build) 2.use cloudbr0 for management and cloudbr1 for guest by specifying the traffic labels in the physical networks. 3.deploy few vms 4.upgrade to felton GA build as per the Upgrade instructions. actual result: Upgrade successful but all the vnets that were attached to cloudbr1 before upgrade are attached to cloudbr0. Due to this network connectivity is lost. Expected result: Even after upgrade ,all the vnets should be attached to the same bridge as before upgrade. ex: before Upgrade : this vms(i-5-616-VM) nic was attached to cloudbr1 and after upgrade and VM stop/start. the network rules are getting programmed in cloudbr0 .check below output ,984 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Executing: /usr/share/cloudstack-common/scripts/vm/network/security_group.py default_network_rules --vmname i-5-616-VM --vmid 616 --vmip 10.x.x245 --vmmac 06:14:48:00:00:7f --vif vnet15 --brname cloudbr0 --nicsecips 0: dumpxml output for i-5-616-VM after upgrade( after VM restart) * virsh # dumpxml 38 domain type='kvm' id='38' namei-5-616-VM/name uuid87557942-1393-49b3-a73e-ae24c40541d1/uuid descriptionOther CentOS (64-bit)/description memory unit='KiB'2097152/memory currentMemory unit='KiB'2097152/currentMemory vcpu placement='static'1/vcpu cputune shares1000/shares /cputune os type arch='x86_64' machine='rhel6.2.0'hvm/type boot dev='cdrom'/ boot dev='hd'/ /os features acpi/ apic/ pae/ /features cpu /cpu clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices emulator/usr/libexec/qemu-kvm/emulator disk type='file' device='disk' driver name='qemu' type='qcow2' cache='none'/ source file='/mnt/041e5d8e-d9c1-346d-aea9-cd9c7b80a211/75544e9d-a4c9-4a94-943e-b20827676a27'/ target dev='hda' bus='ide'/ alias name='ide0-0-0'/ address type='drive' controller='0' bus='0' target='0' unit='0'/ /disk disk type='file' device='cdrom' driver name='qemu' type='raw' cache='none'/ target dev='hdc' bus='ide'/ readonly/ alias name='ide0-1-0'/ address type='drive' controller='0' bus='1' target='0' unit='0'/ /disk controller type='usb' index='0' alias name='usb0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x2'/ /controller controller type='ide' index='0' alias name='ide0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x1'/ /controller interface type='bridge' mac address='06:14:48:00:00:7f'/ source bridge='cloudbr0'/ target dev='vnet15'/ model type='e1000'/ bandwidth inbound average='25600' peak='25600'/ outbound average='25600' peak='25600'/ /bandwidth alias name='net0'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /interface serial type='pty' source path='/dev/pts/12'/ target port='0'/ alias name='serial0'/ /serial console type='pty' tty='/dev/pts/12' source path='/dev/pts/12'/ target type='serial' port='0'/ alias name='serial0'/ /console input type='tablet' bus='usb' alias name='input0'/ /input input type='mouse' bus='ps2'/ graphics type='vnc' port='5912' autoport='yes' listen='10.x.x.3' listen type='address' address='10.147.37.3'/ /graphics video model type='cirrus' vram='9216' heads='1'/ alias name='video0'/ address type='pci' domain='0x' bus='0x00' slot='0x02' function='0x0'/ /video memballoon model='virtio' alias name='balloon0'/ address type='pci' domain='0x' bus='0x00' slot='0x04' function='0x0'/ /memballoon /devices seclabel
[jira] [Commented] (CLOUDSTACK-6464) [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14018502#comment-14018502 ] Simon Weller commented on CLOUDSTACK-6464: -- After reading the comments from Marcus on the vlan table, I took a look at my vlan table in my lab, and noticed the vlan_id just displayed the vlan (22). So I changed that to vlan://22, restarted the management server, then restarted a project virtual router pair. The network assignments appeared to be normal on router startup. I then acquired a new ip to the network assigned it to a LB rule and added a VM. The alias was correctly assigned to eth2 (my public interface). I then removed the ip, and the ip was correctly removed from eth2. I'll do a bit more testing after I get back from vacation, but at the current time this certainly appears to fix the issue I was experiencing. - Si [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used -- Key: CLOUDSTACK-6464 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6464 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: sadhu suresh Priority: Critical Fix For: 4.4.0 Steps: 1. create a KVM basic zone with 2 nics on host (pre 4.3 build) 2.use cloudbr0 for management and cloudbr1 for guest by specifying the traffic labels in the physical networks. 3.deploy few vms 4.upgrade to felton GA build as per the Upgrade instructions. actual result: Upgrade successful but all the vnets that were attached to cloudbr1 before upgrade are attached to cloudbr0. Due to this network connectivity is lost. Expected result: Even after upgrade ,all the vnets should be attached to the same bridge as before upgrade. ex: before Upgrade : this vms(i-5-616-VM) nic was attached to cloudbr1 and after upgrade and VM stop/start. the network rules are getting programmed in cloudbr0 .check below output ,984 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Executing: /usr/share/cloudstack-common/scripts/vm/network/security_group.py default_network_rules --vmname i-5-616-VM --vmid 616 --vmip 10.x.x245 --vmmac 06:14:48:00:00:7f --vif vnet15 --brname cloudbr0 --nicsecips 0: dumpxml output for i-5-616-VM after upgrade( after VM restart) * virsh # dumpxml 38 domain type='kvm' id='38' namei-5-616-VM/name uuid87557942-1393-49b3-a73e-ae24c40541d1/uuid descriptionOther CentOS (64-bit)/description memory unit='KiB'2097152/memory currentMemory unit='KiB'2097152/currentMemory vcpu placement='static'1/vcpu cputune shares1000/shares /cputune os type arch='x86_64' machine='rhel6.2.0'hvm/type boot dev='cdrom'/ boot dev='hd'/ /os features acpi/ apic/ pae/ /features cpu /cpu clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices emulator/usr/libexec/qemu-kvm/emulator disk type='file' device='disk' driver name='qemu' type='qcow2' cache='none'/ source file='/mnt/041e5d8e-d9c1-346d-aea9-cd9c7b80a211/75544e9d-a4c9-4a94-943e-b20827676a27'/ target dev='hda' bus='ide'/ alias name='ide0-0-0'/ address type='drive' controller='0' bus='0' target='0' unit='0'/ /disk disk type='file' device='cdrom' driver name='qemu' type='raw' cache='none'/ target dev='hdc' bus='ide'/ readonly/ alias name='ide0-1-0'/ address type='drive' controller='0' bus='1' target='0' unit='0'/ /disk controller type='usb' index='0' alias name='usb0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x2'/ /controller controller type='ide' index='0' alias name='ide0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x1'/ /controller interface type='bridge' mac address='06:14:48:00:00:7f'/ source bridge='cloudbr0'/ target dev='vnet15'/ model type='e1000'/ bandwidth inbound average='25600' peak='25600'/ outbound average='25600' peak='25600'/ /bandwidth alias name='net0'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /interface serial type='pty' source path='/dev/pts/12'/ target port='0'/ alias name='serial0'/ /serial console type='pty' tty='/dev/pts/12' source path='/dev/pts/12'/ target type='serial' port='0'/ alias name='serial0'/ /console input type='tablet' bus='usb' alias name='input0'/ /input input type='mouse' bus='ps2'/ graphics type='vnc' port='5912' autoport='yes' listen='10.x.x.3' listen type='address'
[jira] [Commented] (CLOUDSTACK-6464) [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14016522#comment-14016522 ] Gerolamo Valcamonica commented on CLOUDSTACK-6464: -- It's worse than I described 2 days ago: we have advanced networking and every time we apply a new rule to a guest network (i.e. adding a new static route, open or close a port on firewall, ..) the router hangs, VMs become unreachable and the quicker solution is to restart the router and re-apply Bob's workaround In addition, some rules seems not to works: i.e. FTP server in a guest VM become unreachable either in active and in passive mode and the only workaround we found is to modprobe nf_conntrack_ftp and ip_nat_ftp on the VR. FTP worked correctly before upgrading to 4.3 It seems to me that Cloudstack Devs needs to give a clear message to the world: YOU CANNOT UPGRADE TO CLOUDSTACK 4.3 IF YOU ARE USING TRAFFIC LABELS IN YOUR NETWORK SETUP do you agree, Devs? [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used -- Key: CLOUDSTACK-6464 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6464 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: sadhu suresh Priority: Critical Fix For: 4.4.0 Steps: 1. create a KVM basic zone with 2 nics on host (pre 4.3 build) 2.use cloudbr0 for management and cloudbr1 for guest by specifying the traffic labels in the physical networks. 3.deploy few vms 4.upgrade to felton GA build as per the Upgrade instructions. actual result: Upgrade successful but all the vnets that were attached to cloudbr1 before upgrade are attached to cloudbr0. Due to this network connectivity is lost. Expected result: Even after upgrade ,all the vnets should be attached to the same bridge as before upgrade. ex: before Upgrade : this vms(i-5-616-VM) nic was attached to cloudbr1 and after upgrade and VM stop/start. the network rules are getting programmed in cloudbr0 .check below output ,984 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Executing: /usr/share/cloudstack-common/scripts/vm/network/security_group.py default_network_rules --vmname i-5-616-VM --vmid 616 --vmip 10.x.x245 --vmmac 06:14:48:00:00:7f --vif vnet15 --brname cloudbr0 --nicsecips 0: dumpxml output for i-5-616-VM after upgrade( after VM restart) * virsh # dumpxml 38 domain type='kvm' id='38' namei-5-616-VM/name uuid87557942-1393-49b3-a73e-ae24c40541d1/uuid descriptionOther CentOS (64-bit)/description memory unit='KiB'2097152/memory currentMemory unit='KiB'2097152/currentMemory vcpu placement='static'1/vcpu cputune shares1000/shares /cputune os type arch='x86_64' machine='rhel6.2.0'hvm/type boot dev='cdrom'/ boot dev='hd'/ /os features acpi/ apic/ pae/ /features cpu /cpu clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices emulator/usr/libexec/qemu-kvm/emulator disk type='file' device='disk' driver name='qemu' type='qcow2' cache='none'/ source file='/mnt/041e5d8e-d9c1-346d-aea9-cd9c7b80a211/75544e9d-a4c9-4a94-943e-b20827676a27'/ target dev='hda' bus='ide'/ alias name='ide0-0-0'/ address type='drive' controller='0' bus='0' target='0' unit='0'/ /disk disk type='file' device='cdrom' driver name='qemu' type='raw' cache='none'/ target dev='hdc' bus='ide'/ readonly/ alias name='ide0-1-0'/ address type='drive' controller='0' bus='1' target='0' unit='0'/ /disk controller type='usb' index='0' alias name='usb0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x2'/ /controller controller type='ide' index='0' alias name='ide0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x1'/ /controller interface type='bridge' mac address='06:14:48:00:00:7f'/ source bridge='cloudbr0'/ target dev='vnet15'/ model type='e1000'/ bandwidth inbound average='25600' peak='25600'/ outbound average='25600' peak='25600'/ /bandwidth alias name='net0'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /interface serial type='pty' source path='/dev/pts/12'/ target port='0'/ alias name='serial0'/ /serial console type='pty' tty='/dev/pts/12' source path='/dev/pts/12'/ target type='serial' port='0'/ alias name='serial0'/ /console input type='tablet' bus='usb' alias name='input0'/ /input input type='mouse'
[jira] [Commented] (CLOUDSTACK-6464) [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14016580#comment-14016580 ] Andrija Panic commented on CLOUDSTACK-6464: --- Can you check your agent conf if there are changes to it ? I also use advanced zone, kvm traffic labels, and I don't have this bug for some reason... [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used -- Key: CLOUDSTACK-6464 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6464 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: sadhu suresh Priority: Critical Fix For: 4.4.0 Steps: 1. create a KVM basic zone with 2 nics on host (pre 4.3 build) 2.use cloudbr0 for management and cloudbr1 for guest by specifying the traffic labels in the physical networks. 3.deploy few vms 4.upgrade to felton GA build as per the Upgrade instructions. actual result: Upgrade successful but all the vnets that were attached to cloudbr1 before upgrade are attached to cloudbr0. Due to this network connectivity is lost. Expected result: Even after upgrade ,all the vnets should be attached to the same bridge as before upgrade. ex: before Upgrade : this vms(i-5-616-VM) nic was attached to cloudbr1 and after upgrade and VM stop/start. the network rules are getting programmed in cloudbr0 .check below output ,984 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Executing: /usr/share/cloudstack-common/scripts/vm/network/security_group.py default_network_rules --vmname i-5-616-VM --vmid 616 --vmip 10.x.x245 --vmmac 06:14:48:00:00:7f --vif vnet15 --brname cloudbr0 --nicsecips 0: dumpxml output for i-5-616-VM after upgrade( after VM restart) * virsh # dumpxml 38 domain type='kvm' id='38' namei-5-616-VM/name uuid87557942-1393-49b3-a73e-ae24c40541d1/uuid descriptionOther CentOS (64-bit)/description memory unit='KiB'2097152/memory currentMemory unit='KiB'2097152/currentMemory vcpu placement='static'1/vcpu cputune shares1000/shares /cputune os type arch='x86_64' machine='rhel6.2.0'hvm/type boot dev='cdrom'/ boot dev='hd'/ /os features acpi/ apic/ pae/ /features cpu /cpu clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices emulator/usr/libexec/qemu-kvm/emulator disk type='file' device='disk' driver name='qemu' type='qcow2' cache='none'/ source file='/mnt/041e5d8e-d9c1-346d-aea9-cd9c7b80a211/75544e9d-a4c9-4a94-943e-b20827676a27'/ target dev='hda' bus='ide'/ alias name='ide0-0-0'/ address type='drive' controller='0' bus='0' target='0' unit='0'/ /disk disk type='file' device='cdrom' driver name='qemu' type='raw' cache='none'/ target dev='hdc' bus='ide'/ readonly/ alias name='ide0-1-0'/ address type='drive' controller='0' bus='1' target='0' unit='0'/ /disk controller type='usb' index='0' alias name='usb0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x2'/ /controller controller type='ide' index='0' alias name='ide0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x1'/ /controller interface type='bridge' mac address='06:14:48:00:00:7f'/ source bridge='cloudbr0'/ target dev='vnet15'/ model type='e1000'/ bandwidth inbound average='25600' peak='25600'/ outbound average='25600' peak='25600'/ /bandwidth alias name='net0'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /interface serial type='pty' source path='/dev/pts/12'/ target port='0'/ alias name='serial0'/ /serial console type='pty' tty='/dev/pts/12' source path='/dev/pts/12'/ target type='serial' port='0'/ alias name='serial0'/ /console input type='tablet' bus='usb' alias name='input0'/ /input input type='mouse' bus='ps2'/ graphics type='vnc' port='5912' autoport='yes' listen='10.x.x.3' listen type='address' address='10.147.37.3'/ /graphics video model type='cirrus' vram='9216' heads='1'/ alias name='video0'/ address type='pci' domain='0x' bus='0x00' slot='0x02' function='0x0'/ /video memballoon model='virtio' alias name='balloon0'/ address type='pci' domain='0x' bus='0x00' slot='0x04' function='0x0'/ /memballoon /devices seclabel type='none'/ /domain its also applicable to new vm deployments. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6464) [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14016597#comment-14016597 ] Marcus Sorensen commented on CLOUDSTACK-6464: - This is a shot in the dark, but there have been some issues around upgrades that involve the cloud.vlan table expected contents changing. New 4.3 installs using vlan isolation don't seem to reproduce the issue. I'll see if I can reproduce anything like this with basic and/or non-vlan isolated upgrades/installs. Can anyone experiencing an issue look at their database via something like select * from cloud.vlan and look at the vlan_id. If you see something like untagged instead of vlan://untagged, please try changing it and see if that helps. I should note as well that it sounds like there might be several different issues represented here. [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used -- Key: CLOUDSTACK-6464 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6464 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: sadhu suresh Priority: Critical Fix For: 4.4.0 Steps: 1. create a KVM basic zone with 2 nics on host (pre 4.3 build) 2.use cloudbr0 for management and cloudbr1 for guest by specifying the traffic labels in the physical networks. 3.deploy few vms 4.upgrade to felton GA build as per the Upgrade instructions. actual result: Upgrade successful but all the vnets that were attached to cloudbr1 before upgrade are attached to cloudbr0. Due to this network connectivity is lost. Expected result: Even after upgrade ,all the vnets should be attached to the same bridge as before upgrade. ex: before Upgrade : this vms(i-5-616-VM) nic was attached to cloudbr1 and after upgrade and VM stop/start. the network rules are getting programmed in cloudbr0 .check below output ,984 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Executing: /usr/share/cloudstack-common/scripts/vm/network/security_group.py default_network_rules --vmname i-5-616-VM --vmid 616 --vmip 10.x.x245 --vmmac 06:14:48:00:00:7f --vif vnet15 --brname cloudbr0 --nicsecips 0: dumpxml output for i-5-616-VM after upgrade( after VM restart) * virsh # dumpxml 38 domain type='kvm' id='38' namei-5-616-VM/name uuid87557942-1393-49b3-a73e-ae24c40541d1/uuid descriptionOther CentOS (64-bit)/description memory unit='KiB'2097152/memory currentMemory unit='KiB'2097152/currentMemory vcpu placement='static'1/vcpu cputune shares1000/shares /cputune os type arch='x86_64' machine='rhel6.2.0'hvm/type boot dev='cdrom'/ boot dev='hd'/ /os features acpi/ apic/ pae/ /features cpu /cpu clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices emulator/usr/libexec/qemu-kvm/emulator disk type='file' device='disk' driver name='qemu' type='qcow2' cache='none'/ source file='/mnt/041e5d8e-d9c1-346d-aea9-cd9c7b80a211/75544e9d-a4c9-4a94-943e-b20827676a27'/ target dev='hda' bus='ide'/ alias name='ide0-0-0'/ address type='drive' controller='0' bus='0' target='0' unit='0'/ /disk disk type='file' device='cdrom' driver name='qemu' type='raw' cache='none'/ target dev='hdc' bus='ide'/ readonly/ alias name='ide0-1-0'/ address type='drive' controller='0' bus='1' target='0' unit='0'/ /disk controller type='usb' index='0' alias name='usb0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x2'/ /controller controller type='ide' index='0' alias name='ide0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x1'/ /controller interface type='bridge' mac address='06:14:48:00:00:7f'/ source bridge='cloudbr0'/ target dev='vnet15'/ model type='e1000'/ bandwidth inbound average='25600' peak='25600'/ outbound average='25600' peak='25600'/ /bandwidth alias name='net0'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /interface serial type='pty' source path='/dev/pts/12'/ target port='0'/ alias name='serial0'/ /serial console type='pty' tty='/dev/pts/12' source path='/dev/pts/12'/ target type='serial' port='0'/ alias name='serial0'/ /console input type='tablet' bus='usb' alias name='input0'/ /input input type='mouse' bus='ps2'/ graphics type='vnc' port='5912' autoport='yes' listen='10.x.x.3' listen type='address' address='10.147.37.3'/ /graphics
[jira] [Commented] (CLOUDSTACK-6464) [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14016864#comment-14016864 ] Marcus Sorensen commented on CLOUDSTACK-6464: - See my comment on https://reviews.apache.org/r/21908/ If this chunk of code solves the issue, then it IS in fact related to the cloud.vlan table's vlan_id issue that Daan and I are discussing, and yet another place where the mgmt server passes broadcastUri in one format for one Command and in another format for a different Command. Generally we've seen these getting fixed by updating the vlan table and prepending vlan:// to each item, but we're still discussing whether or not that's a good permanent solution. [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used -- Key: CLOUDSTACK-6464 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6464 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: sadhu suresh Priority: Critical Fix For: 4.4.0 Steps: 1. create a KVM basic zone with 2 nics on host (pre 4.3 build) 2.use cloudbr0 for management and cloudbr1 for guest by specifying the traffic labels in the physical networks. 3.deploy few vms 4.upgrade to felton GA build as per the Upgrade instructions. actual result: Upgrade successful but all the vnets that were attached to cloudbr1 before upgrade are attached to cloudbr0. Due to this network connectivity is lost. Expected result: Even after upgrade ,all the vnets should be attached to the same bridge as before upgrade. ex: before Upgrade : this vms(i-5-616-VM) nic was attached to cloudbr1 and after upgrade and VM stop/start. the network rules are getting programmed in cloudbr0 .check below output ,984 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Executing: /usr/share/cloudstack-common/scripts/vm/network/security_group.py default_network_rules --vmname i-5-616-VM --vmid 616 --vmip 10.x.x245 --vmmac 06:14:48:00:00:7f --vif vnet15 --brname cloudbr0 --nicsecips 0: dumpxml output for i-5-616-VM after upgrade( after VM restart) * virsh # dumpxml 38 domain type='kvm' id='38' namei-5-616-VM/name uuid87557942-1393-49b3-a73e-ae24c40541d1/uuid descriptionOther CentOS (64-bit)/description memory unit='KiB'2097152/memory currentMemory unit='KiB'2097152/currentMemory vcpu placement='static'1/vcpu cputune shares1000/shares /cputune os type arch='x86_64' machine='rhel6.2.0'hvm/type boot dev='cdrom'/ boot dev='hd'/ /os features acpi/ apic/ pae/ /features cpu /cpu clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices emulator/usr/libexec/qemu-kvm/emulator disk type='file' device='disk' driver name='qemu' type='qcow2' cache='none'/ source file='/mnt/041e5d8e-d9c1-346d-aea9-cd9c7b80a211/75544e9d-a4c9-4a94-943e-b20827676a27'/ target dev='hda' bus='ide'/ alias name='ide0-0-0'/ address type='drive' controller='0' bus='0' target='0' unit='0'/ /disk disk type='file' device='cdrom' driver name='qemu' type='raw' cache='none'/ target dev='hdc' bus='ide'/ readonly/ alias name='ide0-1-0'/ address type='drive' controller='0' bus='1' target='0' unit='0'/ /disk controller type='usb' index='0' alias name='usb0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x2'/ /controller controller type='ide' index='0' alias name='ide0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x1'/ /controller interface type='bridge' mac address='06:14:48:00:00:7f'/ source bridge='cloudbr0'/ target dev='vnet15'/ model type='e1000'/ bandwidth inbound average='25600' peak='25600'/ outbound average='25600' peak='25600'/ /bandwidth alias name='net0'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /interface serial type='pty' source path='/dev/pts/12'/ target port='0'/ alias name='serial0'/ /serial console type='pty' tty='/dev/pts/12' source path='/dev/pts/12'/ target type='serial' port='0'/ alias name='serial0'/ /console input type='tablet' bus='usb' alias name='input0'/ /input input type='mouse' bus='ps2'/ graphics type='vnc' port='5912' autoport='yes' listen='10.x.x.3' listen type='address' address='10.147.37.3'/ /graphics video model type='cirrus' vram='9216' heads='1'/ alias name='video0'/ address type='pci' domain='0x' bus='0x00' slot='0x02'
[jira] [Commented] (CLOUDSTACK-6464) [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14016888#comment-14016888 ] Marcus Sorensen commented on CLOUDSTACK-6464: - Bob, I think your issue is related, but different. I'm trying to reproduce that now. [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used -- Key: CLOUDSTACK-6464 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6464 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: sadhu suresh Priority: Critical Fix For: 4.4.0 Steps: 1. create a KVM basic zone with 2 nics on host (pre 4.3 build) 2.use cloudbr0 for management and cloudbr1 for guest by specifying the traffic labels in the physical networks. 3.deploy few vms 4.upgrade to felton GA build as per the Upgrade instructions. actual result: Upgrade successful but all the vnets that were attached to cloudbr1 before upgrade are attached to cloudbr0. Due to this network connectivity is lost. Expected result: Even after upgrade ,all the vnets should be attached to the same bridge as before upgrade. ex: before Upgrade : this vms(i-5-616-VM) nic was attached to cloudbr1 and after upgrade and VM stop/start. the network rules are getting programmed in cloudbr0 .check below output ,984 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Executing: /usr/share/cloudstack-common/scripts/vm/network/security_group.py default_network_rules --vmname i-5-616-VM --vmid 616 --vmip 10.x.x245 --vmmac 06:14:48:00:00:7f --vif vnet15 --brname cloudbr0 --nicsecips 0: dumpxml output for i-5-616-VM after upgrade( after VM restart) * virsh # dumpxml 38 domain type='kvm' id='38' namei-5-616-VM/name uuid87557942-1393-49b3-a73e-ae24c40541d1/uuid descriptionOther CentOS (64-bit)/description memory unit='KiB'2097152/memory currentMemory unit='KiB'2097152/currentMemory vcpu placement='static'1/vcpu cputune shares1000/shares /cputune os type arch='x86_64' machine='rhel6.2.0'hvm/type boot dev='cdrom'/ boot dev='hd'/ /os features acpi/ apic/ pae/ /features cpu /cpu clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices emulator/usr/libexec/qemu-kvm/emulator disk type='file' device='disk' driver name='qemu' type='qcow2' cache='none'/ source file='/mnt/041e5d8e-d9c1-346d-aea9-cd9c7b80a211/75544e9d-a4c9-4a94-943e-b20827676a27'/ target dev='hda' bus='ide'/ alias name='ide0-0-0'/ address type='drive' controller='0' bus='0' target='0' unit='0'/ /disk disk type='file' device='cdrom' driver name='qemu' type='raw' cache='none'/ target dev='hdc' bus='ide'/ readonly/ alias name='ide0-1-0'/ address type='drive' controller='0' bus='1' target='0' unit='0'/ /disk controller type='usb' index='0' alias name='usb0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x2'/ /controller controller type='ide' index='0' alias name='ide0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x1'/ /controller interface type='bridge' mac address='06:14:48:00:00:7f'/ source bridge='cloudbr0'/ target dev='vnet15'/ model type='e1000'/ bandwidth inbound average='25600' peak='25600'/ outbound average='25600' peak='25600'/ /bandwidth alias name='net0'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /interface serial type='pty' source path='/dev/pts/12'/ target port='0'/ alias name='serial0'/ /serial console type='pty' tty='/dev/pts/12' source path='/dev/pts/12'/ target type='serial' port='0'/ alias name='serial0'/ /console input type='tablet' bus='usb' alias name='input0'/ /input input type='mouse' bus='ps2'/ graphics type='vnc' port='5912' autoport='yes' listen='10.x.x.3' listen type='address' address='10.147.37.3'/ /graphics video model type='cirrus' vram='9216' heads='1'/ alias name='video0'/ address type='pci' domain='0x' bus='0x00' slot='0x02' function='0x0'/ /video memballoon model='virtio' alias name='balloon0'/ address type='pci' domain='0x' bus='0x00' slot='0x04' function='0x0'/ /memballoon /devices seclabel type='none'/ /domain its also applicable to new vm deployments. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6464) [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14016911#comment-14016911 ] Marcus Sorensen commented on CLOUDSTACK-6464: - Bob, unfortunately, I cannot reproduce the issue given the info provided. I did a fresh 4.3 install with cloudbr0 and cloudbr1, with cloudbr0 hosting an untagged mgmt network and guest networks (vlan isolated), while cloudbr1 was untagged public network. I deployed an isolated network router as well as VPC router with one isolated network, and only got the expected networks. Then I added vms to the isolated networks on both of these, added static nats to them, rebooted the routers, and never got the situation you describe. If you'd be willing to create a separate bug and document the steps to reproduce from fresh install, that would help significantly. [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used -- Key: CLOUDSTACK-6464 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6464 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: sadhu suresh Priority: Critical Fix For: 4.4.0 Steps: 1. create a KVM basic zone with 2 nics on host (pre 4.3 build) 2.use cloudbr0 for management and cloudbr1 for guest by specifying the traffic labels in the physical networks. 3.deploy few vms 4.upgrade to felton GA build as per the Upgrade instructions. actual result: Upgrade successful but all the vnets that were attached to cloudbr1 before upgrade are attached to cloudbr0. Due to this network connectivity is lost. Expected result: Even after upgrade ,all the vnets should be attached to the same bridge as before upgrade. ex: before Upgrade : this vms(i-5-616-VM) nic was attached to cloudbr1 and after upgrade and VM stop/start. the network rules are getting programmed in cloudbr0 .check below output ,984 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Executing: /usr/share/cloudstack-common/scripts/vm/network/security_group.py default_network_rules --vmname i-5-616-VM --vmid 616 --vmip 10.x.x245 --vmmac 06:14:48:00:00:7f --vif vnet15 --brname cloudbr0 --nicsecips 0: dumpxml output for i-5-616-VM after upgrade( after VM restart) * virsh # dumpxml 38 domain type='kvm' id='38' namei-5-616-VM/name uuid87557942-1393-49b3-a73e-ae24c40541d1/uuid descriptionOther CentOS (64-bit)/description memory unit='KiB'2097152/memory currentMemory unit='KiB'2097152/currentMemory vcpu placement='static'1/vcpu cputune shares1000/shares /cputune os type arch='x86_64' machine='rhel6.2.0'hvm/type boot dev='cdrom'/ boot dev='hd'/ /os features acpi/ apic/ pae/ /features cpu /cpu clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices emulator/usr/libexec/qemu-kvm/emulator disk type='file' device='disk' driver name='qemu' type='qcow2' cache='none'/ source file='/mnt/041e5d8e-d9c1-346d-aea9-cd9c7b80a211/75544e9d-a4c9-4a94-943e-b20827676a27'/ target dev='hda' bus='ide'/ alias name='ide0-0-0'/ address type='drive' controller='0' bus='0' target='0' unit='0'/ /disk disk type='file' device='cdrom' driver name='qemu' type='raw' cache='none'/ target dev='hdc' bus='ide'/ readonly/ alias name='ide0-1-0'/ address type='drive' controller='0' bus='1' target='0' unit='0'/ /disk controller type='usb' index='0' alias name='usb0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x2'/ /controller controller type='ide' index='0' alias name='ide0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x1'/ /controller interface type='bridge' mac address='06:14:48:00:00:7f'/ source bridge='cloudbr0'/ target dev='vnet15'/ model type='e1000'/ bandwidth inbound average='25600' peak='25600'/ outbound average='25600' peak='25600'/ /bandwidth alias name='net0'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /interface serial type='pty' source path='/dev/pts/12'/ target port='0'/ alias name='serial0'/ /serial console type='pty' tty='/dev/pts/12' source path='/dev/pts/12'/ target type='serial' port='0'/ alias name='serial0'/ /console input type='tablet' bus='usb' alias name='input0'/ /input input type='mouse' bus='ps2'/ graphics type='vnc' port='5912' autoport='yes' listen='10.x.x.3' listen type='address' address='10.147.37.3'/
[jira] [Commented] (CLOUDSTACK-6464) [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14016919#comment-14016919 ] Bob Vanderford commented on CLOUDSTACK-6464: Marcus, thanks much for investigating. Two physical nics, eth0 and eth1. No VPC. It is an isolated network using vlans. The OS is CentOS6.5 minimal. The compute nodes have 2 physical nics. Eth0 is running the storage and management networks, with an untagged vlan and the bridge I named mgmt bridged to eth0. Eth1 is running the guest and public network. The public bridge I named breth1-20 and it runs over vlan 20. The guest bridge I named cloudbr1 and the vlans are 100-150. All these are of course tagged vlans on the compute nodes. If you need more detail let me know. I can provide the actual network configs if needed but they are pretty straightforward and probably what you would expect. It would not surprise me if there are more than one issue among the posts. If mine is difficult to reproduce, I can provide access to the management interface for my setup. I would have to rebuild it though since I am currently trying version 4.2, trying to get amysta installed and amysta is requiring version 4.2 or else for me to compile in a usage patch for 4.3. Decided just to try 4.2. But, I am willing, if needed to rebuild the 4.3 setup as I had it, give me a few hours for that if needed. [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used -- Key: CLOUDSTACK-6464 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6464 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: sadhu suresh Priority: Critical Fix For: 4.4.0 Steps: 1. create a KVM basic zone with 2 nics on host (pre 4.3 build) 2.use cloudbr0 for management and cloudbr1 for guest by specifying the traffic labels in the physical networks. 3.deploy few vms 4.upgrade to felton GA build as per the Upgrade instructions. actual result: Upgrade successful but all the vnets that were attached to cloudbr1 before upgrade are attached to cloudbr0. Due to this network connectivity is lost. Expected result: Even after upgrade ,all the vnets should be attached to the same bridge as before upgrade. ex: before Upgrade : this vms(i-5-616-VM) nic was attached to cloudbr1 and after upgrade and VM stop/start. the network rules are getting programmed in cloudbr0 .check below output ,984 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Executing: /usr/share/cloudstack-common/scripts/vm/network/security_group.py default_network_rules --vmname i-5-616-VM --vmid 616 --vmip 10.x.x245 --vmmac 06:14:48:00:00:7f --vif vnet15 --brname cloudbr0 --nicsecips 0: dumpxml output for i-5-616-VM after upgrade( after VM restart) * virsh # dumpxml 38 domain type='kvm' id='38' namei-5-616-VM/name uuid87557942-1393-49b3-a73e-ae24c40541d1/uuid descriptionOther CentOS (64-bit)/description memory unit='KiB'2097152/memory currentMemory unit='KiB'2097152/currentMemory vcpu placement='static'1/vcpu cputune shares1000/shares /cputune os type arch='x86_64' machine='rhel6.2.0'hvm/type boot dev='cdrom'/ boot dev='hd'/ /os features acpi/ apic/ pae/ /features cpu /cpu clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices emulator/usr/libexec/qemu-kvm/emulator disk type='file' device='disk' driver name='qemu' type='qcow2' cache='none'/ source file='/mnt/041e5d8e-d9c1-346d-aea9-cd9c7b80a211/75544e9d-a4c9-4a94-943e-b20827676a27'/ target dev='hda' bus='ide'/ alias name='ide0-0-0'/ address type='drive' controller='0' bus='0' target='0' unit='0'/ /disk disk type='file' device='cdrom' driver name='qemu' type='raw' cache='none'/ target dev='hdc' bus='ide'/ readonly/ alias name='ide0-1-0'/ address type='drive' controller='0' bus='1' target='0' unit='0'/ /disk controller type='usb' index='0' alias name='usb0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x2'/ /controller controller type='ide' index='0' alias name='ide0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x1'/ /controller interface type='bridge' mac address='06:14:48:00:00:7f'/ source bridge='cloudbr0'/ target dev='vnet15'/ model type='e1000'/ bandwidth inbound average='25600' peak='25600'/ outbound average='25600'
[jira] [Commented] (CLOUDSTACK-6464) [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14017100#comment-14017100 ] edison su commented on CLOUDSTACK-6464: --- Back to issue itself: guest network bridge is changed after upgrade to 4.x, if guest network is using vlan://untagged. The root cause is that, in 3.0.x, if guest network is vlan://untagged, then kvm agent will use whatever value in private.network.device, while in 4.x, kvm agent will use guest.network.device. So if both value are not the same in the agent.properties, then kvm agent will use incorrect bridge to create vif. The fix will be, kvm agent code needs to honor traffic type passed down from mgt server in startcommand, in case of vlan://untagged. [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used -- Key: CLOUDSTACK-6464 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6464 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: sadhu suresh Priority: Critical Fix For: 4.4.0 Steps: 1. create a KVM basic zone with 2 nics on host (pre 4.3 build) 2.use cloudbr0 for management and cloudbr1 for guest by specifying the traffic labels in the physical networks. 3.deploy few vms 4.upgrade to felton GA build as per the Upgrade instructions. actual result: Upgrade successful but all the vnets that were attached to cloudbr1 before upgrade are attached to cloudbr0. Due to this network connectivity is lost. Expected result: Even after upgrade ,all the vnets should be attached to the same bridge as before upgrade. ex: before Upgrade : this vms(i-5-616-VM) nic was attached to cloudbr1 and after upgrade and VM stop/start. the network rules are getting programmed in cloudbr0 .check below output ,984 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Executing: /usr/share/cloudstack-common/scripts/vm/network/security_group.py default_network_rules --vmname i-5-616-VM --vmid 616 --vmip 10.x.x245 --vmmac 06:14:48:00:00:7f --vif vnet15 --brname cloudbr0 --nicsecips 0: dumpxml output for i-5-616-VM after upgrade( after VM restart) * virsh # dumpxml 38 domain type='kvm' id='38' namei-5-616-VM/name uuid87557942-1393-49b3-a73e-ae24c40541d1/uuid descriptionOther CentOS (64-bit)/description memory unit='KiB'2097152/memory currentMemory unit='KiB'2097152/currentMemory vcpu placement='static'1/vcpu cputune shares1000/shares /cputune os type arch='x86_64' machine='rhel6.2.0'hvm/type boot dev='cdrom'/ boot dev='hd'/ /os features acpi/ apic/ pae/ /features cpu /cpu clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices emulator/usr/libexec/qemu-kvm/emulator disk type='file' device='disk' driver name='qemu' type='qcow2' cache='none'/ source file='/mnt/041e5d8e-d9c1-346d-aea9-cd9c7b80a211/75544e9d-a4c9-4a94-943e-b20827676a27'/ target dev='hda' bus='ide'/ alias name='ide0-0-0'/ address type='drive' controller='0' bus='0' target='0' unit='0'/ /disk disk type='file' device='cdrom' driver name='qemu' type='raw' cache='none'/ target dev='hdc' bus='ide'/ readonly/ alias name='ide0-1-0'/ address type='drive' controller='0' bus='1' target='0' unit='0'/ /disk controller type='usb' index='0' alias name='usb0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x2'/ /controller controller type='ide' index='0' alias name='ide0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x1'/ /controller interface type='bridge' mac address='06:14:48:00:00:7f'/ source bridge='cloudbr0'/ target dev='vnet15'/ model type='e1000'/ bandwidth inbound average='25600' peak='25600'/ outbound average='25600' peak='25600'/ /bandwidth alias name='net0'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /interface serial type='pty' source path='/dev/pts/12'/ target port='0'/ alias name='serial0'/ /serial console type='pty' tty='/dev/pts/12' source path='/dev/pts/12'/ target type='serial' port='0'/ alias name='serial0'/ /console input type='tablet' bus='usb' alias name='input0'/ /input input type='mouse' bus='ps2'/ graphics type='vnc' port='5912' autoport='yes' listen='10.x.x.3' listen type='address' address='10.147.37.3'/ /graphics video model type='cirrus' vram='9216' heads='1'/ alias name='video0'/ address type='pci'
[jira] [Commented] (CLOUDSTACK-6464) [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14017109#comment-14017109 ] ASF subversion and git services commented on CLOUDSTACK-6464: - Commit 15385948dcdf4c69136e99bf3c602f95fd018f39 in cloudstack's branch refs/heads/4.3-forward from Edison Su [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=1538594 ] CLOUDSTACK-6464: if guest network type is vlan://untagged, and traffic label is used, kvm agent needs to honor traffic label [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used -- Key: CLOUDSTACK-6464 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6464 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: sadhu suresh Priority: Critical Fix For: 4.4.0 Steps: 1. create a KVM basic zone with 2 nics on host (pre 4.3 build) 2.use cloudbr0 for management and cloudbr1 for guest by specifying the traffic labels in the physical networks. 3.deploy few vms 4.upgrade to felton GA build as per the Upgrade instructions. actual result: Upgrade successful but all the vnets that were attached to cloudbr1 before upgrade are attached to cloudbr0. Due to this network connectivity is lost. Expected result: Even after upgrade ,all the vnets should be attached to the same bridge as before upgrade. ex: before Upgrade : this vms(i-5-616-VM) nic was attached to cloudbr1 and after upgrade and VM stop/start. the network rules are getting programmed in cloudbr0 .check below output ,984 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Executing: /usr/share/cloudstack-common/scripts/vm/network/security_group.py default_network_rules --vmname i-5-616-VM --vmid 616 --vmip 10.x.x245 --vmmac 06:14:48:00:00:7f --vif vnet15 --brname cloudbr0 --nicsecips 0: dumpxml output for i-5-616-VM after upgrade( after VM restart) * virsh # dumpxml 38 domain type='kvm' id='38' namei-5-616-VM/name uuid87557942-1393-49b3-a73e-ae24c40541d1/uuid descriptionOther CentOS (64-bit)/description memory unit='KiB'2097152/memory currentMemory unit='KiB'2097152/currentMemory vcpu placement='static'1/vcpu cputune shares1000/shares /cputune os type arch='x86_64' machine='rhel6.2.0'hvm/type boot dev='cdrom'/ boot dev='hd'/ /os features acpi/ apic/ pae/ /features cpu /cpu clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices emulator/usr/libexec/qemu-kvm/emulator disk type='file' device='disk' driver name='qemu' type='qcow2' cache='none'/ source file='/mnt/041e5d8e-d9c1-346d-aea9-cd9c7b80a211/75544e9d-a4c9-4a94-943e-b20827676a27'/ target dev='hda' bus='ide'/ alias name='ide0-0-0'/ address type='drive' controller='0' bus='0' target='0' unit='0'/ /disk disk type='file' device='cdrom' driver name='qemu' type='raw' cache='none'/ target dev='hdc' bus='ide'/ readonly/ alias name='ide0-1-0'/ address type='drive' controller='0' bus='1' target='0' unit='0'/ /disk controller type='usb' index='0' alias name='usb0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x2'/ /controller controller type='ide' index='0' alias name='ide0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x1'/ /controller interface type='bridge' mac address='06:14:48:00:00:7f'/ source bridge='cloudbr0'/ target dev='vnet15'/ model type='e1000'/ bandwidth inbound average='25600' peak='25600'/ outbound average='25600' peak='25600'/ /bandwidth alias name='net0'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /interface serial type='pty' source path='/dev/pts/12'/ target port='0'/ alias name='serial0'/ /serial console type='pty' tty='/dev/pts/12' source path='/dev/pts/12'/ target type='serial' port='0'/ alias name='serial0'/ /console input type='tablet' bus='usb' alias name='input0'/ /input input type='mouse' bus='ps2'/ graphics type='vnc' port='5912' autoport='yes' listen='10.x.x.3' listen type='address' address='10.147.37.3'/ /graphics video model type='cirrus' vram='9216' heads='1'/ alias name='video0'/ address type='pci' domain='0x' bus='0x00' slot='0x02' function='0x0'/ /video memballoon model='virtio' alias name='balloon0'/ address type='pci' domain='0x' bus='0x00' slot='0x04' function='0x0'/ /memballoon /devices seclabel
[jira] [Commented] (CLOUDSTACK-6464) [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14017116#comment-14017116 ] ASF subversion and git services commented on CLOUDSTACK-6464: - Commit dfb59cd6cc0292a88cb619e53f34cdb713879ffd in cloudstack's branch refs/heads/4.4-forward from Edison Su [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=dfb59cd ] CLOUDSTACK-6464: if guest network type is vlan://untagged, and traffic label is used, kvm agent needs to honor traffic label [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used -- Key: CLOUDSTACK-6464 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6464 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: sadhu suresh Priority: Critical Fix For: 4.4.0 Steps: 1. create a KVM basic zone with 2 nics on host (pre 4.3 build) 2.use cloudbr0 for management and cloudbr1 for guest by specifying the traffic labels in the physical networks. 3.deploy few vms 4.upgrade to felton GA build as per the Upgrade instructions. actual result: Upgrade successful but all the vnets that were attached to cloudbr1 before upgrade are attached to cloudbr0. Due to this network connectivity is lost. Expected result: Even after upgrade ,all the vnets should be attached to the same bridge as before upgrade. ex: before Upgrade : this vms(i-5-616-VM) nic was attached to cloudbr1 and after upgrade and VM stop/start. the network rules are getting programmed in cloudbr0 .check below output ,984 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Executing: /usr/share/cloudstack-common/scripts/vm/network/security_group.py default_network_rules --vmname i-5-616-VM --vmid 616 --vmip 10.x.x245 --vmmac 06:14:48:00:00:7f --vif vnet15 --brname cloudbr0 --nicsecips 0: dumpxml output for i-5-616-VM after upgrade( after VM restart) * virsh # dumpxml 38 domain type='kvm' id='38' namei-5-616-VM/name uuid87557942-1393-49b3-a73e-ae24c40541d1/uuid descriptionOther CentOS (64-bit)/description memory unit='KiB'2097152/memory currentMemory unit='KiB'2097152/currentMemory vcpu placement='static'1/vcpu cputune shares1000/shares /cputune os type arch='x86_64' machine='rhel6.2.0'hvm/type boot dev='cdrom'/ boot dev='hd'/ /os features acpi/ apic/ pae/ /features cpu /cpu clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices emulator/usr/libexec/qemu-kvm/emulator disk type='file' device='disk' driver name='qemu' type='qcow2' cache='none'/ source file='/mnt/041e5d8e-d9c1-346d-aea9-cd9c7b80a211/75544e9d-a4c9-4a94-943e-b20827676a27'/ target dev='hda' bus='ide'/ alias name='ide0-0-0'/ address type='drive' controller='0' bus='0' target='0' unit='0'/ /disk disk type='file' device='cdrom' driver name='qemu' type='raw' cache='none'/ target dev='hdc' bus='ide'/ readonly/ alias name='ide0-1-0'/ address type='drive' controller='0' bus='1' target='0' unit='0'/ /disk controller type='usb' index='0' alias name='usb0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x2'/ /controller controller type='ide' index='0' alias name='ide0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x1'/ /controller interface type='bridge' mac address='06:14:48:00:00:7f'/ source bridge='cloudbr0'/ target dev='vnet15'/ model type='e1000'/ bandwidth inbound average='25600' peak='25600'/ outbound average='25600' peak='25600'/ /bandwidth alias name='net0'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /interface serial type='pty' source path='/dev/pts/12'/ target port='0'/ alias name='serial0'/ /serial console type='pty' tty='/dev/pts/12' source path='/dev/pts/12'/ target type='serial' port='0'/ alias name='serial0'/ /console input type='tablet' bus='usb' alias name='input0'/ /input input type='mouse' bus='ps2'/ graphics type='vnc' port='5912' autoport='yes' listen='10.x.x.3' listen type='address' address='10.147.37.3'/ /graphics video model type='cirrus' vram='9216' heads='1'/ alias name='video0'/ address type='pci' domain='0x' bus='0x00' slot='0x02' function='0x0'/ /video memballoon model='virtio' alias name='balloon0'/ address type='pci' domain='0x' bus='0x00' slot='0x04' function='0x0'/ /memballoon /devices seclabel
[jira] [Commented] (CLOUDSTACK-6464) [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14017137#comment-14017137 ] Bob Vanderford commented on CLOUDSTACK-6464: Marcus, I just saw your last post to me, I had posted a response before I saw your last response. I can definitely put in a new bug report, but at this point I think I'll wait until I see the final outcome on this one. If I still see a problem after the air clears here, then, I put in the new bug report. [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used -- Key: CLOUDSTACK-6464 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6464 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: sadhu suresh Priority: Critical Fix For: 4.4.0 Steps: 1. create a KVM basic zone with 2 nics on host (pre 4.3 build) 2.use cloudbr0 for management and cloudbr1 for guest by specifying the traffic labels in the physical networks. 3.deploy few vms 4.upgrade to felton GA build as per the Upgrade instructions. actual result: Upgrade successful but all the vnets that were attached to cloudbr1 before upgrade are attached to cloudbr0. Due to this network connectivity is lost. Expected result: Even after upgrade ,all the vnets should be attached to the same bridge as before upgrade. ex: before Upgrade : this vms(i-5-616-VM) nic was attached to cloudbr1 and after upgrade and VM stop/start. the network rules are getting programmed in cloudbr0 .check below output ,984 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Executing: /usr/share/cloudstack-common/scripts/vm/network/security_group.py default_network_rules --vmname i-5-616-VM --vmid 616 --vmip 10.x.x245 --vmmac 06:14:48:00:00:7f --vif vnet15 --brname cloudbr0 --nicsecips 0: dumpxml output for i-5-616-VM after upgrade( after VM restart) * virsh # dumpxml 38 domain type='kvm' id='38' namei-5-616-VM/name uuid87557942-1393-49b3-a73e-ae24c40541d1/uuid descriptionOther CentOS (64-bit)/description memory unit='KiB'2097152/memory currentMemory unit='KiB'2097152/currentMemory vcpu placement='static'1/vcpu cputune shares1000/shares /cputune os type arch='x86_64' machine='rhel6.2.0'hvm/type boot dev='cdrom'/ boot dev='hd'/ /os features acpi/ apic/ pae/ /features cpu /cpu clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices emulator/usr/libexec/qemu-kvm/emulator disk type='file' device='disk' driver name='qemu' type='qcow2' cache='none'/ source file='/mnt/041e5d8e-d9c1-346d-aea9-cd9c7b80a211/75544e9d-a4c9-4a94-943e-b20827676a27'/ target dev='hda' bus='ide'/ alias name='ide0-0-0'/ address type='drive' controller='0' bus='0' target='0' unit='0'/ /disk disk type='file' device='cdrom' driver name='qemu' type='raw' cache='none'/ target dev='hdc' bus='ide'/ readonly/ alias name='ide0-1-0'/ address type='drive' controller='0' bus='1' target='0' unit='0'/ /disk controller type='usb' index='0' alias name='usb0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x2'/ /controller controller type='ide' index='0' alias name='ide0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x1'/ /controller interface type='bridge' mac address='06:14:48:00:00:7f'/ source bridge='cloudbr0'/ target dev='vnet15'/ model type='e1000'/ bandwidth inbound average='25600' peak='25600'/ outbound average='25600' peak='25600'/ /bandwidth alias name='net0'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /interface serial type='pty' source path='/dev/pts/12'/ target port='0'/ alias name='serial0'/ /serial console type='pty' tty='/dev/pts/12' source path='/dev/pts/12'/ target type='serial' port='0'/ alias name='serial0'/ /console input type='tablet' bus='usb' alias name='input0'/ /input input type='mouse' bus='ps2'/ graphics type='vnc' port='5912' autoport='yes' listen='10.x.x.3' listen type='address' address='10.147.37.3'/ /graphics video model type='cirrus' vram='9216' heads='1'/ alias name='video0'/ address type='pci' domain='0x' bus='0x00' slot='0x02' function='0x0'/ /video memballoon model='virtio' alias name='balloon0'/ address type='pci' domain='0x' bus='0x00' slot='0x04' function='0x0'/ /memballoon /devices seclabel type='none'/ /domain its also
[jira] [Commented] (CLOUDSTACK-6464) [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14017150#comment-14017150 ] edison su commented on CLOUDSTACK-6464: --- Bob, better create new bug for the issue you have, with both mgt server and agent log(with debug level turned on). I think I already fixed the original issue. [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used -- Key: CLOUDSTACK-6464 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6464 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: sadhu suresh Priority: Critical Fix For: 4.4.0 Steps: 1. create a KVM basic zone with 2 nics on host (pre 4.3 build) 2.use cloudbr0 for management and cloudbr1 for guest by specifying the traffic labels in the physical networks. 3.deploy few vms 4.upgrade to felton GA build as per the Upgrade instructions. actual result: Upgrade successful but all the vnets that were attached to cloudbr1 before upgrade are attached to cloudbr0. Due to this network connectivity is lost. Expected result: Even after upgrade ,all the vnets should be attached to the same bridge as before upgrade. ex: before Upgrade : this vms(i-5-616-VM) nic was attached to cloudbr1 and after upgrade and VM stop/start. the network rules are getting programmed in cloudbr0 .check below output ,984 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Executing: /usr/share/cloudstack-common/scripts/vm/network/security_group.py default_network_rules --vmname i-5-616-VM --vmid 616 --vmip 10.x.x245 --vmmac 06:14:48:00:00:7f --vif vnet15 --brname cloudbr0 --nicsecips 0: dumpxml output for i-5-616-VM after upgrade( after VM restart) * virsh # dumpxml 38 domain type='kvm' id='38' namei-5-616-VM/name uuid87557942-1393-49b3-a73e-ae24c40541d1/uuid descriptionOther CentOS (64-bit)/description memory unit='KiB'2097152/memory currentMemory unit='KiB'2097152/currentMemory vcpu placement='static'1/vcpu cputune shares1000/shares /cputune os type arch='x86_64' machine='rhel6.2.0'hvm/type boot dev='cdrom'/ boot dev='hd'/ /os features acpi/ apic/ pae/ /features cpu /cpu clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices emulator/usr/libexec/qemu-kvm/emulator disk type='file' device='disk' driver name='qemu' type='qcow2' cache='none'/ source file='/mnt/041e5d8e-d9c1-346d-aea9-cd9c7b80a211/75544e9d-a4c9-4a94-943e-b20827676a27'/ target dev='hda' bus='ide'/ alias name='ide0-0-0'/ address type='drive' controller='0' bus='0' target='0' unit='0'/ /disk disk type='file' device='cdrom' driver name='qemu' type='raw' cache='none'/ target dev='hdc' bus='ide'/ readonly/ alias name='ide0-1-0'/ address type='drive' controller='0' bus='1' target='0' unit='0'/ /disk controller type='usb' index='0' alias name='usb0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x2'/ /controller controller type='ide' index='0' alias name='ide0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x1'/ /controller interface type='bridge' mac address='06:14:48:00:00:7f'/ source bridge='cloudbr0'/ target dev='vnet15'/ model type='e1000'/ bandwidth inbound average='25600' peak='25600'/ outbound average='25600' peak='25600'/ /bandwidth alias name='net0'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /interface serial type='pty' source path='/dev/pts/12'/ target port='0'/ alias name='serial0'/ /serial console type='pty' tty='/dev/pts/12' source path='/dev/pts/12'/ target type='serial' port='0'/ alias name='serial0'/ /console input type='tablet' bus='usb' alias name='input0'/ /input input type='mouse' bus='ps2'/ graphics type='vnc' port='5912' autoport='yes' listen='10.x.x.3' listen type='address' address='10.147.37.3'/ /graphics video model type='cirrus' vram='9216' heads='1'/ alias name='video0'/ address type='pci' domain='0x' bus='0x00' slot='0x02' function='0x0'/ /video memballoon model='virtio' alias name='balloon0'/ address type='pci' domain='0x' bus='0x00' slot='0x04' function='0x0'/ /memballoon /devices seclabel type='none'/ /domain its also applicable to new vm deployments. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6464) [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14014968#comment-14014968 ] Gerolamo Valcamonica commented on CLOUDSTACK-6464: -- Same bug after upgrading 4.1 -4.3 Bob Vanderford's workaround works but is not a permanent solution. This needs a bug fix urgently [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used -- Key: CLOUDSTACK-6464 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6464 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: sadhu suresh Priority: Critical Fix For: 4.4.0 Steps: 1. create a KVM basic zone with 2 nics on host (pre 4.3 build) 2.use cloudbr0 for management and cloudbr1 for guest by specifying the traffic labels in the physical networks. 3.deploy few vms 4.upgrade to felton GA build as per the Upgrade instructions. actual result: Upgrade successful but all the vnets that were attached to cloudbr1 before upgrade are attached to cloudbr0. Due to this network connectivity is lost. Expected result: Even after upgrade ,all the vnets should be attached to the same bridge as before upgrade. ex: before Upgrade : this vms(i-5-616-VM) nic was attached to cloudbr1 and after upgrade and VM stop/start. the network rules are getting programmed in cloudbr0 .check below output ,984 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Executing: /usr/share/cloudstack-common/scripts/vm/network/security_group.py default_network_rules --vmname i-5-616-VM --vmid 616 --vmip 10.x.x245 --vmmac 06:14:48:00:00:7f --vif vnet15 --brname cloudbr0 --nicsecips 0: dumpxml output for i-5-616-VM after upgrade( after VM restart) * virsh # dumpxml 38 domain type='kvm' id='38' namei-5-616-VM/name uuid87557942-1393-49b3-a73e-ae24c40541d1/uuid descriptionOther CentOS (64-bit)/description memory unit='KiB'2097152/memory currentMemory unit='KiB'2097152/currentMemory vcpu placement='static'1/vcpu cputune shares1000/shares /cputune os type arch='x86_64' machine='rhel6.2.0'hvm/type boot dev='cdrom'/ boot dev='hd'/ /os features acpi/ apic/ pae/ /features cpu /cpu clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices emulator/usr/libexec/qemu-kvm/emulator disk type='file' device='disk' driver name='qemu' type='qcow2' cache='none'/ source file='/mnt/041e5d8e-d9c1-346d-aea9-cd9c7b80a211/75544e9d-a4c9-4a94-943e-b20827676a27'/ target dev='hda' bus='ide'/ alias name='ide0-0-0'/ address type='drive' controller='0' bus='0' target='0' unit='0'/ /disk disk type='file' device='cdrom' driver name='qemu' type='raw' cache='none'/ target dev='hdc' bus='ide'/ readonly/ alias name='ide0-1-0'/ address type='drive' controller='0' bus='1' target='0' unit='0'/ /disk controller type='usb' index='0' alias name='usb0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x2'/ /controller controller type='ide' index='0' alias name='ide0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x1'/ /controller interface type='bridge' mac address='06:14:48:00:00:7f'/ source bridge='cloudbr0'/ target dev='vnet15'/ model type='e1000'/ bandwidth inbound average='25600' peak='25600'/ outbound average='25600' peak='25600'/ /bandwidth alias name='net0'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /interface serial type='pty' source path='/dev/pts/12'/ target port='0'/ alias name='serial0'/ /serial console type='pty' tty='/dev/pts/12' source path='/dev/pts/12'/ target type='serial' port='0'/ alias name='serial0'/ /console input type='tablet' bus='usb' alias name='input0'/ /input input type='mouse' bus='ps2'/ graphics type='vnc' port='5912' autoport='yes' listen='10.x.x.3' listen type='address' address='10.147.37.3'/ /graphics video model type='cirrus' vram='9216' heads='1'/ alias name='video0'/ address type='pci' domain='0x' bus='0x00' slot='0x02' function='0x0'/ /video memballoon model='virtio' alias name='balloon0'/ address type='pci' domain='0x' bus='0x00' slot='0x04' function='0x0'/ /memballoon /devices seclabel type='none'/ /domain its also applicable to new vm deployments. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6464) [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14010920#comment-14010920 ] E. Anders Lannerbäck commented on CLOUDSTACK-6464: -- Hello Bob! Your symptoms are very similar to ours, so I believe it is indeed the same bug, and that my bugfix just wasn't generic enough. I am not familiar with the Cloudstack codebase and the patch was produced under a fair amount of stress, trying to get our cloud to work again. My hope is that someone who knows the code can look at my patch and see how it really should be solved. I will unfortunately not have time to try to produce a better patch for the next few days. [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used -- Key: CLOUDSTACK-6464 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6464 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: sadhu suresh Priority: Critical Fix For: 4.4.0 Steps: 1. create a KVM basic zone with 2 nics on host (pre 4.3 build) 2.use cloudbr0 for management and cloudbr1 for guest by specifying the traffic labels in the physical networks. 3.deploy few vms 4.upgrade to felton GA build as per the Upgrade instructions. actual result: Upgrade successful but all the vnets that were attached to cloudbr1 before upgrade are attached to cloudbr0. Due to this network connectivity is lost. Expected result: Even after upgrade ,all the vnets should be attached to the same bridge as before upgrade. ex: before Upgrade : this vms(i-5-616-VM) nic was attached to cloudbr1 and after upgrade and VM stop/start. the network rules are getting programmed in cloudbr0 .check below output ,984 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Executing: /usr/share/cloudstack-common/scripts/vm/network/security_group.py default_network_rules --vmname i-5-616-VM --vmid 616 --vmip 10.x.x245 --vmmac 06:14:48:00:00:7f --vif vnet15 --brname cloudbr0 --nicsecips 0: dumpxml output for i-5-616-VM after upgrade( after VM restart) * virsh # dumpxml 38 domain type='kvm' id='38' namei-5-616-VM/name uuid87557942-1393-49b3-a73e-ae24c40541d1/uuid descriptionOther CentOS (64-bit)/description memory unit='KiB'2097152/memory currentMemory unit='KiB'2097152/currentMemory vcpu placement='static'1/vcpu cputune shares1000/shares /cputune os type arch='x86_64' machine='rhel6.2.0'hvm/type boot dev='cdrom'/ boot dev='hd'/ /os features acpi/ apic/ pae/ /features cpu /cpu clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices emulator/usr/libexec/qemu-kvm/emulator disk type='file' device='disk' driver name='qemu' type='qcow2' cache='none'/ source file='/mnt/041e5d8e-d9c1-346d-aea9-cd9c7b80a211/75544e9d-a4c9-4a94-943e-b20827676a27'/ target dev='hda' bus='ide'/ alias name='ide0-0-0'/ address type='drive' controller='0' bus='0' target='0' unit='0'/ /disk disk type='file' device='cdrom' driver name='qemu' type='raw' cache='none'/ target dev='hdc' bus='ide'/ readonly/ alias name='ide0-1-0'/ address type='drive' controller='0' bus='1' target='0' unit='0'/ /disk controller type='usb' index='0' alias name='usb0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x2'/ /controller controller type='ide' index='0' alias name='ide0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x1'/ /controller interface type='bridge' mac address='06:14:48:00:00:7f'/ source bridge='cloudbr0'/ target dev='vnet15'/ model type='e1000'/ bandwidth inbound average='25600' peak='25600'/ outbound average='25600' peak='25600'/ /bandwidth alias name='net0'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /interface serial type='pty' source path='/dev/pts/12'/ target port='0'/ alias name='serial0'/ /serial console type='pty' tty='/dev/pts/12' source path='/dev/pts/12'/ target type='serial' port='0'/ alias name='serial0'/ /console input type='tablet' bus='usb' alias name='input0'/ /input input type='mouse' bus='ps2'/ graphics type='vnc' port='5912' autoport='yes' listen='10.x.x.3' listen type='address' address='10.147.37.3'/ /graphics video model type='cirrus' vram='9216' heads='1'/ alias name='video0'/ address type='pci' domain='0x' bus='0x00' slot='0x02' function='0x0'/ /video
[jira] [Commented] (CLOUDSTACK-6464) [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14010199#comment-14010199 ] Bob Vanderford commented on CLOUDSTACK-6464: We also have had trouble similar to this issue. We did not upgrade, just started with version 4.3 in a prototype environment using advanced networking. Here is were we got in troubleshooting this. We found what seems to be a redundant interface on the virtual router for the network (isolated), eth3. Eth2 is the public interface but eth3 has the same public ip address assigned as eth2. Now we see the following iptables rule on the virtual router: iptables -t nat -A POSTROUTING -j SNAT -o eth3 --to-source=ip address We delete this rule using the -D form of the iptables command and then added the rule back but using eth2 instead of eth3, like this: iptables -t nat -A POSTROUTING -j SNAT -o eth2 --to-source=ip address After that the instance(s) on that network have egress and can access the public internet. This is not an acceptable workaround, however, since users won't have access to the virtual router. But, it does demonstrate the nature of the issue. So, either the eth3 interface shouldn't be there at all or the iptables rule needs to apply its rule to eth2 rather than eth3. This issue essentially makes version 4.3 unusable for us. To have an effect instance it must be able to access the Internet for patch updates, downloading files, etc. We would consider this a blocking issue and deserving of a patch or a quick release for 4.3.1 if such a thing is possible. If there is another workaround in meantime, we would be happy to use it. Also, note, this is a prototype environment and we can provide access to the management portal to anyone that would be interested in debugging or trying a patch. [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used -- Key: CLOUDSTACK-6464 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6464 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: sadhu suresh Priority: Critical Fix For: 4.4.0 Steps: 1. create a KVM basic zone with 2 nics on host (pre 4.3 build) 2.use cloudbr0 for management and cloudbr1 for guest by specifying the traffic labels in the physical networks. 3.deploy few vms 4.upgrade to felton GA build as per the Upgrade instructions. actual result: Upgrade successful but all the vnets that were attached to cloudbr1 before upgrade are attached to cloudbr0. Due to this network connectivity is lost. Expected result: Even after upgrade ,all the vnets should be attached to the same bridge as before upgrade. ex: before Upgrade : this vms(i-5-616-VM) nic was attached to cloudbr1 and after upgrade and VM stop/start. the network rules are getting programmed in cloudbr0 .check below output ,984 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Executing: /usr/share/cloudstack-common/scripts/vm/network/security_group.py default_network_rules --vmname i-5-616-VM --vmid 616 --vmip 10.x.x245 --vmmac 06:14:48:00:00:7f --vif vnet15 --brname cloudbr0 --nicsecips 0: dumpxml output for i-5-616-VM after upgrade( after VM restart) * virsh # dumpxml 38 domain type='kvm' id='38' namei-5-616-VM/name uuid87557942-1393-49b3-a73e-ae24c40541d1/uuid descriptionOther CentOS (64-bit)/description memory unit='KiB'2097152/memory currentMemory unit='KiB'2097152/currentMemory vcpu placement='static'1/vcpu cputune shares1000/shares /cputune os type arch='x86_64' machine='rhel6.2.0'hvm/type boot dev='cdrom'/ boot dev='hd'/ /os features acpi/ apic/ pae/ /features cpu /cpu clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices emulator/usr/libexec/qemu-kvm/emulator disk type='file' device='disk' driver name='qemu' type='qcow2' cache='none'/ source file='/mnt/041e5d8e-d9c1-346d-aea9-cd9c7b80a211/75544e9d-a4c9-4a94-943e-b20827676a27'/ target dev='hda' bus='ide'/ alias name='ide0-0-0'/ address type='drive' controller='0' bus='0' target='0' unit='0'/ /disk disk type='file' device='cdrom' driver name='qemu' type='raw' cache='none'/ target dev='hdc' bus='ide'/ readonly/ alias name='ide0-1-0'/ address type='drive' controller='0' bus='1' target='0' unit='0'/ /disk controller type='usb' index='0' alias name='usb0'/ address type='pci'
[jira] [Commented] (CLOUDSTACK-6464) [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14010706#comment-14010706 ] Bob Vanderford commented on CLOUDSTACK-6464: Regarding my earlier comment, I tried the patch provided by E. Anders Lannerbäck. It did not resolve the issue I reported earlier today. Maybe my problem is different but the symptoms seem the same. Also, after installing the patch on the compute nodes, I could no longer use the console tool (clicking on view console gave an error about not able to find /ajax, 404 error. After removing the patch and putting back the original .jar file, I could again access the console. [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used -- Key: CLOUDSTACK-6464 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6464 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: sadhu suresh Priority: Critical Fix For: 4.4.0 Steps: 1. create a KVM basic zone with 2 nics on host (pre 4.3 build) 2.use cloudbr0 for management and cloudbr1 for guest by specifying the traffic labels in the physical networks. 3.deploy few vms 4.upgrade to felton GA build as per the Upgrade instructions. actual result: Upgrade successful but all the vnets that were attached to cloudbr1 before upgrade are attached to cloudbr0. Due to this network connectivity is lost. Expected result: Even after upgrade ,all the vnets should be attached to the same bridge as before upgrade. ex: before Upgrade : this vms(i-5-616-VM) nic was attached to cloudbr1 and after upgrade and VM stop/start. the network rules are getting programmed in cloudbr0 .check below output ,984 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Executing: /usr/share/cloudstack-common/scripts/vm/network/security_group.py default_network_rules --vmname i-5-616-VM --vmid 616 --vmip 10.x.x245 --vmmac 06:14:48:00:00:7f --vif vnet15 --brname cloudbr0 --nicsecips 0: dumpxml output for i-5-616-VM after upgrade( after VM restart) * virsh # dumpxml 38 domain type='kvm' id='38' namei-5-616-VM/name uuid87557942-1393-49b3-a73e-ae24c40541d1/uuid descriptionOther CentOS (64-bit)/description memory unit='KiB'2097152/memory currentMemory unit='KiB'2097152/currentMemory vcpu placement='static'1/vcpu cputune shares1000/shares /cputune os type arch='x86_64' machine='rhel6.2.0'hvm/type boot dev='cdrom'/ boot dev='hd'/ /os features acpi/ apic/ pae/ /features cpu /cpu clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices emulator/usr/libexec/qemu-kvm/emulator disk type='file' device='disk' driver name='qemu' type='qcow2' cache='none'/ source file='/mnt/041e5d8e-d9c1-346d-aea9-cd9c7b80a211/75544e9d-a4c9-4a94-943e-b20827676a27'/ target dev='hda' bus='ide'/ alias name='ide0-0-0'/ address type='drive' controller='0' bus='0' target='0' unit='0'/ /disk disk type='file' device='cdrom' driver name='qemu' type='raw' cache='none'/ target dev='hdc' bus='ide'/ readonly/ alias name='ide0-1-0'/ address type='drive' controller='0' bus='1' target='0' unit='0'/ /disk controller type='usb' index='0' alias name='usb0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x2'/ /controller controller type='ide' index='0' alias name='ide0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x1'/ /controller interface type='bridge' mac address='06:14:48:00:00:7f'/ source bridge='cloudbr0'/ target dev='vnet15'/ model type='e1000'/ bandwidth inbound average='25600' peak='25600'/ outbound average='25600' peak='25600'/ /bandwidth alias name='net0'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /interface serial type='pty' source path='/dev/pts/12'/ target port='0'/ alias name='serial0'/ /serial console type='pty' tty='/dev/pts/12' source path='/dev/pts/12'/ target type='serial' port='0'/ alias name='serial0'/ /console input type='tablet' bus='usb' alias name='input0'/ /input input type='mouse' bus='ps2'/ graphics type='vnc' port='5912' autoport='yes' listen='10.x.x.3' listen type='address' address='10.147.37.3'/ /graphics video model type='cirrus' vram='9216' heads='1'/ alias name='video0'/ address type='pci' domain='0x' bus='0x00' slot='0x02' function='0x0'/ /video memballoon
[jira] [Commented] (CLOUDSTACK-6464) [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14008807#comment-14008807 ] E. Anders Lannerbäck commented on CLOUDSTACK-6464: -- This is a showstopper bug. We had a major outage after upgrading cloudstack. After an allnighter, we found the bug, and have submitted a patch for review. This patch solves the issue for us. See https://reviews.apache.org/r/21908/ We have made a prebuilt JAR available here: http://cloudstack-fixes.redbridge-ab.objekt.rbcloud.net/cloud-plugin-hypervisor-kvm-4.3.0.jar. To use it, replace the old jar with this fixed one on your cloudstack agents, restart your cloudstack-agents, and reboot your virtual routers. Hope this helps! [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used -- Key: CLOUDSTACK-6464 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6464 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: sadhu suresh Priority: Critical Fix For: 4.4.0 Steps: 1. create a KVM basic zone with 2 nics on host (pre 4.3 build) 2.use cloudbr0 for management and cloudbr1 for guest by specifying the traffic labels in the physical networks. 3.deploy few vms 4.upgrade to felton GA build as per the Upgrade instructions. actual result: Upgrade successful but all the vnets that were attached to cloudbr1 before upgrade are attached to cloudbr0. Due to this network connectivity is lost. Expected result: Even after upgrade ,all the vnets should be attached to the same bridge as before upgrade. ex: before Upgrade : this vms(i-5-616-VM) nic was attached to cloudbr1 and after upgrade and VM stop/start. the network rules are getting programmed in cloudbr0 .check below output ,984 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Executing: /usr/share/cloudstack-common/scripts/vm/network/security_group.py default_network_rules --vmname i-5-616-VM --vmid 616 --vmip 10.x.x245 --vmmac 06:14:48:00:00:7f --vif vnet15 --brname cloudbr0 --nicsecips 0: dumpxml output for i-5-616-VM after upgrade( after VM restart) * virsh # dumpxml 38 domain type='kvm' id='38' namei-5-616-VM/name uuid87557942-1393-49b3-a73e-ae24c40541d1/uuid descriptionOther CentOS (64-bit)/description memory unit='KiB'2097152/memory currentMemory unit='KiB'2097152/currentMemory vcpu placement='static'1/vcpu cputune shares1000/shares /cputune os type arch='x86_64' machine='rhel6.2.0'hvm/type boot dev='cdrom'/ boot dev='hd'/ /os features acpi/ apic/ pae/ /features cpu /cpu clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices emulator/usr/libexec/qemu-kvm/emulator disk type='file' device='disk' driver name='qemu' type='qcow2' cache='none'/ source file='/mnt/041e5d8e-d9c1-346d-aea9-cd9c7b80a211/75544e9d-a4c9-4a94-943e-b20827676a27'/ target dev='hda' bus='ide'/ alias name='ide0-0-0'/ address type='drive' controller='0' bus='0' target='0' unit='0'/ /disk disk type='file' device='cdrom' driver name='qemu' type='raw' cache='none'/ target dev='hdc' bus='ide'/ readonly/ alias name='ide0-1-0'/ address type='drive' controller='0' bus='1' target='0' unit='0'/ /disk controller type='usb' index='0' alias name='usb0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x2'/ /controller controller type='ide' index='0' alias name='ide0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x1'/ /controller interface type='bridge' mac address='06:14:48:00:00:7f'/ source bridge='cloudbr0'/ target dev='vnet15'/ model type='e1000'/ bandwidth inbound average='25600' peak='25600'/ outbound average='25600' peak='25600'/ /bandwidth alias name='net0'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /interface serial type='pty' source path='/dev/pts/12'/ target port='0'/ alias name='serial0'/ /serial console type='pty' tty='/dev/pts/12' source path='/dev/pts/12'/ target type='serial' port='0'/ alias name='serial0'/ /console input type='tablet' bus='usb' alias name='input0'/ /input input type='mouse' bus='ps2'/ graphics type='vnc' port='5912' autoport='yes' listen='10.x.x.3' listen type='address' address='10.147.37.3'/ /graphics video model type='cirrus' vram='9216' heads='1'/ alias name='video0'/ address type='pci'
[jira] [Commented] (CLOUDSTACK-6464) [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13993653#comment-13993653 ] Simon Weller commented on CLOUDSTACK-6464: -- We are experiencing the exact same issue as Serg noted above using vlan isolation (traffic labels) in KVM with advanced networking on 6.3. What's also interesting is that releasing an ip appears to add an additional interface to the VR, as if it doesn't think a usable interface currently exists, so it hot-plugs a duplicate via libvirtd. It looks like the multiple interfaces are causing ARP problems. Please also look at https://issues.apache.org/jira/browse/CLOUDSTACK-5282 as that references a similar issue, but claims that it was related to https://issues.apache.org/jira/browse/CLOUDSTACK-5280 and resolved. It may be in our case that this is the same issue, but with traffic labels in use being the difference. Note that our platform was upgraded from 4.1.x. I'm more than happy to supply any required logs, and I have a lab platform to test on. - Si [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used -- Key: CLOUDSTACK-6464 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6464 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: sadhu suresh Priority: Critical Fix For: 4.3.1 Steps: 1. create a KVM basic zone with 2 nics on host (pre 4.3 build) 2.use cloudbr0 for management and cloudbr1 for guest by specifying the traffic labels in the physical networks. 3.deploy few vms 4.upgrade to felton GA build as per the Upgrade instructions. actual result: Upgrade successful but all the vnets that were attached to cloudbr1 before upgrade are attached to cloudbr0. Due to this network connectivity is lost. Expected result: Even after upgrade ,all the vnets should be attached to the same bridge as before upgrade. ex: before Upgrade : this vms(i-5-616-VM) nic was attached to cloudbr1 and after upgrade and VM stop/start. the network rules are getting programmed in cloudbr0 .check below output ,984 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Executing: /usr/share/cloudstack-common/scripts/vm/network/security_group.py default_network_rules --vmname i-5-616-VM --vmid 616 --vmip 10.x.x245 --vmmac 06:14:48:00:00:7f --vif vnet15 --brname cloudbr0 --nicsecips 0: dumpxml output for i-5-616-VM after upgrade( after VM restart) * virsh # dumpxml 38 domain type='kvm' id='38' namei-5-616-VM/name uuid87557942-1393-49b3-a73e-ae24c40541d1/uuid descriptionOther CentOS (64-bit)/description memory unit='KiB'2097152/memory currentMemory unit='KiB'2097152/currentMemory vcpu placement='static'1/vcpu cputune shares1000/shares /cputune os type arch='x86_64' machine='rhel6.2.0'hvm/type boot dev='cdrom'/ boot dev='hd'/ /os features acpi/ apic/ pae/ /features cpu /cpu clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices emulator/usr/libexec/qemu-kvm/emulator disk type='file' device='disk' driver name='qemu' type='qcow2' cache='none'/ source file='/mnt/041e5d8e-d9c1-346d-aea9-cd9c7b80a211/75544e9d-a4c9-4a94-943e-b20827676a27'/ target dev='hda' bus='ide'/ alias name='ide0-0-0'/ address type='drive' controller='0' bus='0' target='0' unit='0'/ /disk disk type='file' device='cdrom' driver name='qemu' type='raw' cache='none'/ target dev='hdc' bus='ide'/ readonly/ alias name='ide0-1-0'/ address type='drive' controller='0' bus='1' target='0' unit='0'/ /disk controller type='usb' index='0' alias name='usb0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x2'/ /controller controller type='ide' index='0' alias name='ide0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x1'/ /controller interface type='bridge' mac address='06:14:48:00:00:7f'/ source bridge='cloudbr0'/ target dev='vnet15'/ model type='e1000'/ bandwidth inbound average='25600' peak='25600'/ outbound average='25600' peak='25600'/ /bandwidth alias name='net0'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /interface serial type='pty' source path='/dev/pts/12'/ target port='0'/ alias name='serial0'/ /serial console type='pty' tty='/dev/pts/12' source path='/dev/pts/12'/ target type='serial' port='0'/ alias name='serial0'/ /console input
[jira] [Commented] (CLOUDSTACK-6464) [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13990903#comment-13990903 ] Evan McGee commented on CLOUDSTACK-6464: Just a +1 bump on this. It seems like a fairly large regression for anyone using traffic labels in KVM to lose all egress connectivity. Could someone with more knowledge of the commit that caused this weigh in? [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used -- Key: CLOUDSTACK-6464 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6464 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: sadhu suresh Priority: Critical Fix For: 4.3.1 Steps: 1. create a KVM basic zone with 2 nics on host (pre 4.3 build) 2.use cloudbr0 for management and cloudbr1 for guest by specifying the traffic labels in the physical networks. 3.deploy few vms 4.upgrade to felton GA build as per the Upgrade instructions. actual result: Upgrade successful but all the vnets that were attached to cloudbr1 before upgrade are attached to cloudbr0. Due to this network connectivity is lost. Expected result: Even after upgrade ,all the vnets should be attached to the same bridge as before upgrade. ex: before Upgrade : this vms(i-5-616-VM) nic was attached to cloudbr1 and after upgrade and VM stop/start. the network rules are getting programmed in cloudbr0 .check below output ,984 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Executing: /usr/share/cloudstack-common/scripts/vm/network/security_group.py default_network_rules --vmname i-5-616-VM --vmid 616 --vmip 10.x.x245 --vmmac 06:14:48:00:00:7f --vif vnet15 --brname cloudbr0 --nicsecips 0: dumpxml output for i-5-616-VM after upgrade( after VM restart) * virsh # dumpxml 38 domain type='kvm' id='38' namei-5-616-VM/name uuid87557942-1393-49b3-a73e-ae24c40541d1/uuid descriptionOther CentOS (64-bit)/description memory unit='KiB'2097152/memory currentMemory unit='KiB'2097152/currentMemory vcpu placement='static'1/vcpu cputune shares1000/shares /cputune os type arch='x86_64' machine='rhel6.2.0'hvm/type boot dev='cdrom'/ boot dev='hd'/ /os features acpi/ apic/ pae/ /features cpu /cpu clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices emulator/usr/libexec/qemu-kvm/emulator disk type='file' device='disk' driver name='qemu' type='qcow2' cache='none'/ source file='/mnt/041e5d8e-d9c1-346d-aea9-cd9c7b80a211/75544e9d-a4c9-4a94-943e-b20827676a27'/ target dev='hda' bus='ide'/ alias name='ide0-0-0'/ address type='drive' controller='0' bus='0' target='0' unit='0'/ /disk disk type='file' device='cdrom' driver name='qemu' type='raw' cache='none'/ target dev='hdc' bus='ide'/ readonly/ alias name='ide0-1-0'/ address type='drive' controller='0' bus='1' target='0' unit='0'/ /disk controller type='usb' index='0' alias name='usb0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x2'/ /controller controller type='ide' index='0' alias name='ide0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x1'/ /controller interface type='bridge' mac address='06:14:48:00:00:7f'/ source bridge='cloudbr0'/ target dev='vnet15'/ model type='e1000'/ bandwidth inbound average='25600' peak='25600'/ outbound average='25600' peak='25600'/ /bandwidth alias name='net0'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /interface serial type='pty' source path='/dev/pts/12'/ target port='0'/ alias name='serial0'/ /serial console type='pty' tty='/dev/pts/12' source path='/dev/pts/12'/ target type='serial' port='0'/ alias name='serial0'/ /console input type='tablet' bus='usb' alias name='input0'/ /input input type='mouse' bus='ps2'/ graphics type='vnc' port='5912' autoport='yes' listen='10.x.x.3' listen type='address' address='10.147.37.3'/ /graphics video model type='cirrus' vram='9216' heads='1'/ alias name='video0'/ address type='pci' domain='0x' bus='0x00' slot='0x02' function='0x0'/ /video memballoon model='virtio' alias name='balloon0'/ address type='pci' domain='0x' bus='0x00' slot='0x04' function='0x0'/ /memballoon /devices seclabel type='none'/ /domain its also applicable to new vm deployments. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6464) [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13981292#comment-13981292 ] Serg Senko commented on CLOUDSTACK-6464: Hi, This is a very critical bug which does not allow upgrade to 4.3 any KVM ( Traffic labeled ) environment. Someone can assist? [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used -- Key: CLOUDSTACK-6464 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6464 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: sadhu suresh Priority: Critical Fix For: 4.3.1 Steps: 1. create a KVM basic zone with 2 nics on host (pre 4.3 build) 2.use cloudbr0 for management and cloudbr1 for guest by specifying the traffic labels in the physical networks. 3.deploy few vms 4.upgrade to felton GA build as per the Upgrade instructions. actual result: Upgrade successful but all the vnets that were attached to cloudbr1 before upgrade are attached to cloudbr0. Due to this network connectivity is lost. Expected result: Even after upgrade ,all the vnets should be attached to the same bridge as before upgrade. ex: before Upgrade : this vms(i-5-616-VM) nic was attached to cloudbr1 and after upgrade and VM stop/start. the network rules are getting programmed in cloudbr0 .check below output ,984 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Executing: /usr/share/cloudstack-common/scripts/vm/network/security_group.py default_network_rules --vmname i-5-616-VM --vmid 616 --vmip 10.x.x245 --vmmac 06:14:48:00:00:7f --vif vnet15 --brname cloudbr0 --nicsecips 0: dumpxml output for i-5-616-VM after upgrade( after VM restart) * virsh # dumpxml 38 domain type='kvm' id='38' namei-5-616-VM/name uuid87557942-1393-49b3-a73e-ae24c40541d1/uuid descriptionOther CentOS (64-bit)/description memory unit='KiB'2097152/memory currentMemory unit='KiB'2097152/currentMemory vcpu placement='static'1/vcpu cputune shares1000/shares /cputune os type arch='x86_64' machine='rhel6.2.0'hvm/type boot dev='cdrom'/ boot dev='hd'/ /os features acpi/ apic/ pae/ /features cpu /cpu clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices emulator/usr/libexec/qemu-kvm/emulator disk type='file' device='disk' driver name='qemu' type='qcow2' cache='none'/ source file='/mnt/041e5d8e-d9c1-346d-aea9-cd9c7b80a211/75544e9d-a4c9-4a94-943e-b20827676a27'/ target dev='hda' bus='ide'/ alias name='ide0-0-0'/ address type='drive' controller='0' bus='0' target='0' unit='0'/ /disk disk type='file' device='cdrom' driver name='qemu' type='raw' cache='none'/ target dev='hdc' bus='ide'/ readonly/ alias name='ide0-1-0'/ address type='drive' controller='0' bus='1' target='0' unit='0'/ /disk controller type='usb' index='0' alias name='usb0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x2'/ /controller controller type='ide' index='0' alias name='ide0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x1'/ /controller interface type='bridge' mac address='06:14:48:00:00:7f'/ source bridge='cloudbr0'/ target dev='vnet15'/ model type='e1000'/ bandwidth inbound average='25600' peak='25600'/ outbound average='25600' peak='25600'/ /bandwidth alias name='net0'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /interface serial type='pty' source path='/dev/pts/12'/ target port='0'/ alias name='serial0'/ /serial console type='pty' tty='/dev/pts/12' source path='/dev/pts/12'/ target type='serial' port='0'/ alias name='serial0'/ /console input type='tablet' bus='usb' alias name='input0'/ /input input type='mouse' bus='ps2'/ graphics type='vnc' port='5912' autoport='yes' listen='10.x.x.3' listen type='address' address='10.147.37.3'/ /graphics video model type='cirrus' vram='9216' heads='1'/ alias name='video0'/ address type='pci' domain='0x' bus='0x00' slot='0x02' function='0x0'/ /video memballoon model='virtio' alias name='balloon0'/ address type='pci' domain='0x' bus='0x00' slot='0x04' function='0x0'/ /memballoon /devices seclabel type='none'/ /domain its also applicable to new vm deployments. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6464) [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13975510#comment-13975510 ] Serg Senko commented on CLOUDSTACK-6464: Hello, Also related to advanced zone with VLAN isolation: Environment: OS : CentOS 6.3 Hypervizor : KVM ( QEMU ) Zone : Advanced VLAN isolation Traffic labels : Guest: cloudbr1 private: cloudbr1 public: cloudbr0 After upgrade to ACS 4.3 new VR's started with duplicate NIC's. All IP aliases started as network interfaces with same public IP Following that, egress traffic iptables rules doesn't work and no outgoing network connectivity in any cases. root@r-256-VM:~# ip addr show 1: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 02:00:6b:16:00:09 brd ff:ff:ff:ff:ff:ff inet 10.1.1.1/24 brd 10.1.1.255 scope global eth0 inet6 fe80::6bff:fe16:9/64 scope link valid_lft forever preferred_lft forever 3: eth1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 0e:00:a9:fe:01:38 brd ff:ff:ff:ff:ff:ff inet 169.254.1.56/16 brd 169.254.255.255 scope global eth1 inet6 fe80::c00:a9ff:fefe:138/64 scope link valid_lft forever preferred_lft forever 4: eth2: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 06:06:ec:00:00:0e brd ff:ff:ff:ff:ff:ff inet XXX.XXX.XXX.219/26 brd 46.165.231.255 scope global eth2 inet6 fe80::406:ecff:fe00:e/64 scope link valid_lft forever preferred_lft forever 5: eth3: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 06:81:44:00:00:0e brd ff:ff:ff:ff:ff:ff inet XXX.XXX.XXX.219/26 brd 46.165.231.255 scope global eth3 inet XXX.XXX.XXX.230/26 brd 46.165.231.255 scope global secondary eth3 inet XXX.XXX.XXX.228/26 brd 46.165.231.255 scope global secondary eth3 inet XXX.XXX.XXX.209/26 brd 46.165.231.255 scope global secondary eth3 inet XXX.XXX.XXX.247/26 brd 46.165.231.255 scope global secondary eth3 inet XXX.XXX.XXX.227/26 brd 46.165.231.255 scope global secondary eth3 inet6 fe80::481:44ff:fe00:e/64 scope link valid_lft forever preferred_lft forever 6: eth4: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 06:e5:36:00:00:0e brd ff:ff:ff:ff:ff:ff inet XXX.XXX.XXX.219/26 brd 46.165.231.255 scope global eth4 inet XXX.XXX.XXX.247/26 brd 46.165.231.255 scope global secondary eth4 inet XXX.XXX.XXX.209/26 brd 46.165.231.255 scope global secondary eth4 inet XXX.XXX.XXX.227/26 brd 46.165.231.255 scope global secondary eth4 inet XXX.XXX.XXX.230/26 brd 46.165.231.255 scope global secondary eth4 inet6 fe80::4e5:36ff:fe00:e/64 scope link valid_lft forever preferred_lft forever 7: eth5: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 06:6f:3a:00:00:0e brd ff:ff:ff:ff:ff:ff inet XXX.XXX.XXX.219/26 brd 46.165.231.255 scope global eth5 inet XXX.XXX.XXX.228/26 brd 46.165.231.255 scope global secondary eth5 inet XXX.XXX.XXX.227/26 brd 46.165.231.255 scope global secondary eth5 inet XXX.XXX.XXX.209/26 brd 46.165.231.255 scope global secondary eth5 inet XXX.XXX.XXX.247/26 brd 46.165.231.255 scope global secondary eth5 inet XXX.XXX.XXX.230/26 brd 46.165.231.255 scope global secondary eth5 inet6 fe80::46f:3aff:fe00:e/64 scope link valid_lft forever preferred_lft forever 8: eth6: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 06:b0:30:00:00:0e brd ff:ff:ff:ff:ff:ff inet XXX.XXX.XXX.219/26 brd 46.165.231.255 scope global eth6 inet XXX.XXX.XXX.209/26 brd 46.165.231.255 scope global secondary eth6 inet XXX.XXX.XXX.247/26 brd 46.165.231.255 scope global secondary eth6 inet XXX.XXX.XXX.230/26 brd 46.165.231.255 scope global secondary eth6 inet XXX.XXX.XXX.227/26 brd 46.165.231.255 scope global secondary eth6 inet6 fe80::4b0:30ff:fe00:e/64 scope link valid_lft forever preferred_lft forever 9: eth7: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 06:26:b4:00:00:0e brd ff:ff:ff:ff:ff:ff inet XXX.XXX.XXX.219/26 brd 46.165.231.255 scope global eth7 inet XXX.XXX.XXX.247/26 brd 46.165.231.255 scope global secondary eth7 inet XXX.XXX.XXX.228/26 brd 46.165.231.255 scope global secondary eth7 inet XXX.XXX.XXX.230/26 brd 46.165.231.255 scope global secondary eth7 inet XXX.XXX.XXX.209/26 brd 46.165.231.255 scope global secondary eth7 inet XXX.XXX.XXX.227/26 brd 46.165.231.255 scope global