Activity log for bug #1754073

Date Who What changed Old value New value Message
2018-03-07 15:53:13 Alex Moldovan bug added bug
2018-03-07 15:54:47 Alex Moldovan summary Instances on Apache CloudStack using KVM hypervisor are not detected as a virtual machine Instances on Apache CloudStack using KVM hypervisor are not detected as virtual machines
2018-03-07 15:58:19 Simon Poirier landscape-client (Ubuntu): status New Confirmed
2018-03-07 15:59:39 Simon Poirier bug task added landscape-client
2018-03-07 16:00:13 Simon Poirier landscape-client: status New Triaged
2018-03-07 16:00:17 Simon Poirier landscape-client: assignee Simon Poirier (simpoir)
2018-03-07 16:00:23 Simon Poirier landscape-client: importance Undecided High
2018-03-26 14:16:44 Simon Poirier landscape-client: status Triaged Fix Committed
2018-03-27 15:43:26 Simon Poirier description Instances running on a Apache CloudStack that is using KVM as a hypervisor are not detected as virtual machines by the landscape-client. They are using a Full license to register instead of a Virtual one. Information from the client: Ubuntu 14.04.5 LTS ​--------------------------------------- landscape-client 14.12-0ubuntu6.14.04.2 ​--------------------------------------- #​cat /sys/class/dmi/id/sys_vendor Apache Software Foundation ​--------------------------------------- ​lscpu:​ Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 1 On-line CPU(s) list: 0 Thread(s) per core: 1 Core(s) per socket: 1 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 42 Stepping: 1 CPU MHz: 2299.998 BogoMIPS: 4599.99 Hypervisor vendor: KVM Virtualization type: full L1d cache: 32K L1i cache: 32K L2 cache: 4096K NUMA node0 CPU(s): 0 ​--------------------------------------- [Impact] * This issue affects users of Apache Cloudstack instances by failing to detect the hypervisor type and reporting the clients as running on a physical machine instead of on KVM. * This fix extends dmi vendor mapping, so that clouds customizing sys_vendor chassis_vendor or bios_vendor values (e.g. CloudStack, DigitalOcean) still get detected as KVM instances. [Test Case] The issue can be reproduced on libvirt/kvm. uvt-kvm create vm virsh edit vm <os> ... <smbios mode='sysinfo'/> </os> <sysinfo type="smbios"> <system> <entry name='manufacturer'>Apache Software Foundation</entry> <entry name='product'>CloudStack KVM Hypervisor</entry> </system> </sysinfo> <cpu match='exact'> <!-- defaults to qemu, which would me detected correctly --> <model fallback='allow'>core2duo</model> <vendor>Intel</vendor> </cpu> virsh destroy vm && virsh start vm uvt-kvm ssh vm --insecure sudo landscape-config --log-level=debug -a devel --silent -t testclient # will fail registering, but that's not relevant to the vm-type detection grep vm-info /var/log/landscape/broker.log # expected output is "KVM", and will be empty because of this bug [Regression Potential] * Like the previous update, this change is local and only affects vm-type detection, which should be low-risk. * Since we extend the current detection to fields we were not previously looking at, one of the risks is to falsely detect clients as running on KVM. This is why we took care to verify opposite scenarios in addition to making sure the existing unit tests pass. Such a regression should have a low user impact, as VM features can be used on a full seat whereas the opposite (due to the bug fixed here) is not true. [Other Info] * AWS and DigitalOcean instances have been fixed slightly differently in the previous SRU, but we wanted to avoid repeating this for every other cloud, thus extending the DMI field lookup instead of adding yet another mapping value. [Original Description] Instances running on a Apache CloudStack that is using KVM as a hypervisor are not detected as virtual machines by the landscape-client. They are using a Full license to register instead of a Virtual one. Information from the client: Ubuntu 14.04.5 LTS --------------------------------------- landscape-client 14.12-0ubuntu6.14.04.2 --------------------------------------- # cat /sys/class/dmi/id/sys_vendor Apache Software Foundation --------------------------------------- lscpu: Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 1 On-line CPU(s) list: 0 Thread(s) per core: 1 Core(s) per socket: 1 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 42 Stepping: 1 CPU MHz: 2299.998 BogoMIPS: 4599.99 Hypervisor vendor: KVM Virtualization type: full L1d cache: 32K L1i cache: 32K L2 cache: 4096K NUMA node0 CPU(s): 0 ---------------------------------------
2018-03-27 15:48:56 Simon Poirier description [Impact] * This issue affects users of Apache Cloudstack instances by failing to detect the hypervisor type and reporting the clients as running on a physical machine instead of on KVM. * This fix extends dmi vendor mapping, so that clouds customizing sys_vendor chassis_vendor or bios_vendor values (e.g. CloudStack, DigitalOcean) still get detected as KVM instances. [Test Case] The issue can be reproduced on libvirt/kvm. uvt-kvm create vm virsh edit vm <os> ... <smbios mode='sysinfo'/> </os> <sysinfo type="smbios"> <system> <entry name='manufacturer'>Apache Software Foundation</entry> <entry name='product'>CloudStack KVM Hypervisor</entry> </system> </sysinfo> <cpu match='exact'> <!-- defaults to qemu, which would me detected correctly --> <model fallback='allow'>core2duo</model> <vendor>Intel</vendor> </cpu> virsh destroy vm && virsh start vm uvt-kvm ssh vm --insecure sudo landscape-config --log-level=debug -a devel --silent -t testclient # will fail registering, but that's not relevant to the vm-type detection grep vm-info /var/log/landscape/broker.log # expected output is "KVM", and will be empty because of this bug [Regression Potential] * Like the previous update, this change is local and only affects vm-type detection, which should be low-risk. * Since we extend the current detection to fields we were not previously looking at, one of the risks is to falsely detect clients as running on KVM. This is why we took care to verify opposite scenarios in addition to making sure the existing unit tests pass. Such a regression should have a low user impact, as VM features can be used on a full seat whereas the opposite (due to the bug fixed here) is not true. [Other Info] * AWS and DigitalOcean instances have been fixed slightly differently in the previous SRU, but we wanted to avoid repeating this for every other cloud, thus extending the DMI field lookup instead of adding yet another mapping value. [Original Description] Instances running on a Apache CloudStack that is using KVM as a hypervisor are not detected as virtual machines by the landscape-client. They are using a Full license to register instead of a Virtual one. Information from the client: Ubuntu 14.04.5 LTS --------------------------------------- landscape-client 14.12-0ubuntu6.14.04.2 --------------------------------------- # cat /sys/class/dmi/id/sys_vendor Apache Software Foundation --------------------------------------- lscpu: Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 1 On-line CPU(s) list: 0 Thread(s) per core: 1 Core(s) per socket: 1 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 42 Stepping: 1 CPU MHz: 2299.998 BogoMIPS: 4599.99 Hypervisor vendor: KVM Virtualization type: full L1d cache: 32K L1i cache: 32K L2 cache: 4096K NUMA node0 CPU(s): 0 --------------------------------------- [Impact]  * This issue affects users of Apache Cloudstack instances by failing to    detect the hypervisor type and reporting the clients as running on    a physical machine instead of on KVM.  * This fix extends dmi vendor mapping, so that clouds customizing sys_vendor    chassis_vendor or bios_vendor values (e.g. CloudStack, DigitalOcean)    still get detected as KVM instances. [Test Case] The issue can be reproduced on libvirt/kvm. uvt-kvm create vm virsh edit vm <os> ... <smbios mode='sysinfo'/> </os> <sysinfo type="smbios">   <system>     <entry name='manufacturer'>Apache Software Foundation</entry>     <entry name='product'>CloudStack KVM Hypervisor</entry>   </system> </sysinfo> <cpu match='exact'> <!-- defaults to qemu, which would me detected correctly -->   <model fallback='allow'>core2duo</model>   <vendor>Intel</vendor> </cpu> virsh destroy vm && virsh start vm uvt-kvm ssh vm --insecure sudo landscape-config --log-level=debug -a devel --silent -t testclient # will fail registering, but that's not relevant to the vm-type detection grep vm-info /var/log/landscape/broker.log # expected output is "KVM", and will be empty because of this bug [Regression Potential]  * Like the previous update, this change is local and only affects vm-type    detection, which should be low-risk.  * Since we extend the current detection to fields we were not previously    looking at, one of the risks is to falsely detect clients as running    on KVM. This is why we took care to verify opposite scenarios in    addition to making sure the existing unit tests pass. Were such a regression to occur, it would have a low user impact, as being detected as VM you can use either physical or VM features, whereas the opposite (due to the bug fixed here) is not true. [Other Info]  * AWS and DigitalOcean instances have been fixed slightly differently in    the previous SRU, but we wanted to avoid repeating this for every other    cloud, thus extending the DMI field lookup instead of adding yet another    mapping value. [Original Description] Instances running on a Apache CloudStack that is using KVM as a hypervisor are not detected as virtual machines by the landscape-client. They are using a Full license to register instead of a Virtual one. Information from the client: Ubuntu 14.04.5 LTS --------------------------------------- landscape-client 14.12-0ubuntu6.14.04.2 --------------------------------------- # cat /sys/class/dmi/id/sys_vendor Apache Software Foundation --------------------------------------- lscpu: Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 1 On-line CPU(s) list: 0 Thread(s) per core: 1 Core(s) per socket: 1 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 42 Stepping: 1 CPU MHz: 2299.998 BogoMIPS: 4599.99 Hypervisor vendor: KVM Virtualization type: full L1d cache: 32K L1i cache: 32K L2 cache: 4096K NUMA node0 CPU(s): 0 ---------------------------------------
2018-03-27 16:03:11 Simon Poirier attachment added bionic.debdiff https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1754073/+attachment/5092476/+files/bionic.debdiff
2018-03-27 16:03:33 Simon Poirier attachment added artful.debdiff https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1754073/+attachment/5092477/+files/artful.debdiff
2018-03-27 16:03:52 Simon Poirier attachment added xenial.debdiff https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1754073/+attachment/5092485/+files/xenial.debdiff
2018-03-27 16:04:19 Simon Poirier attachment added trusty.debdiff https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1754073/+attachment/5092486/+files/trusty.debdiff
2018-03-27 16:20:43 Ubuntu Foundations Team Bug Bot tags lds-squad lds-squad patch
2018-03-27 16:20:51 Ubuntu Foundations Team Bug Bot bug added subscriber Ubuntu Sponsors Team
2018-03-27 19:08:17 Eric Desrochers bug added subscriber Eric Desrochers
2018-03-28 21:55:47 Eric Desrochers landscape-client (Ubuntu): status Confirmed In Progress
2018-03-28 21:56:03 Eric Desrochers landscape-client (Ubuntu): assignee Simon Poirier (simpoir)
2018-03-28 21:56:19 Eric Desrochers landscape-client (Ubuntu): importance Undecided Medium
2018-03-29 12:52:54 Karify DevOps bug added subscriber Karify DevOps
2018-03-29 13:52:32 Simon Poirier description [Impact]  * This issue affects users of Apache Cloudstack instances by failing to    detect the hypervisor type and reporting the clients as running on    a physical machine instead of on KVM.  * This fix extends dmi vendor mapping, so that clouds customizing sys_vendor    chassis_vendor or bios_vendor values (e.g. CloudStack, DigitalOcean)    still get detected as KVM instances. [Test Case] The issue can be reproduced on libvirt/kvm. uvt-kvm create vm virsh edit vm <os> ... <smbios mode='sysinfo'/> </os> <sysinfo type="smbios">   <system>     <entry name='manufacturer'>Apache Software Foundation</entry>     <entry name='product'>CloudStack KVM Hypervisor</entry>   </system> </sysinfo> <cpu match='exact'> <!-- defaults to qemu, which would me detected correctly -->   <model fallback='allow'>core2duo</model>   <vendor>Intel</vendor> </cpu> virsh destroy vm && virsh start vm uvt-kvm ssh vm --insecure sudo landscape-config --log-level=debug -a devel --silent -t testclient # will fail registering, but that's not relevant to the vm-type detection grep vm-info /var/log/landscape/broker.log # expected output is "KVM", and will be empty because of this bug [Regression Potential]  * Like the previous update, this change is local and only affects vm-type    detection, which should be low-risk.  * Since we extend the current detection to fields we were not previously    looking at, one of the risks is to falsely detect clients as running    on KVM. This is why we took care to verify opposite scenarios in    addition to making sure the existing unit tests pass. Were such a regression to occur, it would have a low user impact, as being detected as VM you can use either physical or VM features, whereas the opposite (due to the bug fixed here) is not true. [Other Info]  * AWS and DigitalOcean instances have been fixed slightly differently in    the previous SRU, but we wanted to avoid repeating this for every other    cloud, thus extending the DMI field lookup instead of adding yet another    mapping value. [Original Description] Instances running on a Apache CloudStack that is using KVM as a hypervisor are not detected as virtual machines by the landscape-client. They are using a Full license to register instead of a Virtual one. Information from the client: Ubuntu 14.04.5 LTS --------------------------------------- landscape-client 14.12-0ubuntu6.14.04.2 --------------------------------------- # cat /sys/class/dmi/id/sys_vendor Apache Software Foundation --------------------------------------- lscpu: Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 1 On-line CPU(s) list: 0 Thread(s) per core: 1 Core(s) per socket: 1 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 42 Stepping: 1 CPU MHz: 2299.998 BogoMIPS: 4599.99 Hypervisor vendor: KVM Virtualization type: full L1d cache: 32K L1i cache: 32K L2 cache: 4096K NUMA node0 CPU(s): 0 --------------------------------------- [Impact]  * This issue affects users of Apache Cloudstack instances by failing to    detect the hypervisor type and reporting the clients as running on    a physical machine instead of on KVM.  * This fix extends dmi vendor mapping, so that clouds customizing sys_vendor    chassis_vendor or bios_vendor values (e.g. CloudStack, DigitalOcean)    still get detected as KVM instances. [Test Case] The issue can be reproduced on libvirt/kvm. uvt-kvm create vm virsh edit vm <os> ... <smbios mode='sysinfo'/> </os> <sysinfo type="smbios">   <system>     <entry name='manufacturer'>Apache Software Foundation</entry>     <entry name='product'>CloudStack KVM Hypervisor</entry>   </system> </sysinfo> <cpu match='exact'> <!-- defaults to qemu, which would me detected correctly -->   <model fallback='allow'>core2duo</model>   <vendor>Intel</vendor> </cpu> virsh destroy vm && virsh start vm uvt-kvm ssh vm --insecure sudo landscape-config --log-level=debug -a devel --silent -t testclient # will fail registering, but that's not relevant to the vm-type detection grep vm-info /var/log/landscape/broker.log # expected output is "KVM", and will be empty because of this bug [Regression Potential]  * Like the previous update, this change is local and only affects vm-type    detection, which should be low-risk.  * Since we extend the current detection to fields we were not previously    looking at, one of the risks is to falsely detect clients as running    on KVM. This is why we took care to verify opposite scenarios in    addition to making sure the existing unit tests pass. Were such a    regression to occur, it would have a low user impact, as being detected as    VM you can use either physical or VM license, whereas the opposite    (due to the bug fixed here) is not true. [Other Info]  * AWS and DigitalOcean instances have been fixed slightly differently in    the previous SRU, but we wanted to avoid repeating this for every other    cloud, thus extending the DMI field lookup instead of adding yet another    mapping value. [Original Description] Instances running on a Apache CloudStack that is using KVM as a hypervisor are not detected as virtual machines by the landscape-client. They are using a Full license to register instead of a Virtual one. Information from the client: Ubuntu 14.04.5 LTS --------------------------------------- landscape-client 14.12-0ubuntu6.14.04.2 --------------------------------------- # cat /sys/class/dmi/id/sys_vendor Apache Software Foundation --------------------------------------- lscpu: Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 1 On-line CPU(s) list: 0 Thread(s) per core: 1 Core(s) per socket: 1 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 42 Stepping: 1 CPU MHz: 2299.998 BogoMIPS: 4599.99 Hypervisor vendor: KVM Virtualization type: full L1d cache: 32K L1i cache: 32K L2 cache: 4096K NUMA node0 CPU(s): 0 ---------------------------------------
2018-03-29 15:15:54 Eric Desrochers landscape-client (Ubuntu): status In Progress Fix Committed
2018-03-29 15:40:19 Eric Desrochers bug added subscriber STS Sponsors
2018-03-29 15:41:57 Launchpad Janitor landscape-client (Ubuntu): status Fix Committed Fix Released
2018-04-05 08:53:33 Łukasz Zemczak landscape-client (Ubuntu Artful): status New Fix Committed
2018-04-05 08:53:35 Łukasz Zemczak bug added subscriber Ubuntu Stable Release Updates Team
2018-04-05 08:53:36 Łukasz Zemczak bug added subscriber SRU Verification
2018-04-05 08:53:40 Łukasz Zemczak tags lds-squad patch lds-squad patch verification-needed verification-needed-artful
2018-04-05 09:02:38 Łukasz Zemczak landscape-client (Ubuntu Xenial): status New Fix Committed
2018-04-05 09:02:43 Łukasz Zemczak tags lds-squad patch verification-needed verification-needed-artful lds-squad patch verification-needed verification-needed-artful verification-needed-xenial
2018-04-05 09:04:33 Łukasz Zemczak removed subscriber Ubuntu Sponsors Team
2018-04-05 09:04:51 Łukasz Zemczak landscape-client (Ubuntu Trusty): status New Fix Committed
2018-04-05 09:04:57 Łukasz Zemczak tags lds-squad patch verification-needed verification-needed-artful verification-needed-xenial lds-squad patch verification-needed verification-needed-artful verification-needed-trusty verification-needed-xenial
2018-04-24 14:49:46 Alex Moldovan tags lds-squad patch verification-needed verification-needed-artful verification-needed-trusty verification-needed-xenial lds-squad patch verification-done-trusty verification-done-xenial verification-needed verification-needed-artful
2018-04-24 16:20:05 Alex Moldovan tags lds-squad patch verification-done-trusty verification-done-xenial verification-needed verification-needed-artful lds-squad patch verification-done-artful verification-done-trusty verification-done-xenial verification-needed
2018-04-24 16:21:25 Alex Moldovan tags lds-squad patch verification-done-artful verification-done-trusty verification-done-xenial verification-needed lds-squad patch verification-done-artful verification-done-trusty verification-done-xenial
2018-05-02 02:13:14 Launchpad Janitor landscape-client (Ubuntu Trusty): status Fix Committed Fix Released
2018-05-02 02:13:23 Chris Halse Rogers removed subscriber Ubuntu Stable Release Updates Team
2018-05-02 02:13:47 Launchpad Janitor landscape-client (Ubuntu Xenial): status Fix Committed Fix Released
2018-05-02 02:20:50 Launchpad Janitor landscape-client (Ubuntu Artful): status Fix Committed Fix Released
2018-05-04 12:55:42 Eric Desrochers removed subscriber STS Sponsors