group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1828217@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package landscape-client - 18.01-0ubuntu3.4

---------------
landscape-client (18.01-0ubuntu3.4) bionic; urgency=medium

  * d/p/product-name-vminfo-1828217.patch: Add product_name to things scanned
    for vm_info (LP: #1828217)
  * d/landscape-client.postinst: Set default value if data_path is
    missing. (LP: #1728681)
  * d/p/stagger-launch-1788518.patch: Add option to stagger launch of broker
    plugins. (LP: #1788518)
  * d/landscape-client.init: Fix init script stop action (LP: #1833137)

 -- Simon Poirier <simon.poirier@xxxxxxxxxxxxx>  Thu, 27 Jun 2019
11:07:30 -0400

** Changed in: landscape-client (Ubuntu Bionic)
       Status: Fix Committed => Fix Released

** Changed in: landscape-client (Ubuntu Disco)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1828217

Title:
  Machine not being detected as VM

Status in Landscape Client:
  Fix Committed
Status in landscape-client package in Ubuntu:
  Fix Released
Status in landscape-client source package in Xenial:
  Fix Committed
Status in landscape-client source package in Bionic:
  Fix Released
Status in landscape-client source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * Some KVM hypervisors are incorrectly detected by landscape-client,
     thus making it impossible to make use of VM license seats.  

   * This upload extend the scanning to additional sys/class/dmi/id fields
     for known VM markers

  [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'>my fancy cloud</entry>
      <entry name='product'>my fancy KVM</entry>
    </system>
    <chassis>
      <entry name='manufacturer'>my fancy cloud</entry>
    </chassis>
  </sysinfo>

  
  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]

   * The change is simple and scans an additional file for vm info.
     It's very similar to previous patches and is unlikely to regress. 

   * Assuming this patch goes wrong, false positives may be detected as
     KVM. This would have minimal user impact VM can be used on full seats.

  [Original description]
  For a customer, he was unable to approve his VMs on Landscape hosted by Canonical.

  Customer is running trusty which originally had installed:
  ii landscape-client 14.12-0ubuntu6.14.04.4 i386 The Landscape administration system client
  ii landscape-common 14.12-0ubuntu6.14.04.4 i386 The Landscape administration system client
  We also tried to install from PPA ppa:landscape/17.03, upgraded the client and restarted it, but still no success on approving the machines.

  Example of /proc/cpuinfo:

  processor	: 3
  vendor_id	: GenuineIntel
  cpu family	: 6
  model		: 13
  model name	: QEMU Virtual CPU version (cpu64-rhel6)
  stepping	: 3
  microcode	: 0x1
  cpu MHz		: 2393.998
  cache size	: 4096 KB
  physical id	: 3
  siblings	: 1
  core id		: 0
  cpu cores	: 1
  apicid		: 3
  initial apicid	: 3
  fdiv_bug	: no
  f00f_bug	: no
  coma_bug	: no
  fpu		: yes
  fpu_exception	: yes
  cpuid level	: 4
  wp		: yes
  flags		: fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pse36 clflush mmx fxsr sse sse2 syscall nx lm eagerfpu pni cx16 hypervisor lahf_lm
  bogomips	: 4787.99
  clflush size	: 64
  cache_alignment	: 64
  address sizes	: 40 bits physical, 48 bits virtual
  power management:

  SF case: 00225757
  Let me know if you require further information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/landscape-client/+bug/1828217/+subscriptions