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 (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
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
** 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
** 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 STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1870087
Title:
Old broker lockfile blocks landscape-client starts
** 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]
+
+ * 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 STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1685885
Title:
Extreme RAM and SWAP usage
Status in Landscape Client:
Fix Committed
** Patch added: "trusty.debdiff"
https://bugs.launchpad.net/landscape-client/+bug/1742531/+attachment/5037516/+files/trusty.debdiff
--
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/1742531
** Patch added: "xenial.debdiff"
https://bugs.launchpad.net/landscape-client/+bug/1742531/+attachment/5037513/+files/xenial.debdiff
--
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/1742531
** Patch added: "artful.debdiff"
https://bugs.launchpad.net/landscape-client/+bug/1742531/+attachment/5037514/+files/artful.debdiff
--
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/1742531
** Description changed:
[Impact]
The new Amazon AWS C5 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 C5 instance type is a new type that uses a KVM-family hypervisor
instead of Xen (displaying
I should point out DigitalOcean instances started to inhibit the same
behaviour and will also need to be identified in a similar fashion.
--
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/1742531
** Description changed:
[Impact]
Reference:
https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases
This SRU contains minor updates for landscape-client as follow :
- Fix regression in configuration hook under install-cd chroot (LP: #1699789)
- Report
** Patch added: "xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1721383/+attachment/4963187/+files/xenial.debdiff
--
You received this bug notification because you are a member of STS
Sponsors Team, which is subscribed to the bug report.
** Patch added: "artful.debdiff"
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1721383/+attachment/4963188/+files/artful.debdiff
--
You received this bug notification because you are a member of STS
Sponsors Team, which is subscribed to the bug report.
19 matches
Mail list logo
