Public bug reported: [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 ** Affects: landscape-client Importance: Undecided Status: New ** Affects: landscape-client (Ubuntu) Importance: Medium Assignee: Eric Desrochers (slashd) Status: In Progress ** Affects: landscape-client (Ubuntu Trusty) Importance: Medium Assignee: Eric Desrochers (slashd) Status: Confirmed ** Affects: landscape-client (Ubuntu Xenial) Importance: Medium Assignee: Eric Desrochers (slashd) Status: Confirmed ** Affects: landscape-client (Ubuntu Zesty) Importance: Medium Assignee: Eric Desrochers (slashd) Status: Confirmed ** Affects: landscape-client (Ubuntu Artful) Importance: Medium Assignee: Eric Desrochers (slashd) Status: Confirmed ** Affects: landscape-client (Ubuntu Bionic) Importance: Medium Assignee: Eric Desrochers (slashd) Status: In Progress ** Tags: lds-squad sts sts-sponsor-slashd ** Also affects: landscape-client (Ubuntu) Importance: Undecided Status: New ** Also affects: landscape-client (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: landscape-client (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: landscape-client (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: landscape-client (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: landscape-client (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: landscape-client (Ubuntu Trusty) Status: New => Confirmed ** Changed in: landscape-client (Ubuntu Xenial) Status: New => Confirmed ** Changed in: landscape-client (Ubuntu Zesty) Status: New => Confirmed ** Changed in: landscape-client (Ubuntu Artful) Status: New => Confirmed ** Changed in: landscape-client (Ubuntu Bionic) Status: New => Confirmed ** Changed in: landscape-client (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: landscape-client (Ubuntu Xenial) Importance: Undecided => Critical ** Changed in: landscape-client (Ubuntu Xenial) Importance: Critical => Medium ** Changed in: landscape-client (Ubuntu Zesty) Importance: Undecided => Medium ** Changed in: landscape-client (Ubuntu Artful) Importance: Undecided => Medium ** Changed in: landscape-client (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: landscape-client (Ubuntu Trusty) Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: landscape-client (Ubuntu Xenial) Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: landscape-client (Ubuntu Zesty) Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: landscape-client (Ubuntu Artful) Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: landscape-client (Ubuntu Bionic) Assignee: (unassigned) => Eric Desrochers (slashd) ** Tags added: lds-squad sts ** Tags added: sts-sponsor-slashd ** Changed in: landscape-client (Ubuntu Bionic) Status: Confirmed => In Progress ** Description changed: [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 + * 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 + * 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 + * 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 + * Upstream commit: + https://github.com/CanonicalLtd/landscape-client/pull/24/files -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743232 Title: set vm_info to kvm for digitalocean instances To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1743232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
