sts-sponsors team mailing list archive
-
sts-sponsors team
-
Mailing list archive
-
Message #00259
[Bug 1743232] [NEW] set vm_info to kvm for digitalocean instances
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 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:
New
Status in landscape-client package in Ubuntu:
In Progress
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:
In Progress
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
Follow ups
-
[Bug 1743232] Re: set vm_info to kvm for digitalocean instances
From: Launchpad Bug Tracker, 2018-02-01
-
[Bug 1743232] Re: set vm_info to kvm for digitalocean instances
From: Launchpad Bug Tracker, 2018-02-01
-
[Bug 1743232] Re: set vm_info to kvm for digitalocean instances
From: Launchpad Bug Tracker, 2018-02-01
-
[Bug 1743232] Update Released
From: Łukasz Zemczak, 2018-02-01
-
[Bug 1743232] Re: set vm_info to kvm for digitalocean instances
From: Eric Desrochers, 2018-01-26
-
[Bug 1743232] Re: set vm_info to kvm for digitalocean instances
From: David Coronel, 2018-01-26
-
[Bug 1743232] Re: set vm_info to kvm for digitalocean instances
From: David Coronel, 2018-01-26
-
[Bug 1743232] Re: set vm_info to kvm for digitalocean instances
From: David Coronel, 2018-01-26
-
[Bug 1743232] Re: set vm_info to kvm for digitalocean instances
From: David Coronel, 2018-01-26
-
[Bug 1743232] Re: set vm_info to kvm for digitalocean instances
From: Łukasz Zemczak, 2018-01-25
-
[Bug 1743232] Please test proposed package
From: Łukasz Zemczak, 2018-01-25
-
[Bug 1743232] Re: set vm_info to kvm for digitalocean instances
From: Łukasz Zemczak, 2018-01-25
-
[Bug 1743232] Re: set vm_info to kvm for digitalocean instances
From: Eric Desrochers, 2018-01-23
-
[Bug 1743232] Re: set vm_info to kvm for digitalocean instances
From: Launchpad Bug Tracker, 2018-01-23
-
[Bug 1743232] Re: set vm_info to kvm for digitalocean instances
From: Eric Desrochers, 2018-01-20
-
[Bug 1743232] Re: set vm_info to kvm for digitalocean instances
From: Eric Desrochers, 2018-01-16
-
[Bug 1743232] Re: set vm_info to kvm for digitalocean instances
From: Andreas Hasenack, 2018-01-16
-
[Bug 1743232] Re: set vm_info to kvm for digitalocean instances
From: Andreas Hasenack, 2018-01-16
-
[Bug 1743232] Re: set vm_info to kvm for digitalocean instances
From: Eric Desrochers, 2018-01-16
-
[Bug 1743232] Re: set vm_info to kvm for digitalocean instances
From: Eric Desrochers, 2018-01-15
-
[Bug 1743232] Re: set vm_info to kvm for digitalocean instances
From: Andreas Hasenack, 2018-01-15
-
[Bug 1743232] Re: set vm_info to kvm for digitalocean instances
From: Launchpad Bug Tracker, 2018-01-15
-
[Bug 1743232] Re: set vm_info to kvm for digitalocean instances
From: David Coronel, 2018-01-15
-
[Bug 1743232] [NEW] set vm_info to kvm for digitalocean instances
From: Launchpad Bug Tracker, 2018-01-14