sts-sponsors team mailing list archive

[Łukasz Zemczak <1743232@xxxxxxxxxxxxxxxxxx>]

Hello Eric, or anyone else affected,

Accepted landscape-client into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/landscape-
client/16.03-0ubuntu2.16.04.3 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

-- 
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1743232

Title:
  set vm_info to kvm for digitalocean instances

Status in Landscape Client:
  Fix Committed
Status in landscape-client package in Ubuntu:
  Fix Released
Status in landscape-client source package in Trusty:
  In Progress
Status in landscape-client source package in Xenial:
  Fix Committed
Status in landscape-client source package in Artful:
  Fix Committed
Status in landscape-client source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  digitalocean instance type is not a recognised VM type in Landscape
  and thus won't allow use of a Virtual Guest asset to register with.

  The digitalocean type uses a KVM-family hypervisor (displaying
  "digitalocean" in sys_vendor which landscape-client doesn't recognise,
  thus cannot associate/map to kvm)

  [Test Case]

   * Deploy a digitalocean instance
   * Look sys_vendor
     $ cat /sys/class/dmi/id/sys_vendor
     digitalocean

   * Install landscape-client
   * Register the client to the desired landscape-server
   * Verify "VM Type" to be "kvm" under the computer info (in landscape-server)

  [Regression Potential]

   * No regression anticipated, the fix is only adding a new entry
  mapping to recognize digitalocean instances.

  [Other Info]

   * Upstream commit:
     https://github.com/CanonicalLtd/landscape-client/pull/24/files

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