** Attachment added: "digitalocean-xenial.png" https://bugs.launchpad.net/landscape-client/+bug/1743232/+attachment/5043543/+files/digitalocean-xenial.png
-- 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: Fix Committed 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 -- Mailing list: https://launchpad.net/~sts-sponsors Post to : [email protected] Unsubscribe : https://launchpad.net/~sts-sponsors More help : https://help.launchpad.net/ListHelp
