| 2018-08-21 14:49:21 |
Simon Poirier |
bug |
|
|
added bug |
| 2018-09-11 23:40:31 |
Simon Poirier |
landscape-client (Ubuntu): status |
New |
Fix Committed |
|
| 2018-09-11 23:40:37 |
Simon Poirier |
landscape-client (Ubuntu): status |
Fix Committed |
New |
|
| 2018-09-14 00:07:06 |
Simon Poirier |
summary |
vm_type for nutanix cloud instances |
backport upstream landscape-client fixes |
|
| 2018-09-14 00:07:40 |
Simon Poirier |
description |
Landscape client does not properly report vm_type for Nutanix cloud instances.
DMI id for those instances are:
sys_vendor: Nutanix
bios_vendor: SeaBIOS
chassis_vendor: Red Hat |
[Impact]
This bug is for inclusion of a limited collection of upstream fixes affecting
some of landscape features such as
* The dmi id for Nutanix cloud instances was added to the detection list
for it to be properly detected as KVM.
* Various corrections related to release-upgrades (LP: #1699179) performed
by landscape. Those should address cases of failure to upgrade, failure
to report upgrade success, failure to reboot after an upgrade.
* Decoding of unicode tags when running scripts and using python3 client.
This change is intentionally left out of trusty and xenial clients, for
which landscape-client run on python2.7 and is different enough in
its encoding handling. (LP: #1765518)
[Test Case]
* Tagging a client with accented characters and running a simple
"echo script" should be enough to validate the encoding change.
* For the release-upgrade, one should be able to trigger one from landscape
running on trusty or xenial. That upgrade should be reported as a success
by landscape. A reboot command following that upgrade should also
work, accompanied by a report of systemd errors which may have been raised
during the action.
[Regression Potential]
* The hypervisor change is both trivial and similar to previous changes.
* The tag encoding change for scripts is equally trivial for recent clients.
It affects only code related to running shell script and, assuming bad
system encoding, should still work the same for ASCII tags.
However, the nature of python2.7 handling of encoding for trusty and xenial
is different enough for this patch not to be included for them, thus
avoiding regressions on those clients.
* The patch which avoids apt-locks during an upgrade does have some potential
attached. However since it's already released in bionic and cosmic,
it's fairly well tested.
* The upgrade success reporting patch should be safe as it's only an earlier
import of a library which will get touched during the upgrade. Worst case
scenario, it would only fail faster.
* The reboot patch is not quite trivial but should be safe. It only adds an
additional error handler in cases where shutdown command fails in order
to try an additional method. Normal success behaviour is unchanged.
[Other Info]
* Patches are already in the upstreams trunk.
* Those changes have been tested by some affected users |
|
| 2018-09-14 00:08:50 |
Simon Poirier |
attachment added |
|
cosmic.debdiff https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1788219/+attachment/5188637/+files/cosmic.debdiff |
|
| 2018-09-14 00:09:22 |
Simon Poirier |
attachment added |
|
bionic.debdiff https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1788219/+attachment/5188638/+files/bionic.debdiff |
|
| 2018-09-14 00:10:02 |
Simon Poirier |
attachment added |
|
xenial.debdiff https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1788219/+attachment/5188639/+files/xenial.debdiff |
|
| 2018-09-14 00:10:33 |
Simon Poirier |
attachment added |
|
trusty.debdiff https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1788219/+attachment/5188640/+files/trusty.debdiff |
|
| 2018-09-14 00:21:57 |
Ubuntu Foundations Team Bug Bot |
tags |
|
patch |
|
| 2018-09-14 00:22:05 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2018-09-18 11:53:04 |
Eric Desrochers |
bug |
|
|
added subscriber Eric Desrochers |
| 2018-09-18 11:53:25 |
Eric Desrochers |
nominated for series |
|
Ubuntu Trusty |
|
| 2018-09-18 11:53:25 |
Eric Desrochers |
bug task added |
|
landscape-client (Ubuntu Trusty) |
|
| 2018-09-18 11:53:25 |
Eric Desrochers |
nominated for series |
|
Ubuntu Cosmic |
|
| 2018-09-18 11:53:25 |
Eric Desrochers |
bug task added |
|
landscape-client (Ubuntu Cosmic) |
|
| 2018-09-18 11:53:25 |
Eric Desrochers |
nominated for series |
|
Ubuntu Bionic |
|
| 2018-09-18 11:53:25 |
Eric Desrochers |
bug task added |
|
landscape-client (Ubuntu Bionic) |
|
| 2018-09-18 11:53:25 |
Eric Desrochers |
nominated for series |
|
Ubuntu Xenial |
|
| 2018-09-18 11:53:25 |
Eric Desrochers |
bug task added |
|
landscape-client (Ubuntu Xenial) |
|
| 2018-09-18 13:44:38 |
Simon Poirier |
description |
[Impact]
This bug is for inclusion of a limited collection of upstream fixes affecting
some of landscape features such as
* The dmi id for Nutanix cloud instances was added to the detection list
for it to be properly detected as KVM.
* Various corrections related to release-upgrades (LP: #1699179) performed
by landscape. Those should address cases of failure to upgrade, failure
to report upgrade success, failure to reboot after an upgrade.
* Decoding of unicode tags when running scripts and using python3 client.
This change is intentionally left out of trusty and xenial clients, for
which landscape-client run on python2.7 and is different enough in
its encoding handling. (LP: #1765518)
[Test Case]
* Tagging a client with accented characters and running a simple
"echo script" should be enough to validate the encoding change.
* For the release-upgrade, one should be able to trigger one from landscape
running on trusty or xenial. That upgrade should be reported as a success
by landscape. A reboot command following that upgrade should also
work, accompanied by a report of systemd errors which may have been raised
during the action.
[Regression Potential]
* The hypervisor change is both trivial and similar to previous changes.
* The tag encoding change for scripts is equally trivial for recent clients.
It affects only code related to running shell script and, assuming bad
system encoding, should still work the same for ASCII tags.
However, the nature of python2.7 handling of encoding for trusty and xenial
is different enough for this patch not to be included for them, thus
avoiding regressions on those clients.
* The patch which avoids apt-locks during an upgrade does have some potential
attached. However since it's already released in bionic and cosmic,
it's fairly well tested.
* The upgrade success reporting patch should be safe as it's only an earlier
import of a library which will get touched during the upgrade. Worst case
scenario, it would only fail faster.
* The reboot patch is not quite trivial but should be safe. It only adds an
additional error handler in cases where shutdown command fails in order
to try an additional method. Normal success behaviour is unchanged.
[Other Info]
* Patches are already in the upstreams trunk.
* Those changes have been tested by some affected users |
[Impact]
This bug is for inclusion of a limited collection of upstream fixes affecting
some of landscape features such as
* The dmi id for Nutanix cloud instances was added to the detection list
for it to be properly detected as KVM.
* Various corrections related to release-upgrades (LP: #1699179) performed
by landscape. Those should address cases of failure to upgrade, failure
to report upgrade success, failure to reboot after an upgrade
(LP: #1670291)
* Decoding of unicode tags when running scripts and using python3 client.
This change is intentionally left out of trusty and xenial clients, for
which landscape-client run on python2.7 and is different enough in
its encoding handling. (LP: #1765518)
[Test Case]
* Tagging a client with accented characters and running a simple
"echo script" should be enough to validate the encoding change.
* For the release-upgrade, one should be able to trigger one from landscape
running on trusty or xenial. That upgrade should be reported as a success
by landscape. A reboot command following that upgrade should also
work, accompanied by a report of systemd errors which may have been raised
during the action.
[Regression Potential]
* The hypervisor change is both trivial and similar to previous changes.
* The tag encoding change for scripts is equally trivial for recent clients.
It affects only code related to running shell script and, assuming bad
system encoding, should still work the same for ASCII tags.
However, the nature of python2.7 handling of encoding for trusty and xenial
is different enough for this patch not to be included for them, thus
avoiding regressions on those clients.
* The patch which avoids apt-locks during an upgrade does have some potential
attached. However since it's already released in bionic and cosmic,
it's fairly well tested.
* The upgrade success reporting patch should be safe as it's only an earlier
import of a library which will get touched during the upgrade. Worst case
scenario, it would only fail faster.
* The reboot patch is not quite trivial but should be safe. It only adds an
additional error handler in cases where shutdown command fails in order
to try an additional method. Normal success behaviour is unchanged.
[Other Info]
* Patches are already in the upstreams trunk.
* Those changes have been tested by some affected users |
|
| 2018-11-01 13:20:28 |
Simon Poirier |
merge proposal linked |
|
https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/358162 |
|
| 2018-11-01 13:21:37 |
Simon Poirier |
merge proposal linked |
|
https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/358163 |
|
| 2018-11-01 13:23:02 |
Simon Poirier |
merge proposal linked |
|
https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/358164 |
|
| 2018-11-15 00:56:44 |
Simon Poirier |
merge proposal unlinked |
https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/358162 |
|
|
| 2018-11-15 00:58:10 |
Simon Poirier |
merge proposal unlinked |
https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/358163 |
|
|
| 2018-11-15 00:59:31 |
Simon Poirier |
merge proposal unlinked |
https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/358164 |
|
|
| 2018-12-10 16:48:09 |
Simon Poirier |
attachment removed |
cosmic.debdiff https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1788219/+attachment/5188637/+files/cosmic.debdiff |
|
|
| 2018-12-10 16:48:18 |
Simon Poirier |
attachment removed |
bionic.debdiff https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1788219/+attachment/5188638/+files/bionic.debdiff |
|
|
| 2018-12-10 16:48:28 |
Simon Poirier |
attachment removed |
xenial.debdiff https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1788219/+attachment/5188639/+files/xenial.debdiff |
|
|
| 2018-12-10 16:48:36 |
Simon Poirier |
attachment removed |
trusty.debdiff https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1788219/+attachment/5188640/+files/trusty.debdiff |
|
|
| 2018-12-10 17:28:49 |
Simon Poirier |
description |
[Impact]
This bug is for inclusion of a limited collection of upstream fixes affecting
some of landscape features such as
* The dmi id for Nutanix cloud instances was added to the detection list
for it to be properly detected as KVM.
* Various corrections related to release-upgrades (LP: #1699179) performed
by landscape. Those should address cases of failure to upgrade, failure
to report upgrade success, failure to reboot after an upgrade
(LP: #1670291)
* Decoding of unicode tags when running scripts and using python3 client.
This change is intentionally left out of trusty and xenial clients, for
which landscape-client run on python2.7 and is different enough in
its encoding handling. (LP: #1765518)
[Test Case]
* Tagging a client with accented characters and running a simple
"echo script" should be enough to validate the encoding change.
* For the release-upgrade, one should be able to trigger one from landscape
running on trusty or xenial. That upgrade should be reported as a success
by landscape. A reboot command following that upgrade should also
work, accompanied by a report of systemd errors which may have been raised
during the action.
[Regression Potential]
* The hypervisor change is both trivial and similar to previous changes.
* The tag encoding change for scripts is equally trivial for recent clients.
It affects only code related to running shell script and, assuming bad
system encoding, should still work the same for ASCII tags.
However, the nature of python2.7 handling of encoding for trusty and xenial
is different enough for this patch not to be included for them, thus
avoiding regressions on those clients.
* The patch which avoids apt-locks during an upgrade does have some potential
attached. However since it's already released in bionic and cosmic,
it's fairly well tested.
* The upgrade success reporting patch should be safe as it's only an earlier
import of a library which will get touched during the upgrade. Worst case
scenario, it would only fail faster.
* The reboot patch is not quite trivial but should be safe. It only adds an
additional error handler in cases where shutdown command fails in order
to try an additional method. Normal success behaviour is unchanged.
[Other Info]
* Patches are already in the upstreams trunk.
* Those changes have been tested by some affected users |
[Impact]
* The dmi id for Nutanix cloud instances was added to the detection list
for it to be properly detected as KVM.
[Test Case]
* create a vm
* virsh edit tst (and create or update sysinfo fields like https://pastebin.ubuntu.com/p/C5mkc2B7rx/)
* install landscape-client/common and call landscape-config
* see the computer is detected as kvm
[Regression Potential]
* The hypervisor detection change is both trivial and similar to previous changes and is specific enough not to conflict with other hypervisors.
[Other Info]
* Patches are already in the upstreams trunk.
* Changes have been tested by some affected users |
|
| 2018-12-10 17:29:59 |
Simon Poirier |
description |
[Impact]
* The dmi id for Nutanix cloud instances was added to the detection list
for it to be properly detected as KVM.
[Test Case]
* create a vm
* virsh edit tst (and create or update sysinfo fields like https://pastebin.ubuntu.com/p/C5mkc2B7rx/)
* install landscape-client/common and call landscape-config
* see the computer is detected as kvm
[Regression Potential]
* The hypervisor detection change is both trivial and similar to previous changes and is specific enough not to conflict with other hypervisors.
[Other Info]
* Patches are already in the upstreams trunk.
* Changes have been tested by some affected users |
[Impact]
* The dmi id for Nutanix cloud instances was added to the detection list
for it to be properly detected as KVM.
[Test Case]
* create a vm
* virsh edit vm_name (and create or update sysinfo fields like https://pastebin.ubuntu.com/p/C5mkc2B7rx/)
* install landscape-client/common and call landscape-config
* see the computer is detected as kvm
[Regression Potential]
* The hypervisor detection change is both trivial and similar to previous changes and is specific enough not to conflict with other hypervisors.
[Other Info]
* Patches are already in the upstreams trunk.
* Changes have been tested by some affected users |
|
| 2018-12-10 17:30:40 |
Simon Poirier |
description |
[Impact]
* The dmi id for Nutanix cloud instances was added to the detection list
for it to be properly detected as KVM.
[Test Case]
* create a vm
* virsh edit vm_name (and create or update sysinfo fields like https://pastebin.ubuntu.com/p/C5mkc2B7rx/)
* install landscape-client/common and call landscape-config
* see the computer is detected as kvm
[Regression Potential]
* The hypervisor detection change is both trivial and similar to previous changes and is specific enough not to conflict with other hypervisors.
[Other Info]
* Patches are already in the upstreams trunk.
* Changes have been tested by some affected users |
[Impact]
* The dmi id for Nutanix cloud instances was added to the detection list
for it to be properly detected as KVM.
[Test Case]
* create a vm (uvt-kvm create --no-start vm_name release=xenial)
* virsh edit vm_name (and create or update sysinfo fields like https://pastebin.ubuntu.com/p/C5mkc2B7rx/)
* install landscape-client/common and call landscape-config
* see the computer is detected as kvm
[Regression Potential]
* The hypervisor detection change is both trivial and similar to previous changes and is specific enough not to conflict with other hypervisors.
[Other Info]
* Patches are already in the upstreams trunk.
* Changes have been tested by some affected users |
|
| 2018-12-11 23:28:45 |
Simon Poirier |
summary |
backport upstream landscape-client fixes |
vm_type detection for nutanix cloud instances |
|
| 2018-12-11 23:36:41 |
Simon Poirier |
description |
[Impact]
* The dmi id for Nutanix cloud instances was added to the detection list
for it to be properly detected as KVM.
[Test Case]
* create a vm (uvt-kvm create --no-start vm_name release=xenial)
* virsh edit vm_name (and create or update sysinfo fields like https://pastebin.ubuntu.com/p/C5mkc2B7rx/)
* install landscape-client/common and call landscape-config
* see the computer is detected as kvm
[Regression Potential]
* The hypervisor detection change is both trivial and similar to previous changes and is specific enough not to conflict with other hypervisors.
[Other Info]
* Patches are already in the upstreams trunk.
* Changes have been tested by some affected users |
[Impact]
* The dmi id for Nutanix cloud instances was added to the detection list
for it to be properly detected as KVM.
[Test Case]
* create a vm (uvt-kvm create --no-start vm_name release=xenial)
* virsh edit vm_name (and create or update sysinfo manufacturer to be "nutanix", like https://pastebin.ubuntu.com/p/C5mkc2B7rx/)
* install landscape-client/common and call landscape-config
* see the computer is detected as kvm
[Regression Potential]
* The hypervisor detection change is both trivial and similar to previous changes and is specific enough not to conflict with other hypervisors.
[Other Info]
* Patches are already in the upstreams trunk.
* Changes have been tested by some affected users |
|
| 2018-12-11 23:51:49 |
Simon Poirier |
merge proposal linked |
|
https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/358162 |
|
| 2018-12-11 23:52:07 |
Simon Poirier |
merge proposal linked |
|
https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/358163 |
|
| 2018-12-11 23:52:24 |
Simon Poirier |
merge proposal linked |
|
https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/358164 |
|
| 2018-12-11 23:52:39 |
Simon Poirier |
merge proposal linked |
|
https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/358165 |
|
| 2018-12-13 12:10:58 |
Andreas Hasenack |
landscape-client (Ubuntu): status |
New |
Fix Released |
|
| 2018-12-13 12:11:05 |
Andreas Hasenack |
landscape-client (Ubuntu): assignee |
|
Simon Poirier (simpoir) |
|
| 2018-12-13 12:19:50 |
Andreas Hasenack |
landscape-client (Ubuntu Cosmic): status |
New |
In Progress |
|
| 2018-12-13 12:19:54 |
Andreas Hasenack |
landscape-client (Ubuntu Cosmic): assignee |
|
Simon Poirier (simpoir) |
|
| 2018-12-13 12:26:57 |
Andreas Hasenack |
landscape-client (Ubuntu Bionic): status |
New |
In Progress |
|
| 2018-12-13 12:27:02 |
Andreas Hasenack |
landscape-client (Ubuntu Bionic): assignee |
|
Simon Poirier (simpoir) |
|
| 2018-12-13 12:34:22 |
Andreas Hasenack |
landscape-client (Ubuntu Xenial): status |
New |
In Progress |
|
| 2018-12-13 12:34:28 |
Andreas Hasenack |
landscape-client (Ubuntu Xenial): assignee |
|
Simon Poirier (simpoir) |
|
| 2018-12-13 12:45:02 |
Andreas Hasenack |
landscape-client (Ubuntu Trusty): status |
New |
In Progress |
|
| 2018-12-13 12:45:09 |
Andreas Hasenack |
landscape-client (Ubuntu Trusty): assignee |
|
Simon Poirier (simpoir) |
|
| 2018-12-14 11:49:40 |
Timo Aaltonen |
landscape-client (Ubuntu Cosmic): status |
In Progress |
Fix Committed |
|
| 2018-12-14 11:49:42 |
Timo Aaltonen |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2018-12-14 11:49:43 |
Timo Aaltonen |
bug |
|
|
added subscriber SRU Verification |
| 2018-12-14 11:49:46 |
Timo Aaltonen |
tags |
patch |
patch verification-needed verification-needed-cosmic |
|
| 2018-12-14 11:50:03 |
Timo Aaltonen |
removed subscriber Ubuntu Sponsors Team |
|
|
|
| 2018-12-14 11:52:27 |
Timo Aaltonen |
landscape-client (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2018-12-14 11:52:32 |
Timo Aaltonen |
tags |
patch verification-needed verification-needed-cosmic |
patch verification-needed verification-needed-bionic verification-needed-cosmic |
|
| 2018-12-14 11:56:55 |
Timo Aaltonen |
landscape-client (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2018-12-14 11:57:00 |
Timo Aaltonen |
tags |
patch verification-needed verification-needed-bionic verification-needed-cosmic |
patch verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-xenial |
|
| 2018-12-14 12:09:56 |
Timo Aaltonen |
landscape-client (Ubuntu Trusty): status |
In Progress |
Fix Committed |
|
| 2018-12-14 12:10:00 |
Timo Aaltonen |
tags |
patch verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-xenial |
patch verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-trusty verification-needed-xenial |
|
| 2019-02-04 21:28:22 |
Simon Poirier |
tags |
patch verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-trusty verification-needed-xenial |
patch verification-done verification-done-bionic verification-done-cosmic verification-done-trusty verification-done-xenial |
|
| 2019-02-04 21:29:08 |
Simon Poirier |
tags |
patch verification-done verification-done-bionic verification-done-cosmic verification-done-trusty verification-done-xenial |
patch verification-done-bionic verification-done-cosmic verification-done-trusty verification-done-xenial |
|
| 2019-02-05 18:25:02 |
Brian Murray |
landscape-client (Ubuntu Cosmic): status |
Fix Committed |
Incomplete |
|
| 2019-02-05 18:25:05 |
Brian Murray |
landscape-client (Ubuntu Bionic): status |
Fix Committed |
Incomplete |
|
| 2019-02-05 18:25:07 |
Brian Murray |
landscape-client (Ubuntu Xenial): status |
Fix Committed |
Incomplete |
|
| 2019-02-05 18:25:09 |
Brian Murray |
landscape-client (Ubuntu Trusty): status |
Fix Committed |
Incomplete |
|
| 2019-02-07 14:28:02 |
Simon Poirier |
landscape-client (Ubuntu Trusty): status |
Incomplete |
Fix Committed |
|
| 2019-02-07 14:28:05 |
Simon Poirier |
landscape-client (Ubuntu Xenial): status |
Incomplete |
Fix Committed |
|
| 2019-02-07 14:28:08 |
Simon Poirier |
landscape-client (Ubuntu Bionic): status |
Incomplete |
Fix Committed |
|
| 2019-02-07 14:28:11 |
Simon Poirier |
landscape-client (Ubuntu Cosmic): status |
Incomplete |
Fix Committed |
|
| 2019-02-07 19:36:27 |
Launchpad Janitor |
landscape-client (Ubuntu Cosmic): status |
Fix Committed |
Fix Released |
|
| 2019-02-07 19:37:09 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2019-02-07 19:38:16 |
Launchpad Janitor |
landscape-client (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2019-02-07 19:42:54 |
Launchpad Janitor |
landscape-client (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2019-02-07 19:43:51 |
Launchpad Janitor |
landscape-client (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
