group.of.nepali.translators team mailing list archive
-
group.of.nepali.translators team
-
Mailing list archive
-
Message #22041
[Bug 1743232] Re: set vm_info to kvm for digitalocean instances
** Changed in: landscape-client
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/1743232
Title:
set vm_info to kvm for digitalocean instances
Status in Landscape Client:
Fix Released
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 Artful:
Fix Released
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