Public bug reported:
[ impact ]
* In replacing kpartx with losetup, earlier this year, grub-install
(grub-probe) started failing for bootable uefi buildd images on jammy.
This failure started around 2024-01-14.
* uefi buildd images don't build on jammy. Later suites appear to have
** Merge proposal linked:
https://code.launchpad.net/~simpoir/livecd-rootfs/+git/livecd-rootfs/+merge/464543
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062024
Title:
armhf doesn't build
suite will start generating uefi images again.
** Affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Assignee: Simon Poirier (simpoir)
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
I also verified landscape-client 19.12-0ubuntu10.1 from impish-proposed.
I used the same landscape-server-quickstart from ppa:landscape/19.10 as
previously, with the same database query to enable upgrading.
Again, upgrade tool downloaded and validated successfully on the proposed
version, with
I verified landscape-client 19.12-0ubuntu4.3 from focal-proposed.
I used landscape-server-quickstart from ppa:landscape/19.10 and registered the
proposed client against it.
Then I had to enable the upcoming upgrade tool to the server:
# sudo -u landscape psql landscape-standalone-main -c "insert
Verified landscape-client 18.01-0ubuntu3.6 on bionic by updating to the
bionic-proposed package.
I registered a new LXD container client on a SaaS account, triggered a
release upgrade. The upgrade tool downloaded, validated, launched and
the landscape activity completed successfully.
** Tags
** Changed in: landscape-client
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962539
Title:
python3-twisted breaks landscape-sysinfo
To manage
** Also affects: landscape-client
Importance: Undecided
Status: New
** Changed in: landscape-client
Status: New => In Progress
** Changed in: landscape-client
Importance: Undecided => Critical
** Changed in: landscape-client
Assignee: (unassigned) => Simo
** Changed in: landscape-client (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962539
Title:
python3-twisted breaks landscape-sysinfo
To manage
** Changed in: landscape-client (Ubuntu)
Status: Confirmed => In Progress
** Changed in: landscape-client (Ubuntu)
Assignee: (unassigned) => Simon Poirier (simpoir)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: landscape-client (Ubuntu Bionic)
Assignee: Simon Poirier (simpoir) => (unassigned)
** Changed in: landscape-client (Ubuntu Focal)
Assignee: Simon Poirier (simpoir) => (unassigned)
** Changed in: landscape-client (Ubuntu Groovy)
Assignee: Simon Poirier (s
** Also affects: landscape-client (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: landscape-client (Ubuntu Jammy)
Importance: Undecided
Assignee: Simon Poirier (simpoir)
Status: In Progress
--
You received this bug notification because you
** Changed in: landscape-client
Status: In Progress => Fix Committed
** Changed in: landscape-client
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I verified the fixes for groovy-proposed and focal-proposed packages
versions 19.12-0ubuntu5.1 and 19.12-0ubuntu4.2
I followed the test case without any issue.
Additionally, I also tried a few scenarios for terminating processes, which now
all terminate cleanly if stopped with SIGTERM, whether
** Information type changed from Proprietary to Public
** Project changed: landscape => landscape-client
** Changed in: landscape-client
Status: In Progress => Fix Committed
** Also affects: landscape-client (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
** Description changed:
[Impact]
* landscape-client services are prevented from starting if its older PIDs get
recycled.
* The exact conditions for the issue, are particularly more likely to occur
- on release upgrade.
+ on release upgrade. This is exacerbated by the fact
** Description changed:
[Impact]
- * landscape-client services are prevented from starting if its older PIDs get
-recycled.
+ * landscape-client services are prevented from starting if its older PIDs get
+ recycled.
- * The exact conditions for the issue, are particularly more
** Changed in: landscape-client
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1616116
Title:
Unrecoverable resyncs if DB is restored from backup
To
** Changed in: landscape-client (Ubuntu Hirsute)
Assignee: (unassigned) => Simon Poirier (simpoir)
** Changed in: landscape-client (Ubuntu Groovy)
Assignee: (unassigned) => Simon Poirier (simpoir)
** Changed in: landscape-client (Ubuntu Focal)
Assignee: (unassigned) =&
** Description changed:
+ [Impact]
+
+ * When launching an Ubuntu release-upgrade through landscape-client, the
+upgrade-tool fails GPG verification due to trusted apt key having changed
+location as of 18.04 LTS.
+
+ * The proposed patch extends gpg lookup path to include all
+
** Also affects: landscape-client (Ubuntu)
Importance: Undecided
Status: New
** Changed in: landscape-client (Ubuntu)
Status: New => Confirmed
** Also affects: landscape-client (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: landscape-client (Ubuntu
** Changed in: landscape
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1583276
Title:
glance restarted during image upload, image stuck in "saving"
I verified the fix by upgrading landcape-client from 16.03-0ubuntu2.16.04.7 to
16.03-0ubuntu2.16.04.8 on an Ubuntu 16.04 machine.
After the upgrade, the profile applied as expected.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done
Subsequent releases already had this corrected. I have updated the task
status.
** Changed in: landscape-client (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Mark and anyone affected. Just to clarify the remaining part of the
issue:
>From the various test scenarios which I have tried, the initial issue of
the client failing to restart in the presence of stale lock files and
sockets appears to be resolved. That is, lock files pointing to dead or
** Changed in: landscape-client (Ubuntu Focal)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870087
Title:
Old broker lockfile blocks landscape-client
main amd64 Packages
** Changed in: landscape-client (Ubuntu Xenial)
Assignee: (unassigned) => Simon Poirier (simpoir)
** Changed in: landscape-client (Ubuntu Xenial)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ub
** Merge proposal linked:
https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/387004
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886491
Title:
It looks like python-apt (1.1.0~beta1ubuntu0.16.04.7) created a regression and
elects to ignore
Acquire::AllowInsecureRepositories in favor of APT::Get::AllowUnauthenticated.
The simpler approach would likely be to backport the [trusted=true] fix
we've got working with later releases, instead of
I've verified the upgrade path on focal by triggering an update through
Landscape of packages landscape-client and landscape-common from
19.12-0ubuntu4 to 19.12-0ubuntu4.1
Upgrade went through, successfully leaving configuration subprocesses to
finish cleanly:
** Merge proposal linked:
https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/382682
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870087
Title:
The issue was fixed in python-apt =2.0.0
** Changed in: python-apt (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827857
Title:
Stuck on applying
** Description changed:
+ [Impact]
+
+ * landscape-client services are prevented from starting if its older PIDs get
+recycled.
+
+ * The exact conditions for the issue, are particularly more likely to occur
+on release upgrade.
+
+ * The proposed fix tries to verify existing locks
ent (Ubuntu Focal)
Assignee: (unassigned) => Simon Poirier (simpoir)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870087
Title:
Old broker lockfile blocks landscape-client starts
To
** Changed in: landscape-client (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827857
Title:
Stuck on applying package profile for servers
landscape-client workaround: https://github.com/CanonicalLtd/landscape-
client/pull/80
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827857
Title:
Stuck on applying package profile for servers
landscape-server still uses python-convoy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870402
Title:
RM: convoy obsolete/unused package
To manage notifications about this bug go to:
I've verified the proposed package by upgrading a client to the eoan-proposed
package and applying a new package profile though the Landscape web UI.
Profile applied as expected with the proposed version.
** Tags removed: verification-needed verification-needed-eoan
** Tags added:
** Description changed:
- There has been an API change in focal/eoan for python3-apt >= 1.9, and
- the package changer now raises exceptions:
+ [Impact]
+
+ * Regression when applying a package profile through landscape on
+ubuntu-19.10. Process will stack-trace.
+
+ * The issue is
** Also affects: landscape-client (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: landscape-client (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: landscape-client (Ubuntu Focal)
Milestone: eoan-updates => None
** Changed in:
** Changed in: landscape
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858692
Title:
ceph-common postinst does not check for ceph user existing
** Changed in: landscape
Milestone: 19.11 => 19.10.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858692
Title:
ceph-common postinst does not check for ceph user existing externally
To
** Changed in: landscape
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858692
Title:
ceph-common postinst does not check for ceph user existing
Public bug reported:
[Impact]
Reference:
https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases
This SRU is for the 19.12 release of landscape-client which includes:
* Modernized packaging.
* Added support for python-apt 1.9
* Converted init script to systemd service.
*
I've just verified this on xenial, with the package from xenial-proposed
16.03-0ubuntu2.16.04.7
I followed the above test case without any issue.
** Changed in: landscape-client (Ubuntu Xenial)
Status: Incomplete => Fix Committed
** Tags removed: verification-needed
** Tags added:
I just verified this fix with the xenial-proposed package version
16.03-0ubuntu2.16.04.7
I followed the test case without issues.
** Tags removed: verification-needed
** Tags added: verification-done
** Changed in: landscape-client (Ubuntu Xenial)
Status: Incomplete => Fix Committed
--
** Description changed:
[Impact]
I report this bug to add the necessary bit into lds-client for all
affected/supported releases.
[Test Case]
* One must use Landscape server on-prem (version >=19.01) or hosted which
already contain the necessary server side change.
* Install
** Description changed:
[Impact]
I report this bug to add the necessary bit into lds-client for all
affected/supported releases.
[Test Case]
* One must use Landscape server on-prem (version >=19.01) or hosted which
already contain the necessary server side change.
* Install
I verified the pacakges in xenial-proposed and the logs indicated
scattered start delays, as expected.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of
verified disco-proposed, also as expected:
multipass@di:~$ sudo landscape-config --log-level=debug -a devel --silent -t
testclient
[ ok ] Restarting landscape-client (via systemctl): landscape-client.service.
Please wait...
Traceback (most recent call last):
Failure:
Verified bionic-proposed with the above instructions and it works as
expected:
root@bi:/home/multipass# landscape-config --log-level=debug -a devel --silent
-t testclient
[ ok ] Restarting landscape-client (via systemctl): landscape-client.service.
root@bi:/home/multipass# grep vm-info
Verified bionic and disco proposed, by setting launching a couple of
instances and verifying the monitors are scattered in the logs.
** Tags removed: verification-needed-bionic verification-needed-disco
** Tags added: verification-done-bionic verification-done-disco
--
You received this bug
I tested the -proposed packages against disco and bionic by registering
landscape-clients and stopping/restarting them.
The services stopped successfully as expected.
** Tags removed: verification-needed-bionic verification-needed-disco
** Tags added: verification-done-bionic
I verified upgrading to the -proposed packages without data_path on bionic and
disco.
They installed and upgraded cleanly with the new version.
** Tags removed: verification-needed-bionic verification-needed-disco
** Tags added: verification-done-bionic verification-done-disco
--
You received
** Merge proposal linked:
https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/370075
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833137
Title:
** Description changed:
+ [Impact]
+
+ * Manually editing landscape client.conf to unset the data_path
+blocks upgrade postinst. That field was not required to be present
+before 14.04, and older configurations can fail to upgrade without
+purging the existing configuration.
+
+ *
I've been able to reproduce this bug consistently. It appears
python3-apt is at cause. If a non-utf8 locale is configured, apt will
returned descriptions in the preferred lang/encoding and python3 fails
to interpret them as utf8. Python2.7 did ascii conversion, returning
"lossy" unicode conversion
** Changed in: landscape-client (Ubuntu)
Status: Confirmed => In Progress
** Changed in: landscape-client (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: landscape-client
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728681
Title:
postinst script fails if data_path not set in client.conf
To
** Changed in: landscape-client
Assignee: (unassigned) => Simon Poirier (simpoir)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728681
Title:
postinst script fails if data_path not
** Changed in: landscape-client
Status: Triaged => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728681
Title:
postinst script fails if data_path not set in client.conf
To manage
I tested this on xenial, bionic and cosmic by launching 2 identical lxd
containers of each, one of which using the landscape-client/common from
-proposed packages. Clients were registered in against the same account and
left idle for a few hours before taking a reading:
ps o rss,args `pgrep
** Description changed:
+ [Impact]
+
+ * Memory usage of landscape processes abnormally grows, over time,
+even for processes which are generally idle and have no reason to
+grow.
+
+ * Most of that memory leak is due to uninitialized python-twisted
+logging facilities buffering
** No longer affects: landscape-client (Ubuntu Trusty)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685885
Title:
Extreme RAM and SWAP usage
To manage notifications about this bug go to:
** Changed in: landscape-client (Ubuntu Trusty)
Status: Incomplete => Fix Committed
** Changed in: landscape-client (Ubuntu Xenial)
Status: Incomplete => Fix Committed
** Changed in: landscape-client (Ubuntu Bionic)
Status: Incomplete => Fix Committed
** Changed in:
I tested landscape-client and landscape-common for both bionic-proposed and
cosmic-proposed.
Then I reset the locale config, enabled script execution, set some fancy
unicode tags and ran a script successfully.
The script ran successfully on both bionic and cosmic, as can be seen
here
I tested successfully landscape-client and landscape-common packages
from {trusty,xenial,bionic,cosmic}-proposed. As in the test case, masked
systemd-logind.
After triggering reboots from landscape on all of those. All machines both
force-rebooted as would be expected, and surfaced the error to
I tested xenial-proposed and trusty-proposed by setting a short apt
interval, like in the testing instructions, launching do-release-upgrade
sudo sed -i -e 's/info/debug/' -e '2iapt_update_interval=300'
/etc/landscape/client.conf
sudo service landscape-client restart
The expected log entries
I tested the fix against trusty, xenial, bionic and cosmic VM instances through
multipass.libvirt
I set the relevant bios flags:
env EDITOR="sed -i '2ihttp://libvirt.org/schemas/domain/qemu/1.0\;>'" multipass.virsh edit ccli
multipass stop ccli && multipass start ccli
checked dmidecode matches:
I tested this by deploying landscape-server from ppa:landscape/18.03,
connecting clients from {trusty,xenial,bionic,cosmic} against it, restoring a
database dump to trigger the issue.
The landscape-clients were then upgraded to *-proposed. As per the test case,
the resync loop stopped after.
** Description changed:
[Impact]
- * Script execution fails on computers with non-ascii tags
+ * Script execution fails on computers with non-ascii tags
- * This is a fairly simple bugfix which is easy to trigger
+ * This is a fairly simple bugfix which is easy to trigger
[Test
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic verification-needed-trusty verification-needed-xenial
** Tags added: verification-done-bionic verification-done-cosmic
verification-done-trusty verification-done-xenial
--
You received this bug
** Tags removed: verification-needed verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699179
Title:
PackageReporter kicks in during
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699179
Title:
PackageReporter kicks in during do-release-upgrade
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic verification-needed-trusty verification-needed-xenial
** Tags added: verification-done verification-done-bionic
verification-done-cosmic verification-done-trusty verification-done-xenial
** Tags removed:
** Tags removed: verification-needed verification-needed-bionic
verification-needed-trusty verification-needed-xenial
** Tags added: verification-done verification-done-bionic
verification-done-trusty verification-done-xenial
--
You received this bug notification because you are a member of
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1616116
Title:
Unrecoverable resyncs if DB is restored from backup
** Merge proposal linked:
https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/358162
** Merge proposal linked:
https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/358163
** Merge proposal linked:
** Description changed:
[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
** Summary changed:
- backport upstream landscape-client fixes
+ vm_type detection for nutanix cloud instances
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788219
Title:
vm_type detection for
** Description changed:
[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
** Patch removed: "cosmic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1788219/+attachment/5188637/+files/cosmic.debdiff
** Patch removed: "bionic.debdiff"
** Merge proposal unlinked:
https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/358162
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699179
Title:
** Merge proposal unlinked:
https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/358162
** Merge proposal unlinked:
https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/358163
** Merge proposal
** Changed in: landscape-client
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1616116
Title:
Unrecoverable resyncs if DB is restored from backup
To manage
** Description changed:
+ [Impact]
+
+ * In some cases generally involving backups/restore, client would get
+inconsistent package data and keep that data upon resync, thus getting
+stuck in a resync loop. This usually gets noticed through the stress
+it adds on the server and
** Description changed:
+ [Impact]
+
+ * This issue affects users of the release-upgrade feature of landscape.
+
+ * Landscape package monitor would previously race during an upgrade
+and possibly grab apt locks, thus making the upgrade fail.
+
+ * The fix adds checks during package
** Merge proposal linked:
https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/358162
** Merge proposal linked:
https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/358163
** Merge proposal linked:
** Description changed:
[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.
+ * The dmi id for
** Patch added: "trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1788219/+attachment/5188640/+files/trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1788219/+attachment/5188639/+files/xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1788219/+attachment/5188638/+files/bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- vm_type for nutanix cloud instances
+ backport upstream landscape-client fixes
** Description changed:
- Landscape client does not properly report vm_type for Nutanix cloud
- instances.
+ [Impact]
- DMI id for those instances are:
+ This bug is for inclusion of a
That workaround wouldn't work in Landscape for many configurations; we
can't assume pocket names as many use custom mirrors or repository
snapshots in which the pocket may not match.
It seems to me there is no simple way to resolve this automatically in
Landscape, but as that upgrade situation is
Public bug reported:
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
** Affects: landscape-client (Ubuntu)
Importance: Undecided
Status: New
--
You
** Description changed:
+ [Impact]
+
+ * An error message is included in when rendering landscape-sysinfo
+statistics through pam_motd if there are processes with a non-ascii
+command. This is due to the fact that environment is not passed
+by pam-motd.
+
+ * As
** Also affects: landscape-client (Ubuntu)
Importance: Undecided
Status: New
** Patch added: "cosmic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1780071/+attachment/5164306/+files/cosmic.debdiff
--
You received this bug notification because you are a
** Patch added: "bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1780071/+attachment/5164307/+files/bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: landscape-client
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685885
Title:
Extreme RAM and SWAP usage
To manage notifications about
** Patch added: "cosmic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1771443/+attachment/5144381/+files/cosmic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
1 - 100 of 145 matches
Mail list logo
