group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1788219@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package landscape-client -
16.03-0ubuntu2.16.04.5

---------------
landscape-client (16.03-0ubuntu2.16.04.5) xenial; urgency=medium

  * debian/patches/nutanix-kvm.patch: Update vm_info.py to include Nutanix
    hypervisor (LP: #1788219)
  * Fixes for release-upgrade (LP: #1699179).
    - debian/patches/1699179-release-upgrade-check.diff: Check if ubuntu-
      release-upgrader is running before apt-update. (LP: #1699179)
    - debian/patches/release-upgrade-success.patch: Enable landscape-client to
      survive trusty upgrade. (LP: #1670291)
    - debian/patches/post-upgrade-reboot.patch: Force reboot operation in
      case systemd fails. (LP: #1670291)
  * debian/patches/1616116-resync-loop.patch:
    Clear hash id database on package resync. (LP: #1616116)

 -- Simon Poirier <simon.poirier@xxxxxxxxxxxxx>  Tue, 27 Nov 2018
09:24:22 -0500

** Changed in: landscape-client (Ubuntu Trusty)
       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/1788219

Title:
  vm_type detection for nutanix cloud instances

Status in landscape-client package in Ubuntu:
  Fix Released
Status in landscape-client source package in Trusty:
  Fix Released
Status in landscape-client source package in Xenial:
  Fix Released
Status in landscape-client source package in Bionic:
  Fix Released
Status in landscape-client source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * The dmi id for Nutanix cloud instances was added to the detection list
     for it to be properly detected as KVM.

   [Test Case]

   * create a vm (uvt-kvm create --no-start vm_name release=xenial)
   * virsh edit vm_name (and create or update sysinfo manufacturer to be "nutanix", like https://pastebin.ubuntu.com/p/C5mkc2B7rx/)
   * install landscape-client/common and call landscape-config
   * see the computer is detected as kvm

  [Regression Potential]

   * The hypervisor detection change is both trivial and similar to
  previous changes and is specific enough not to conflict with other
  hypervisors.

  [Other Info]

   * Patches are already in the upstreams trunk.
   * Changes have been tested by some affected users

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