sts-sponsors team mailing list archive

[Eric Desrochers <eric.desrochers@xxxxxxxxxxxxx>]

I'll sponsor Simon's debdiff found in LP: #1742531 as soon as landscape-
client is consider valid for bionic.

For now it is stuck in bionic-proposed, waiting for the non-i386/amd64
builds to be back operational.

# Ubuntu excuses page
landscape-client (16.03-0ubuntu4 to 16.03-0ubuntu5)
Maintainer: Ubuntu Developers
0 days old
missing build on arm64: landscape-client, landscape-common (from 16.03-0ubuntu4)
missing build on armhf: landscape-client, landscape-common (from 16.03-0ubuntu4)
missing build on ppc64el: landscape-client, landscape-common (from 16.03-0ubuntu4)
missing build on s390x: landscape-client, landscape-common (from 16.03-0ubuntu4)
Not considered

- Eric

-- 
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:
  In Progress
Status in landscape-client package in Ubuntu:
  Fix Committed
Status in landscape-client source package in Trusty:
  Confirmed
Status in landscape-client source package in Xenial:
  Confirmed
Status in landscape-client source package in Zesty:
  Confirmed
Status in landscape-client source package in Artful:
  Confirmed
Status in landscape-client source package in Bionic:
  Fix Committed

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