[Bug 2073973] Re: Add eBPF support to ubuntu:22.04 -kvm variant kernel
** Changed in: cloud-images 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/2073973 Title: Add eBPF support to ubuntu:22.04 -kvm variant kernel To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2073973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2084698] Re: Apparmor profile policy permstable32 component is missing in Jammy 6.8 kernel
** Description changed: A CPC snap preseeding test on recent Jammy image build with 6.8 kernel. Jammy 6.8 kernel has additional component under policy:permstable32 and this is missing in 6.8 apparmor directly. [ Impact ] Boot will be slowed by ~200ms until this is resolved in livecd-rootfs [ Test Plan ] - * Build a jammy cloud image with preseeded snaps with missing components under `permstable321 file + * Build a jammy cloud image with preseeded snaps with missing components under `permstable32` file * Boot an instance * Run `snap debug preseed` * Confirm there is nothing in seed-restart-system-key when running `snap debug preseeding` command [ Where problems could occur ] * Missing these components, images with 6.8 kernel will not be optimized for first boot deployments. [ Other Info ] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2084698 Title: Apparmor profile policy permstable32 component is missing in Jammy 6.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2084698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083685] Re: Utilize SNAPSHOT_SERVICE_TIMESTAMP When Configuring Repositories
I haven't dug this further, but suspect it could be something like proxy configs. germinate uses plain urlopen, so it would disregard any apt proxy config on the build environment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083685 Title: Utilize SNAPSHOT_SERVICE_TIMESTAMP When Configuring Repositories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2083685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077603] Re: debsum of /usr/sbin/start-stop-daemon failed
Certainly. I re-built an image and verified the fix, still against live- build_3.0~a57-1ubuntu49.1 using a noble ubuntu-cpc qcow2 image build. sudo debsums --root /mnt -c No output, as expected of the fix. ** Tags removed: verification-needed-noble ** Tags added: verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077603 Title: debsum of /usr/sbin/start-stop-daemon failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/2077603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077603] Re: debsum of /usr/sbin/start-stop-daemon failed
Verified the noble-proposed package (live-build all 3.0~a57-1ubuntu49.1) through a couple of noble builds through ubuntu-bartender. * Built a few of the ubuntu-cpc download images and bootable buildd. * Logs looked clean * The files hashes validate with: dpkg -V (there are a few hash mismatch on buildd images, but those are not related to this issue) ** Tags removed: verification-needed-noble ** Tags added: verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077603 Title: debsum of /usr/sbin/start-stop-daemon failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/2077603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081065] Re: Md5sum verification failed for the file /usr/sbin/start-stop-daemon in the dpkg package of the noble-20240827.1 image
*** This bug is a duplicate of bug 2077603 *** https://bugs.launchpad.net/bugs/2077603 ** This bug has been marked a duplicate of bug 2077603 debsum of /usr/sbin/start-stop-daemon failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081065 Title: Md5sum verification failed for the file /usr/sbin/start-stop-daemon in the dpkg package of the noble-20240827.1 image To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2081065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081065] Re: Md5sum verification failed for the file /usr/sbin/start-stop-daemon in the dpkg package of the noble-20240827.1 image
** Also affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081065 Title: Md5sum verification failed for the file /usr/sbin/start-stop-daemon in the dpkg package of the noble-20240827.1 image To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2081065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072929] Re: Ubuntu cloud image partition numbering
** Changed in: cloud-images/oracular Status: Confirmed => In Progress ** Changed in: cloud-images Status: Confirmed => In Progress ** Changed in: livecd-rootfs (Ubuntu) Assignee: (unassigned) => Simon Poirier (simpoir) ** Changed in: livecd-rootfs (Ubuntu) Status: New => 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/2072929 Title: Ubuntu cloud image partition numbering To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2072929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064175] Re: buildd/h/02-disk-image-uefi.binary fails on jammy
Verified proposed livecd-rootfs (2.765.44) using launchpad live-builds. Builds successfully and generated virtual images still boot in qemu. [arm64] https://launchpad.net/~cloudware/+livefs/ubuntu/jammy/cpc-development/+build/642828 [amd64] https://launchpad.net/~cloudware/+livefs/ubuntu/jammy/cpc-development/+build/642892 [armhf] https://launchpad.net/~cloudware/+livefs/ubuntu/jammy/cpc-development/+build/642893 ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064175 Title: buildd/h/02-disk-image-uefi.binary fails on jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2064175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2007419] Re: buildd daily kinetic, lunar, and mantic image missing systemd-resolved
Verified package in mantic-proposed (23.10.59) using https://github.com/ubuntu-bartenders/ubuntu-old-fashioned to build a bootable buildd image. Booted resulting artifact in qemu and systemd-resolved is present and active. ** Tags removed: verification-needed verification-needed-mantic ** Tags added: verification-done verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2007419 Title: buildd daily kinetic, lunar, and mantic image missing systemd-resolved To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2007419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064175] Re: buildd/h/02-disk-image-uefi.binary fails on jammy
** Also affects: livecd-rootfs (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064175 Title: buildd/h/02-disk-image-uefi.binary fails on jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2064175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064175] Re: buildd/h/02-disk-image-uefi.binary fails on jammy
** Description changed: [ 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. + * 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 -udev as a transitive dependency, thus not hitting the same issue. + * uefi buildd images don't build on jammy. Later suites have a different code +path (in grub-core/osdep/linux/hostdisk) which doesn't call udevadm anymore. - * udev was getting installed in later hooks. Adding it earlier isn't -altering the resulting artifact. + * udev was getting installed in later hooks. Adding it earlier isn't + altering the resulting artifact. [ test plan ] - * live-build with --series=jammy --project ubuntu-base --subproject + * live-build with --series=jammy --project ubuntu-base --subproject buildd --image-format ext4 --image-target all - * uefi image should build and be bootable from qemu + * uefi image should build and be bootable from qemu [ where problems could occur ] - * affected hook is specific to buildd + * affected hook is specific to buildd - * considering udev is now installed in an earlier buildd hook, it could -technically interfere with later build steps. Recent additions of flock -address some of the udev races but this could surface more. + * considering udev is now installed in an earlier buildd hook, it could + technically interfere with later build steps. Recent additions of flock + address some of the udev races but this could surface more. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064175 Title: buildd/h/02-disk-image-uefi.binary fails on jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2064175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064175] [NEW] buildd/h/02-disk-image-uefi.binary fails on jammy
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 udev as a transitive dependency, thus not hitting the same issue. * udev was getting installed in later hooks. Adding it earlier isn't altering the resulting artifact. [ test plan ] * live-build with --series=jammy --project ubuntu-base --subproject buildd --image-format ext4 --image-target all * uefi image should build and be bootable from qemu [ where problems could occur ] * affected hook is specific to buildd * considering udev is now installed in an earlier buildd hook, it could technically interfere with later build steps. Recent additions of flock address some of the udev races but this could surface more. ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064175 Title: buildd/h/02-disk-image-uefi.binary fails on jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2064175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062024] Re: armhf doesn't build disk-image-uefi
** 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 disk-image-uefi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2062024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062024] [NEW] armhf doesn't build disk-image-uefi
Public bug reported: [ Impact ] * disk-image-uefi build for armhf have been disabled in code, which prevents building qcow images [ Test Plan ] * disk-image-uefi builds for armhf architectures. * launchpad live-build with project=ubuntu-cpc image-target=disk- image,qcow2,squashfs,tarball,vmdk [ Where problems could occur ] * image-targets accidentally depending on disk-image-uefi might start to get exercised again on armhf builds. The obvious ones (qcow2,vmdk,disk-images,squashfs) should be verified. * Out-of-tree image-targets/series depending on the ubuntu-cpc disk-image 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://bugs.launchpad.net/bugs/2062024 Title: armhf doesn't build disk-image-uefi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2062024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903776] Re: Changed ubuntu-keyring paths breaks upgrade to focal.
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 the upgrade successful and the logs confirming the success: # tail -f /var/log/landscape/release-upgrader.log 2022-03-29 19:58:48,927 DEBUG[MainThread] Started firing run. 2022-03-29 19:58:48,927 DEBUG[MainThread] Finished firing run. 2022-03-29 19:58:49,793 INFO [MainThread] Successfully fetched upgrade-tool files 2022-03-29 19:58:49,817 INFO [MainThread] Successfully verified upgrade-tool tarball 2022-03-29 20:09:34,616 INFO [MainThread] Queuing message with release upgrade results to exchange urgently. 2022-03-29 20:09:35,028 DEBUG[MainThread] Started firing stop. 2022-03-29 20:09:35,028 DEBUG[MainThread] Finished firing stop. ** Tags removed: verification-needed verification-needed-focal verification-needed-impish ** Tags added: verification-done verification-done-focal verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903776 Title: Changed ubuntu-keyring paths breaks upgrade to focal. To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1903776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903776] Re: Changed ubuntu-keyring paths breaks upgrade to focal.
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 into meta_release
(code_name, name, version, date, supported, upgrade_tool_tarball_url,
upgrade_tool_signature_url, lts) VALUES ('jammy', 'Jammy Jellyfish', '22.04
LTS', now(), 't',
'http://archive.ubuntu.com/ubuntu/dists/jammy/main/dist-upgrader-all/current/jammy.tar.gz',
'http://archive.ubuntu.com/ubuntu/dists/jammy/main/dist-upgrader-all/current/jammy.tar.gz.gpg',
't')"
# sudo -u landscape psql landscape-standalone-main -c "update meta_release set
upgrade_id=(select id from meta_release where code_name='jammy') where
code_name in ('focal', 'impish')"
Launching the release upgrade activity from the web UI, the client
machine was able to download and validate the upgrade tool and upgraded
to jammy succesfully.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903776
Title:
Changed ubuntu-keyring paths breaks upgrade to focal.
To manage notifications about this bug go to:
https://bugs.launchpad.net/landscape-client/+bug/1903776/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903776] Re: Changed ubuntu-keyring paths breaks upgrade to focal.
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 removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903776 Title: Changed ubuntu-keyring paths breaks upgrade to focal. To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1903776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962539] Re: python3-twisted breaks landscape-sysinfo
** 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 notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1962539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962539] Re: python3-twisted breaks landscape-sysinfo
** 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) => 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/1962539 Title: python3-twisted breaks landscape-sysinfo To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1962539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962539] Re: python3-twisted breaks landscape-sysinfo
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1962539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962539] Re: python3-twisted breaks landscape-sysinfo
** 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. https://bugs.launchpad.net/bugs/1962539 Title: python3-twisted breaks landscape-sysinfo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1962539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903776] Re: Changed ubuntu-keyring paths breaks upgrade to focal.
** 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 (simpoir) => (unassigned)
** Changed in: landscape-client (Ubuntu Hirsute)
Assignee: Simon Poirier (simpoir) => (unassigned)
** Changed in: landscape-client (Ubuntu Jammy)
Assignee: Simon Poirier (simpoir) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903776
Title:
Changed ubuntu-keyring paths breaks upgrade to focal.
To manage notifications about this bug go to:
https://bugs.launchpad.net/landscape-client/+bug/1903776/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903776] Re: Changed ubuntu-keyring paths breaks upgrade to focal.
** 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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903776 Title: Changed ubuntu-keyring paths breaks upgrade to focal. To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1903776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870087] Re: Old broker lockfile blocks landscape-client starts
** 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. https://bugs.launchpad.net/bugs/1870087 Title: Old broker lockfile blocks landscape-client starts To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1870087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870087] Re: Old broker lockfile blocks landscape-client starts
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 directly or indirectly (through systemd). ** Tags removed: verification-needed verification-needed-focal verification-needed-groovy ** Tags added: verification-done verification-done-focal verification-done-groovy -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1870087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878957] Re: Upgrade profile with "security" enabled marks kernel packages as manually installed
** 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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878957 Title: Upgrade profile with "security" enabled marks kernel packages as manually installed To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1878957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870087] Re: Old broker lockfile blocks landscape-client starts
** 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 clients did not await +on their shutdown routine, thus were likely to leak their lock file. * The proposed fix tries to verify existing locks actually belong to landscape-client, instead of just verifying they exist. + + * The follow-up patch ensured some of the process actually complete + their shutdown. [Test Case] * systemctl stop landscape-client - * There should not be any remaining file in + * There should not be any remaining file in /var/lib/landscape/client/sockets/ * ln -sf 1 /var/lib/landscape/client/sockets/broker.sock.lock * systemctl start landscape-client [Regression Potential] * The existing twisted logic is still kept, so assuming checking process names fail, lock conflicts should still be detected normally. * The locks which twisted creates are unlikely to actually see conflicts in the wild as those processes are managed by systemd. False positives in the detection check should have minimal impact. [Original description] I have a machine which was failing to connect to the landscape service. In syslog I found this traceback: Apr 1 03:27:53 maas-1 landscape-client[1538354]: Traceback (most recent call last): Apr 1 03:27:53 maas-1 landscape-client[1538354]: File "/usr/lib/python3/dist-packages/twisted/python/lockfile.py", line 160, in lock Apr 1 03:27:53 maas-1 landscape-client[1538354]: symlink(str(os.getpid()), self.name) Apr 1 03:27:53 maas-1 landscape-client[1538354]: FileExistsError: [Errno 17] File exists: '1538397' -> b'/var/lib/landscape/client/sockets/broker.sock.lock' Apr 1 03:27:53 maas-1 landscape-client[1538354]: During handling of the above exception, another exception occurred: Apr 1 03:27:53 maas-1 landscape-client[1538354]: Traceback (most recent call last): Apr 1 03:27:53 maas-1 landscape-client[1538354]: File "/usr/bin/landscape-broker", line 8, in Apr 1 03:27:53 maas-1 landscape-client[1538354]: run(sys.argv) Apr 1 03:27:53 maas-1 landscape-client[1538354]: File "/usr/lib/python3/dist-packages/landscape/client/broker/service.py", line 93, in run Apr 1 03:27:53 maas-1 landscape-client[1538354]: run_landscape_service(BrokerConfiguration, BrokerService, args) Apr 1 03:27:53 maas-1 landscape-client[1538354]: File "/usr/lib/python3/dist-packages/landscape/client/service.py", line 115, in run_landscape_service Apr 1 03:27:53 maas-1 landscape-client[1538354]: startApplication(application, False) Apr 1 03:27:53 maas-1 landscape-client[1538354]: File "/usr/lib/python3/dist-packages/twisted/application/app.py", line 690, in startApplication Apr 1 03:27:53 maas-1 landscape-client[1538354]: service.IService(application).startService() Apr 1 03:27:53 maas-1 landscape-client[1538354]: File "/usr/lib/python3/dist-packages/twisted/application/service.py", line 288, in startService Apr 1 03:27:53 maas-1 landscape-client[1538354]: service.startService() Apr 1 03:27:53 maas-1 landscape-client[1538354]: File "/usr/lib/python3/dist-packages/landscape/client/broker/service.py", line 79, in startService Apr 1 03:27:53 maas-1 landscape-client[1538354]: self.publisher.start() Apr 1 03:27:53 maas-1 landscape-client[1538354]: File "/usr/lib/python3/dist-packages/landscape/client/amp.py", line 45, in start Apr 1 03:27:53 maas-1 landscape-client[1538354]: self._port = self._reactor.listen_unix(socket_path, factory) Apr 1 03:27:53 maas-1 landscape-client[1538354]: File "/usr/lib/python3/dist-packages/landscape/lib/reactor.py", line 228, in listen_unix Apr 1 03:27:53 maas-1 landscape-client[1538354]: return self._reactor.listenUNIX(socket, factory, wantPID=True) Apr 1 03:27:53 maas-1 landscape-client[1538354]: File "/usr/lib/python3/dist-packages/twisted/internet/posixbase.py", line 397, in listenUNIX Apr 1 03:27:53 maas-1 landscape-client[1538354]: p.startListening() Apr 1 03:27:53 maas-1 landscape-client[1538354]: File "/usr/lib/python3/dist-packages/twisted/internet/unix.py", line 372, in startListening Apr 1 03:27:53 maas-1 landscape-client[1538354]: if not self.lockFile.lock(): Apr 1 03:27:53 maas-1 landscape-client[1538354]: File "/usr/lib/python3/dist-packages/twisted/python/lockfile.py", line 185, in lock Apr 1 03:27:53 maas-1 landscape-client[1538354]: kill(int(pid), 0) Apr 1 03:27:53 maas-1 landscape-client[1538354]: PermissionError: [Errno 1] Operation not permitted In the sockets directory I saw: $ sudo ls /var/lib/landscape/client/sockets/ -la total 8 drwxr-x--- 2 landscape root 4096 Apr 1 03:27
[Bug 1870087] Re: Old broker lockfile blocks landscape-client starts
** 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 likely to occur -on release upgrade. + * The exact conditions for the issue, are particularly more likely to occur + on release upgrade. - * The proposed fix tries to verify existing locks actually belong -to landscape-client, instead of just verifying they exist. + * The proposed fix tries to verify existing locks actually belong + to landscape-client, instead of just verifying they exist. [Test Case] - * systemctl stop landscape-client + * systemctl stop landscape-client - * ln -sf 1 /var/lib/landscape/client/sockets/broker.sock.lock + * There should not be any remaining file in + /var/lib/landscape/client/sockets/ - * systemctl start landscape-client + * ln -sf 1 /var/lib/landscape/client/sockets/broker.sock.lock + + * systemctl start landscape-client [Regression Potential] - * The existing twisted logic is still kept, so assuming checking process -names fail, lock conflicts should still be detected normally. + * The existing twisted logic is still kept, so assuming checking process + names fail, lock conflicts should still be detected normally. - * The locks which twisted creates are unlikely to actually see conflicts in -the wild as those processes are managed by systemd. False positives in -the detection check should have minimal impact. + * The locks which twisted creates are unlikely to actually see conflicts in + the wild as those processes are managed by systemd. False positives in + the detection check should have minimal impact. [Original description] I have a machine which was failing to connect to the landscape service. In syslog I found this traceback: Apr 1 03:27:53 maas-1 landscape-client[1538354]: Traceback (most recent call last): Apr 1 03:27:53 maas-1 landscape-client[1538354]: File "/usr/lib/python3/dist-packages/twisted/python/lockfile.py", line 160, in lock Apr 1 03:27:53 maas-1 landscape-client[1538354]: symlink(str(os.getpid()), self.name) Apr 1 03:27:53 maas-1 landscape-client[1538354]: FileExistsError: [Errno 17] File exists: '1538397' -> b'/var/lib/landscape/client/sockets/broker.sock.lock' Apr 1 03:27:53 maas-1 landscape-client[1538354]: During handling of the above exception, another exception occurred: Apr 1 03:27:53 maas-1 landscape-client[1538354]: Traceback (most recent call last): Apr 1 03:27:53 maas-1 landscape-client[1538354]: File "/usr/bin/landscape-broker", line 8, in Apr 1 03:27:53 maas-1 landscape-client[1538354]: run(sys.argv) Apr 1 03:27:53 maas-1 landscape-client[1538354]: File "/usr/lib/python3/dist-packages/landscape/client/broker/service.py", line 93, in run Apr 1 03:27:53 maas-1 landscape-client[1538354]: run_landscape_service(BrokerConfiguration, BrokerService, args) Apr 1 03:27:53 maas-1 landscape-client[1538354]: File "/usr/lib/python3/dist-packages/landscape/client/service.py", line 115, in run_landscape_service Apr 1 03:27:53 maas-1 landscape-client[1538354]: startApplication(application, False) Apr 1 03:27:53 maas-1 landscape-client[1538354]: File "/usr/lib/python3/dist-packages/twisted/application/app.py", line 690, in startApplication Apr 1 03:27:53 maas-1 landscape-client[1538354]: service.IService(application).startService() Apr 1 03:27:53 maas-1 landscape-client[1538354]: File "/usr/lib/python3/dist-packages/twisted/application/service.py", line 288, in startService Apr 1 03:27:53 maas-1 landscape-client[1538354]: service.startService() Apr 1 03:27:53 maas-1 landscape-client[1538354]: File "/usr/lib/python3/dist-packages/landscape/client/broker/service.py", line 79, in startService Apr 1 03:27:53 maas-1 landscape-client[1538354]: self.publisher.start() Apr 1 03:27:53 maas-1 landscape-client[1538354]: File "/usr/lib/python3/dist-packages/landscape/client/amp.py", line 45, in start Apr 1 03:27:53 maas-1 landscape-client[1538354]: self._port = self._reactor.listen_unix(socket_path, factory) Apr 1 03:27:53 maas-1 landscape-client[1538354]: File "/usr/lib/python3/dist-packages/landscape/lib/reactor.py", line 228, in listen_unix Apr 1 03:27:53 maas-1 landscape-client[1538354]: return self._reactor.listenUNIX(socket, factory, wantPID=True) Apr 1 03:27:53 maas-1 landscape-client[1538354]: File "/usr/lib/python3/dist-packages/twisted/internet/posixbase.py", line 397, in listenUNIX Apr 1 03:27:53 maas-1 landscape-client[1538354]: p.startListening() Apr 1 03:27:53 maas-1 landscape-client[1538354]: File "/usr/lib/python3/dist-packages/twisted/internet/unix.py", line 372, in startListening Apr 1 03:27:53 maas-1
[Bug 1616116] Re: Unrecoverable resyncs if DB is restored from backup
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1616116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903776] Re: Changed ubuntu-keyring paths breaks upgrade to focal.
** 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) => Simon Poirier (simpoir) ** Changed in: landscape-client (Ubuntu Bionic) Assignee: (unassigned) => Simon Poirier (simpoir) ** Changed in: landscape-client (Ubuntu Hirsute) Status: New => In Progress ** Changed in: landscape-client (Ubuntu Groovy) Status: New => In Progress ** Changed in: landscape-client (Ubuntu Focal) Status: New => In Progress ** Changed in: landscape-client (Ubuntu Bionic) Status: New => 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/1903776 Title: Changed ubuntu-keyring paths breaks upgrade to focal. To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1903776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903776] Re: Changed ubuntu-keyring paths breaks upgrade to focal.
** 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 +/etc/apt/trusted.gpg.d/*.gpg files in addition to /etc/apt/trusted.gpg +when verifying the upgrade-tool signature. + + [Test Case] + + * Install and register the landscape-client against a landscape-server +on a series supporting an upgrade. + + * Wait for it to sync up packages. + + * On the computer packages page, there is a link at the bottom to request a +release upgrade of that machine, if a supported version is available. + + * The upgrade fails and /var/log/landscape/release-upgrader.log will indicate +a failed gpg verification. + + [Where problems could occur] + + * One thing which has been considered in this fix is how someone could have +worked around the issue by re-creating the old key path. The fix covers +such a case by still reading the deprecated trusted.gpg file. + + * Although some care has been taken to only load valid gpg keys from apt +trusted keychain, there could be unforeseen scenarios where invalid data +gets read from the keychain. In such a case, the strict nature of gpg would +reject the signature verification, thus being no worse than without the fix. + + * The affected callsite is used for verifying the release-upgrader code prior +to running it. One bad thing which we could imagine with this code path is +falsely accepting an invalid file signature, which may create a security +issue. This would likely take shape of injecting a gpg key, without +having root access, in the search path. + + [Other Info] + + * There is no way to directly verify this issue on 20.10 Groovy and later +(without faking a release) due to the lack of upgrade path to a supported +LTS. The ubuntu-keyring package having the same file layout, the same +validation failure is however to be expected if left unpatched. + + [Original description] + Since bionic, ubuntu-keyring removed `/etc/apt/trusted.gpg` in favor of `/etc/apt/trusted.gpg.d/` This breaks signature verification for the upgrade-tool. Trying to release-upgrade through landscape yields a failure on signature check: 2020-11-10 15:47:51,019 WARNING [MainThread] Invalid signature for upgrade-tool tarball: /usr/bin/gpg failed (out='', err='gpg: keybox '/etc/apt/trusted.gpg' created gpg: Signature made Fri Oct 16 03:28:09 2020 UTC gpg:using RSA key 3B4FE6ACC0B21F32 gpg: Can't check signature: No public key -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903776 Title: Changed ubuntu-keyring paths breaks upgrade to focal. To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1903776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903776] Re: Changed ubuntu-keyring paths breaks upgrade to focal.
** 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 Bionic) Importance: Undecided Status: New ** Also affects: landscape-client (Ubuntu Hirsute) Importance: Undecided Status: Confirmed ** Also affects: landscape-client (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: landscape-client (Ubuntu Hirsute) Status: Confirmed => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903776 Title: Changed ubuntu-keyring paths breaks upgrade to focal. To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1903776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1583276] Re: glance restarted during image upload, image stuck in "saving" state
** 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" state To manage notifications about this bug go to: https://bugs.launchpad.net/glance-simplestreams-sync-charm/+bug/1583276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886491] Re: Applying package profile on Xenial doesn't work
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 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/1886491 Title: Applying package profile on Xenial doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1886491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886491] Re: Applying package profile on Xenial doesn't work
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. https://bugs.launchpad.net/bugs/1886491 Title: Applying package profile on Xenial doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1886491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870087] Re: Old broker lockfile blocks landscape-client starts
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 recycled PIDs should not prevent client starting if the client is in fact not running. This can be verified by checking processes matching PIDs are not landscape: ls -l /var/lib/landscape/client/sockets/*.sock.lock readlink -v /var/lib/landscape/client/sockets/*.sock.lock | xargs ps However, there is an issue of processes not cleaning their lock/sock at exit. This issue affects all currently supported releases (as far as 16.04) and should be addressed in an upcoming patch. -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1870087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870087] Re: Old broker lockfile blocks landscape-client starts
** 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 starts To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1870087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886491] Re: Applying package profile on Xenial doesn't work
** Description changed: - [Impact] - * Users trying to apply changes to package profiles through landscape - will get an error in the activity. This will result in incomplete apt - source list on those clients. + [Impact] + + * Users trying to apply a landscape package profile with a recent + version of python-apt on xenial will get a stuck activity and an + incomplete sources.list.d entry. + + * The change adds a [trusted=yes] option to temporary local sources + created by landscape. Global sources and apt options + [Test Case] + + * install landscape-client and register it. + + * create and associate a package profile. + + * the packages are installed and /var/log/landscape/package-changer.log + has no errors + + + [Regression Potential] + + * This is a backport of fixes already released since yakkety. The + change has been released for a long time. + + * Change is agnostic of whether the issue is present or not and should + work no matter the apt configuration. + + * The affected code path is limited to profiles, but is also used a lot in unit tests fixtures, thus making it reasonably exercised. + + + [Other Info] + + * This change was not previously required on xenial, as it was not required. Acquire::AllowInsecureRepositories was set to be backward compatible and was accepted by python-apt. Changes in python-apt now looks for APT::Get::AllowUnauthenticated. + + * We fix landcape-client instead of raising the python-apt regression + because the new behaviour is consistent with later releases, which we + already handle. Also, it decouples landscape from requiring specific + configuration. + + + [Original Description] * install landscape-server-quickstart and landscape-api * Create a package profile "minimum packages" and add basic packages (byobu, vim, ubuntu-cloud-keyring). Enable for all computers * create a xenial container or machine and install/configure landscape-client Note that the apply package profile gets stuck and doesn't progress. On the container that was created, running apt update shows: sudo apt update Get:1 file:/var/lib/landscape/client/package/binaries ./ InRelease Ign:1 file:/var/lib/landscape/client/package/binaries ./ InRelease Get:2 file:/var/lib/landscape/client/package/binaries ./ Release Err:2 file:/var/lib/landscape/client/package/binaries ./ Release File not found - /var/lib/landscape/client/package/binaries/./Release (2: No such file or directory) Get:3 http://mirror/ubuntu xenial InRelease [247 kB] Hit:4 http://mirror/ubuntu xenial-updates InRelease Hit:5 http://mirror/ubuntu xenial-backports InRelease Hit:6 http://mirror/ubuntu xenial-security InRelease Reading package lists... Done E: The repository 'file:/var/lib/landscape/client/package/binaries ./ Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. apt-cache policy landscape-client landscape-client: Installed: 16.03-0ubuntu2.16.04.7 Candidate: 16.03-0ubuntu2.16.04.7 Version table: *** 16.03-0ubuntu2.16.04.7 500 500 http://mirror/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 16.03-0ubuntu2 500 500 http://mirror/ubuntu xenial/main amd64 Packages This can be easily worked around by: * Remove the file /etc/apt/sources.list.d/_landscape-internal-facade.list * add-apt-repository ppa:landscape/19.01 * apt install landscape-client apt-cache policy landscape-client landscape-client: Installed: 18.03~1070~git.8e52e1d~ubuntu16.04.1 Candidate: 18.03~1070~git.8e52e1d~ubuntu16.04.1 Version table: *** 18.03~1070~git.8e52e1d~ubuntu16.04.1 500 500 http://ppa.launchpad.net/landscape/19.01/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 16.03-0ubuntu2.16.04.7 500 500 http://mirror.glacier.dev/ubuntu xenial-updates/main amd64 Packages 16.03-0ubuntu2 500 500 http://mirror.glacier.dev/ubuntu xenial/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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886491 Title: Applying package profile on Xenial doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1886491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886491] Re: Applying package profile on Xenial doesn't work
** 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: Applying package profile on Xenial doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1886491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886491] Re: Applying package profile on Xenial doesn't work
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 trying anything related to the global apt config. ** Also affects: landscape-client (Ubuntu) Importance: Undecided Status: New ** Also affects: landscape-client (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: landscape-client (Ubuntu Xenial) Status: New => Confirmed ** No longer affects: landscape-client -- 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: Applying package profile on Xenial doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1886491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870087] Re: Old broker lockfile blocks landscape-client starts
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: Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture +++--- ii landscape-client 19.12-0ubuntu4.1 amd64 ii landscape-common 19.12-0ubuntu4.1 amd64 ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1870087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870087] Re: Old broker lockfile blocks landscape-client starts
** 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: Old broker lockfile blocks landscape-client starts To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1870087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827857] Re: Stuck on applying package profile for servers running 18.04
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 package profile for servers running 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1827857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870087] Re: Old broker lockfile blocks landscape-client starts
** 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 actually belong +to landscape-client, instead of just verifying they exist. + + [Test Case] + + * systemctl stop landscape-client + + * ln -sf 1 /var/lib/landscape/client/sockets/broker.sock.lock + + * systemctl start landscape-client + + [Regression Potential] + + * The existing twisted logic is still kept, so assuming checking process +names fail, lock conflicts should still be detected normally. + + * The locks which twisted creates are unlikely to actually see conflicts in +the wild as those processes are managed by systemd. False positives in +the detection check should have minimal impact. + + [Original description] + I have a machine which was failing to connect to the landscape service. In syslog I found this traceback: Apr 1 03:27:53 maas-1 landscape-client[1538354]: Traceback (most recent call last): Apr 1 03:27:53 maas-1 landscape-client[1538354]: File "/usr/lib/python3/dist-packages/twisted/python/lockfile.py", line 160, in lock Apr 1 03:27:53 maas-1 landscape-client[1538354]: symlink(str(os.getpid()), self.name) Apr 1 03:27:53 maas-1 landscape-client[1538354]: FileExistsError: [Errno 17] File exists: '1538397' -> b'/var/lib/landscape/client/sockets/broker.sock.lock' Apr 1 03:27:53 maas-1 landscape-client[1538354]: During handling of the above exception, another exception occurred: Apr 1 03:27:53 maas-1 landscape-client[1538354]: Traceback (most recent call last): Apr 1 03:27:53 maas-1 landscape-client[1538354]: File "/usr/bin/landscape-broker", line 8, in Apr 1 03:27:53 maas-1 landscape-client[1538354]: run(sys.argv) Apr 1 03:27:53 maas-1 landscape-client[1538354]: File "/usr/lib/python3/dist-packages/landscape/client/broker/service.py", line 93, in run Apr 1 03:27:53 maas-1 landscape-client[1538354]: run_landscape_service(BrokerConfiguration, BrokerService, args) Apr 1 03:27:53 maas-1 landscape-client[1538354]: File "/usr/lib/python3/dist-packages/landscape/client/service.py", line 115, in run_landscape_service Apr 1 03:27:53 maas-1 landscape-client[1538354]: startApplication(application, False) Apr 1 03:27:53 maas-1 landscape-client[1538354]: File "/usr/lib/python3/dist-packages/twisted/application/app.py", line 690, in startApplication Apr 1 03:27:53 maas-1 landscape-client[1538354]: service.IService(application).startService() Apr 1 03:27:53 maas-1 landscape-client[1538354]: File "/usr/lib/python3/dist-packages/twisted/application/service.py", line 288, in startService Apr 1 03:27:53 maas-1 landscape-client[1538354]: service.startService() Apr 1 03:27:53 maas-1 landscape-client[1538354]: File "/usr/lib/python3/dist-packages/landscape/client/broker/service.py", line 79, in startService Apr 1 03:27:53 maas-1 landscape-client[1538354]: self.publisher.start() Apr 1 03:27:53 maas-1 landscape-client[1538354]: File "/usr/lib/python3/dist-packages/landscape/client/amp.py", line 45, in start Apr 1 03:27:53 maas-1 landscape-client[1538354]: self._port = self._reactor.listen_unix(socket_path, factory) Apr 1 03:27:53 maas-1 landscape-client[1538354]: File "/usr/lib/python3/dist-packages/landscape/lib/reactor.py", line 228, in listen_unix Apr 1 03:27:53 maas-1 landscape-client[1538354]: return self._reactor.listenUNIX(socket, factory, wantPID=True) Apr 1 03:27:53 maas-1 landscape-client[1538354]: File "/usr/lib/python3/dist-packages/twisted/internet/posixbase.py", line 397, in listenUNIX Apr 1 03:27:53 maas-1 landscape-client[1538354]: p.startListening() Apr 1 03:27:53 maas-1 landscape-client[1538354]: File "/usr/lib/python3/dist-packages/twisted/internet/unix.py", line 372, in startListening Apr 1 03:27:53 maas-1 landscape-client[1538354]: if not self.lockFile.lock(): Apr 1 03:27:53 maas-1 landscape-client[1538354]: File "/usr/lib/python3/dist-packages/twisted/python/lockfile.py", line 185, in lock Apr 1 03:27:53 maas-1 landscape-client[1538354]: kill(int(pid), 0) Apr 1 03:27:53 maas-1 landscape-client[1538354]: PermissionError: [Errno 1] Operation not permitted In the sockets directory I saw: $ sudo ls /var/lib/landscape/client/sockets/ -la total 8 drwxr-x--- 2 landscape root 4096 Apr 1 03:27 . drwxr-xr-x 7 landscape root 4096 Apr 1 03:27 .. srw-rw-rw- 1 landscape landscape0 Mar 12 01:41 broker.sock lrwxrwxrwx 1 landscape landscape3 Mar 12 01:41 broker.sock.lock -> 905 Removing those two files allowed the landscape client to start as normal. Looks like we need some lockfile cleanup code on start. -- You received this bug notificat
[Bug 1870087] Re: Old broker lockfile blocks landscape-client starts
** Also affects: landscape-client (Ubuntu) Importance: Undecided Status: New ** Also affects: landscape-client (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: landscape-client (Ubuntu Focal) Status: New => In Progress ** Changed in: landscape-client (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 manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1870087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827857] Re: Stuck on applying package profile for servers running 18.04
** 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 running 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1827857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827857] Re: Stuck on applying package profile for servers running 18.04
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 running 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1827857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870402] Re: RM: convoy obsolete/unused package
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: https://bugs.launchpad.net/ubuntu/+source/convoy/+bug/1870402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850205] Re: AttributeError: module 'apt_pkg' has no attribute 'rewrite_section'
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: verification-done verification-done-eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850205 Title: AttributeError: module 'apt_pkg' has no attribute 'rewrite_section' To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1850205/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850205] Re: AttributeError: module 'apt_pkg' has no attribute 'rewrite_section'
** 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 caused by removal of some obsolete methods from +python-apt. + + * The backported patch replaces old rewrite_section() by +TagSection.write() + + [Test Case] + + * On ubuntu 19.10 (eoan) install landscape-client, run landscape-config, +and create a package profile on the account. + + * check /var/log/landscape/package-changer.log for exceptions. + + [Regression Potential] + + * The change has already been published for ubuntu 20.04 and is + verified. + + * Patched callsites are only used by package profiles, which would limit +the effect of regressions. + + * One possible regression could be in encoding errors, +as the new methods handle binary files directly instead of receiving +strings. This would imply an issue with python-apt. + + [original description] + There has been an API change in focal/eoan for python3-apt >= 1.9, and the package changer now raises exceptions: AttributeError: module 'apt_pkg' has no attribute 'rewrite_section' ** Also affects: landscape-client (Ubuntu) Importance: Undecided Status: New ** Changed in: landscape-client (Ubuntu) Milestone: None => eoan-updates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850205 Title: AttributeError: module 'apt_pkg' has no attribute 'rewrite_section' To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1850205/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850205] Re: AttributeError: module 'apt_pkg' has no attribute 'rewrite_section'
** 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: landscape-client (Ubuntu Focal) 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/1850205 Title: AttributeError: module 'apt_pkg' has no attribute 'rewrite_section' To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1850205/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858692] Re: ceph-common postinst does not check for ceph user existing externally
** 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 externally To manage notifications about this bug go to: https://bugs.launchpad.net/landscape/+bug/1858692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858692] Re: ceph-common postinst does not check for ceph user existing externally
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/landscape/+bug/1858692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858692] Re: ceph-common postinst does not check for ceph user existing externally
** 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 externally To manage notifications about this bug go to: https://bugs.launchpad.net/landscape/+bug/1858692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855756] [NEW] Update eoan with landscape-client 19.12
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. * Sysinfo: add support for multiple IPv6 addresses per interface. (LP: #829379) * Upstream version of previous SRU patches. [Test Case] * There is no specific test cases for this since it's an upstream release including all previously patched bugfixes, along with with a few regression fixes due to new versions present in eoan. * The current unit test suite and system test suite now pass on eoan/focal. (e.g. https://travis-ci.org/CanonicalLtd/landscape-client/builds/620310386) * The updated packaging also adds build-time testing, which should help raise regressions faster in the future. [Regression Potential] * Most of the changes, apart from the ones listed above have been patched through SRU and are already proven. * The init.d to systemd update is a potential regression point. In the event there were any issues with this change, the effect would be fairly apparent since landscape-client relies on it for startup. However, the new service configuration is much simpler than previously. * Another potential regression point is the update python-apt support. It changed package profiles enforcement. As the feature was completely broken, any regression would likely affect edge cases in package profiles which were not already covered by current test suites. ** Affects: landscape-client (Ubuntu) Importance: Undecided Status: New ** Changed in: landscape-client (Ubuntu) Milestone: None => eoan-updates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855756 Title: Update eoan with landscape-client 19.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1855756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728681] Re: postinst script fails if data_path not set in client.conf
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: verification-done -- 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 notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1728681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833137] Re: Landscape-client service fails to stop on disco+
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 -- 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: Landscape-client service fails to stop on disco+ To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1833137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848828] Re: report packages from security pocket
** 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 landscape-client. * Successfully register a client against Landscape server. * Security updates will only rely on USN notices and could possibly ignore other packages found in -security pocket even if they are there simply by the fact that there was no USN notice specific for them. (e.g. systemd has an USN, systemd get updated but its derived systemd binary packages aren't updated) [Regression Potential] - ## TBD by simpoir ## + * The patch flags potential security updates by matching the pocket name. The server then does additional package selection from that info. If the pocket matching were to break, security updates would continue as it was previously. + * False positive matching could be possible, assuming one builds a mirror which mimics security pockets and contains normal updates. In that case, landscape could mistakenly update as if they were security updates. + * Landscape may apply security updates without USN data, if the update comes from a security pocket. Since this matches the behaviour of unattended-upgrades and MOTD info, this may be closer to what users expect, even though this is a change of behaviour. [Other Info] * Upstream details: https://github.com/CanonicalLtd/landscape-client/commit/93a3b47965da199785e9b3d226cb61f721e54196 https://github.com/CanonicalLtd/landscape-client/pull/57 https://github.com/CanonicalLtd/landscape-client/pull/70 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848828 Title: report packages from security pocket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1848828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848828] Re: report packages from security pocket
** 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 landscape-client. * Successfully register a client against Landscape server. * Security updates will only rely on USN notices and could possibly ignore other packages found in -security pocket even if they are there simply by the fact that there was no USN notice specific for them. (e.g. systemd has an USN, systemd get updated but its derived systemd binary packages aren't updated) [Regression Potential] ## TBD by simpoir ## [Other Info] * Upstream details: https://github.com/CanonicalLtd/landscape-client/commit/93a3b47965da199785e9b3d226cb61f721e54196 https://github.com/CanonicalLtd/landscape-client/pull/57 + https://github.com/CanonicalLtd/landscape-client/pull/70 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848828 Title: report packages from security pocket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1848828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788518] Re: Intervals should be staggered
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788518 Title: Intervals should be staggered To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1788518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828217] Re: Machine not being detected as VM
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: landscape.lib.amp.MethodCallError: timeout multipass@di:~$ sudo grep vm-info /var/log/landscape/broker.log 'vm-info': b''}], 'vm-info': b'kvm'}], Also successfully verified xenial-proposed: multipass@xe:~$ sudo landscape-config --log-level=debug -a devel --silent -t testclient [ ok ] Restarting landscape-client (via systemctl): landscape-client.service. Please wait... Invalid account name or registration key. multipass@xe:~$ sudo grep vm-info /var/log/landscape/broker.log 'vm-info': ''}], 'vm-info': 'kvm'}], ** Tags removed: verification-needed verification-needed-disco verification-needed-xenial ** Tags added: verification-done verification-done-disco 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/1828217 Title: Machine not being detected as VM To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1828217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828217] Re: Machine not being detected as VM
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 /var/log/landscape/broker.log 'vm-info': b'kvm'}], ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828217 Title: Machine not being detected as VM To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1828217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788518] Re: Intervals should be staggered
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788518 Title: Intervals should be staggered To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1788518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833137] Re: Landscape-client service fails to stop on disco+
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 verification-done-disco -- 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: Landscape-client service fails to stop on disco+ To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1833137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728681] Re: postinst script fails if data_path not set in client.conf
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 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 notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1728681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833137] Re: Landscape-client service fails to stop on disco+
** 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: Landscape-client service fails to stop on disco+ To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1833137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728681] Re: postinst script fails if data_path not set in client.conf
** 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. + + * Although data_path is set by default, removing the line is accepted +by landscape and it will use a default path. The fix simply makes sure +the postinst script also has that default. + + [Test Case] + + * sed -i -e '/data_path/d' /etc/landscape/client.conf + + * apt install --reinstall landscape-client + + [Regression Potential] + + * The change is fairly trivial. Regression could be possible if the +default paths were changed and not reflected in the postinst. +In such a case the resync flag file wouldn't be created, +resulting in an out-of-sync list of users; this would be low impact. + + [Original Description] + Tested on 14.04.5, landscape-client (14.12-0ubuntu6.14.04). If the data_path directive is not present in /etc/landscape/client.conf, the postinst script will fail with the following error: Setting up landscape-client (14.12-0ubuntu6.14.04) ... install: missing file operand Try 'install --help' for more information. dpkg: error processing package landscape-client (--configure): - subprocess installed post-installation script returned error exit status 1 + subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: - landscape-client + landscape-client E: Sub-process /usr/bin/dpkg returned an error code (1) Relevant section of the postinst script: - # In response to bug 1508110 we need to trigger a complete update of - # user information. The flag file will be removed by the client when - # the update completes. - DATA_PATH="`grep ^data_path /etc/landscape/client.conf | cut -d= -f2 | tr -d '[[:space:]]'`" - install --owner=landscape --directory $DATA_PATH - USER_UPDATE_FLAG_FILE="$DATA_PATH/user-update-flag" - install --owner=landscape /dev/null $USER_UPDATE_FLAG_FILE + # In response to bug 1508110 we need to trigger a complete update of + # user information. The flag file will be removed by the client when + # the update completes. + DATA_PATH="`grep ^data_path /etc/landscape/client.conf | cut -d= -f2 | tr -d '[[:space:]]'`" + install --owner=landscape --directory $DATA_PATH + USER_UPDATE_FLAG_FILE="$DATA_PATH/user-update-flag" + install --owner=landscape /dev/null $USER_UPDATE_FLAG_FILE It would be helpful if the script checked for data_path's existence and emitted a more informative error message. How to reproduce: Install/configure/register landscape-client. Remove landscape-client Remove data_path from /etc/landscape/client.conf Reinstall landscape-client. -- 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 notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1728681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827857] Re: Stuck on applying package profile for servers running 18.04
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 but not crashing.
$ grep en_US /etc/locale.gen
en_US ISO-8859-1
# en_US.ISO-8859-15 ISO-8859-15
# en_US.UTF-8 UTF-8
$ LANG=en_US python3
Python 3.7.3 (default, Apr 3 2019, 05:39:12)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import apt
>>> apt.Cache().get("gosa").versions[0].description
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/apt/package.py", line 627, in description
dsc = records.long_desc if records is not None else None
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb2 in position 236:
invalid start byte
** Also affects: python-apt (Ubuntu)
Importance: Undecided
Status: New
--
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 running 18.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1827857/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827857] Re: Stuck on applying package profile for servers running 18.04
** 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. https://bugs.launchpad.net/bugs/1827857 Title: Stuck on applying package profile for servers running 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1827857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728681] Re: postinst script fails if data_path not set in client.conf
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1728681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728681] Re: postinst script fails if data_path not set in client.conf
** 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 set in client.conf To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1728681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728681] Re: postinst script fails if data_path not set in client.conf
** 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 notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1728681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685885] Re: Extreme RAM and SWAP usage
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 landscape-cli` Here are the results which, as per test case, show the most noticeable improvement on xenial. xenial-updates RSS COMMAND 254704 /usr/bin/python /usr/bin/landscape-client --daemon --pid-file /var/run/ xenial-proposed RSS COMMAND 46040 /usr/bin/python /usr/bin/landscape-client --daemon --pid-file /var/run/l bionic-updates RSS COMMAND 33744 /usr/bin/python3 /usr/bin/landscape-client --daemon --pid-file /var/run/landscape/ bionic-proposed RSS COMMAND 30960 /usr/bin/python3 /usr/bin/landscape-client --daemon --pid-file /var/run/landscape/ cosmic-updates RSS COMMAND 33660 /usr/bin/python3 /usr/bin/landscape-client --daemon --pid-file /var/run/landscape/la cosmic-proposed RSS COMMAND 30912 /usr/bin/python3 /usr/bin/landscape-client --daemon --pid-file /var/run/landscape/la ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-cosmic 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/1685885 Title: Extreme RAM and SWAP usage To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1685885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685885] Re: Extreme RAM and SWAP usage
** 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 logs and their context. This fix +Initializes logging with a null handler to have those unused log +entries discarded. + + * Upstream twisted has mitigated part of the issue in recent releases +by reducing the default buffer size. Because of that, the impact +of this bug is greater on xenial. + + [Test Case] + + * register a landscape client and log the memory growth over a day + + * the effect is most noticeable on /usr/bin/landscape-client and less on +the other processes + + * the memory difference on recent releases (bionic and up) is +expected to be smaller (~10mb on bionic instead of 200mb on xenial) + + [Regression Potential] + + * The fix initializes twisted logging, which is unused by landscape +so it is unlikely to have an impact. + + * The fix comes from recommendations on the upstream bug: +https://twistedmatrix.com/trac/ticket/8164 + + [Original description] + This has been noticed on several systems of mine, all 16.04. Landscape Client takes up, over time, an *extreme* amount of system resources. On a 1024MB RAM system, within 3 days to a month, Landscape Client and it's python scripts (possibly cached data?) are consuming massive quantities of memory - in the realm of 512MB RAM and over 400MB of the Swap on the system. This is repeatably shown in other systems of mine as well. Is there a memory leak or something in landscape-client that would contribute to this issue? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: landscape-client 16.03-0ubuntu2.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_vcdevice talpa_core talpa_linux talpa_syscallhook talpa_pedevice ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon Apr 24 14:42:37 2017 InstallationDate: Installed on 2017-04-02 (21 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: landscape-client UpgradeStatus: No upgrade log present (probably fresh install) - --- + --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-04-02 (21 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) Package: landscape-client 16.03-0ubuntu2.16.04.1 PackageArchitecture: amd64 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Tags: third-party-packages xenial Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True -- 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: https://bugs.launchpad.net/landscape-client/+bug/1685885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685885] Re: Extreme RAM and SWAP usage
** 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: https://bugs.launchpad.net/landscape-client/+bug/1685885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788219] Re: vm_type detection for nutanix cloud instances
** 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: landscape-client (Ubuntu Cosmic) Status: Incomplete => 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/1788219 Title: vm_type detection for nutanix cloud instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1788219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765518] Re: Can't execute scripts on a landscape-client that has non-ascii character in its tag
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 https://screenshots.firefox.com/oiRDpc3KehjKjG3g/landscape.canonical.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765518 Title: Can't execute scripts on a landscape-client that has non-ascii character in its tag To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1765518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
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 the web
interface
https://screenshots.firefox.com/bCPz5KxKkx4yG5hl/landscape.canonical.com
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670291
Title:
Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699179] Re: PackageReporter kicks in during do-release-upgrade
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 were then found: multipass@tcli:~$ sudo tail -f /var/log/landscape/package-reporter.log 2019-02-05 17:17:11,846 DEBUG[MainThread] Started firing run. 2019-02-05 17:17:11,847 DEBUG[MainThread] Finished firing run. 2019-02-05 17:17:12,811 DEBUG[MainThread] Checking if ubuntu-release-upgrader is running. 2019-02-05 17:17:12,816 INFO [MainThread] Found ubuntu-release-upgrader running (pid: 1814) 2019-02-05 17:17:12,816 DEBUG[MainThread] '/usr/lib/landscape/apt-update' didn't run, conditions not met -- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1699179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788219] Re: vm_type detection for nutanix cloud instances
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: Handle 0x0100, DMI type 1, 27 bytes System Information Manufacturer: Nutanix Product Name: Standard PC (i440FX + PIIX, 1996) [...] Handle 0x0300, DMI type 3, 21 bytes Chassis Information Manufacturer: Red Hat [...] installed the packages from -proposed and registered landscape showing vm_type as "kvm". https://screenshots.firefox.com/IoS0unLONKmTWW2m/landscape.canonical.com -- 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 nutanix cloud instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1788219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1616116] Re: Unrecoverable resyncs if DB is restored from backup
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.
tail -f /var/log/landscape/package-reporter.log
2019-02-05 19:01:07,139 WARNING [MainThread] Removing cached hash=>id database
/var/lib/landscape/client/package/hash-id/2b0e1068-20d4-11e9-8e28-00163e8887ff_bionic_amd64
2019-02-05 19:01:27,315 INFO [MainThread] Queuing message with changes in
known packages: 216 installed, 26775 available, 48 available upgrades, 0
locked, 0 autoremovable, 0 not installed, 0 not available, 0 not available
upgrades, 0 not locked, 0 not autoremovable.
2019-02-05 19:02:07,812 INFO [MainThread] Downloaded hash=>id database from
https://lscape.lxd/hash-id-databases/2b0e1068-20d4-11e9-8e28-00163e8887ff_bionic_amd64
and the server output:
https://screenshots.firefox.com/kU7atd0RI411o7r4/lscape.lxd
--
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 notifications about this bug go to:
https://bugs.launchpad.net/landscape-client/+bug/1616116/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765518] Re: Can't execute scripts on a landscape-client that has non-ascii character in its tag
** 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 Case] - * Tagging a client with accented characters and running a simple -"echo script" should be enough to validate the encoding correction. + * Unset locale (/etc/default/locale) + + * Tagging a client with accented characters and running a simple + "echo script" should be enough to validate the encoding correction. [Regression Potential] - * The tag encoding change for scripts is 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. + * The tag encoding change for scripts is 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. + * 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. [Original Description] Steps to reproduce: 1) Add tag to a landscape-client, ex assgn tag 'täg 2) Go to scripts in the GUI page and attempt to execute script on that client 3) Script will attempt to run on client and will fail, GUI will show below error: [Failure instance: Traceback: : Environment contains a non-string value /usr/lib/python2.7/dist-packages/landscape/manager/scriptexecution.py:176:_handle_execute_script /usr/lib/python2.7/dist-packages/landscape/manager/scriptexecution.py:292:run_script /usr/lib/python2.7/dist-packages/twisted/internet/defer.py:306:addCallback /usr/lib/python2.7/dist-packages/twisted/internet/defer.py:295:addCallbacks --- --- /usr/lib/python2.7/dist-packages/twisted/internet/defer.py:577:_runCallbacks /usr/lib/python2.7/dist-packages/landscape/manager/scriptexecution.py:290:prepare_script /usr/lib/python2.7/dist-packages/landscape/manager/scriptexecution.py:129:_run_script /usr/lib/python2.7/dist-packages/twisted/internet/posixbase.py:336:spawnProcess /usr/lib/python2.7/dist-packages/twisted/internet/base.py:923:_checkProcessArgs ] Above exception is generated by the client w/ LANDSCAPE_COMPUTER_TAGS value being None ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done-bionic 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/1765518 Title: Can't execute scripts on a landscape-client that has non-ascii character in its tag To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1765518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
** 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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699179] Re: PackageReporter kicks in during do-release-upgrade
** 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 do-release-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1699179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699179] Re: PackageReporter kicks in during do-release-upgrade
** 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 To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1699179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788219] Re: vm_type detection for nutanix cloud instances
** 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: verification-done -- 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 nutanix cloud instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1788219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1616116] Re: Unrecoverable resyncs if DB is restored from backup
** 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1616116 Title: Unrecoverable resyncs if DB is restored from backup To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1616116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1616116] Re: Unrecoverable resyncs if DB is restored from backup
** 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 To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1616116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788219] Re: vm_type detection for nutanix cloud instances
** 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: https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/358164 ** Merge proposal linked: https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/358165 -- 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 nutanix cloud instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1788219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788219] Re: vm_type detection for nutanix cloud instances
** 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 sysinfo fields like https://pastebin.ubuntu.com/p/C5mkc2B7rx/) + * 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 -- 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 nutanix cloud instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1788219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788219] Re: vm_type detection for nutanix cloud instances
** 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 nutanix cloud instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1788219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788219] Re: backport upstream landscape-client fixes
** 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 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) + [Test Case] - * 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. + * 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 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. + * 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. - * Those changes have been tested by some affected users + * Changes have been tested by some affected users ** 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 - * 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 + * 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 ** 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 + * 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 -- 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: backport upstream landscape-client fixes To manage notifications about this bug go to: https://bugs.
[Bug 1788219] Re: backport upstream landscape-client fixes
** Patch removed: "cosmic.debdiff" https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1788219/+attachment/5188637/+files/cosmic.debdiff ** Patch removed: "bionic.debdiff" https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1788219/+attachment/5188638/+files/bionic.debdiff ** Patch removed: "xenial.debdiff" https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1788219/+attachment/5188639/+files/xenial.debdiff ** Patch removed: "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. https://bugs.launchpad.net/bugs/1788219 Title: backport upstream landscape-client fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1788219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699179] Re: PackageReporter kicks in during do-release-upgrade
** 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: PackageReporter kicks in during do-release-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1699179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788219] Re: backport upstream landscape-client fixes
** 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 unlinked: https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/358164 -- 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: backport upstream landscape-client fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1788219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1616116] Re: Unrecoverable resyncs if DB is restored from backup
** 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 notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1616116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1616116] Re: Unrecoverable resyncs if DB is restored from backup
** 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 though logs which grow abnormally.
+
+ [Test Case]
+
+ * deploy landscape-server quickstart from ppa:landscape/18.03
+ * register client against server. wait for package info
+ * pg_dumpall
+ * add a repo and wait for new package to show on in landscape.
+ * restore the postgres backup.
+ * run ./scripts/hash_id_databases.sh from the server to complete
+ the restore.
+ * trigger a package install from the new repo to create some package
+ info to update
+ * client should resync once then will re-fetch hash on the next run.
+
+ [Regression Potential]
+
+ * Modified code is used only during resync operations and removes
+cached data when the client state is deemed inconsistent.
+
+ * In the unlikely event the code is called outside of the expected
+cases, the end result would be limited to the package-monitor
+having to re-download the hash-id databases, which shouldn't
+cause issues as that is the behaviour at client registration.
+
+ [Other Info]
+
+ * Other cases than server restores have been noticed to generate the
+bug but they are far less common.
+
+ [Original description]
+
Landscape with live clients cannot handle a DB restore to a point in the
past.
The scenario is Landscape running as usual, with live clients, restoring
to a DB backup taken in the past. After the service ir brought up again
with this data, clients will start resyncing and becoming wedged with
all sorts of tracebacks on the message server.
I left such a scenario running overnight, hoping that eventually the
resyncs would settle down and everything recover, but that didn't
happen. The resyncs continued, in the packages scope.
An interesting one in particular was this:
Aug 22 21:46:26 message-server-2 ERR Error handling message
'operation-result' for computer 104: {'status': 6, 'timestamp': 1471901963,
'result-text': u'Mon Aug 22 21:39:23 UTC 2016\n', 'api': '3.3', 'operation-id':
533, 'type': 'operation-result'}#012Traceback (most recent call last):#012
File "/opt/canonical/landscape/canonical/landscape/message/apis.py", line 358,
in _process_messages#012self.handle(message["type"], message)#012 File
"/opt/canonical/landscape/canonical/message/api.py", line 66, in handle#012
return handler(type, body)#012 File
"/opt/canonical/landscape/canonical/message/handler.py", line 30, in
__call__#012return function(self.message_api, type, body)#012 File
"/opt/canonical/landscape/canonical/lib/arguments.py", line 79, in
replacement#012return original(*new_args, **new_kwargs)#012 File
"/opt/canonical/landscape/canonical/landscape/message/handlers/activity.py",
line 32, in handle_activity_result#012activity.succeed(code=result_code,
text=result_text)#012AttributeError: 'NoneType' object has no attribute
'succeed'
That was about an activity that had been delivered already, but did not
exist in the restored DB.
** Information type changed from Proprietary to Public
** Project changed: landscape => landscape-client
** Also affects: landscape-client (Ubuntu)
Importance: Undecided
Status: New
--
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 notifications about this bug go to:
https://bugs.launchpad.net/landscape-client/+bug/1616116/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699179] Re: PackageReporter kicks in during do-release-upgrade
** 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 operations to make sure a +release upgrade is not in progresss. + + [Test Case] + + * in /etc/landscape/client.conf , set "apt_update_interval=1800" and +"log_level=debug" and restart the client. + + * Launch a release upgrade from landscape-server. Look for messages +in the package-monitor logs stating "conditions not met" + + [Regression Potential] + + * Unlikely, as this has already been released to newer ubuntu releases +and is fairly well tested. + + * Any issue with related changes would likely only affect the client +getting new package info, but won't affect other functionality. + + [Original description] + Affected release: Ubuntu 14.04.5 Version of package: 14.12-0ubuntu5.14.04 Steps to reproduce: 1. Run do-release-upgrade to upgrade to 16.04.2. 2. Trigger the package-reporter to kick in while do-release-upgrade is working but not having the package database locked. 3. Package database is locked by package-reporter, do-release-upgrade fails to access it and exits. Expected result: Landscape detects that there's an release upgrade in progress and will wait for it to finish. Actual result: PackageReporter locks the apt database, do-release-upgrade cannot access it, exits with an error and may leave the system in an unusable state. * Link to Dariusz's PR on GitHub: https://github.com/CanonicalLtd/landscape-client/pull/14 -- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1699179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788219] Re: backport upstream landscape-client fixes
** 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: https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/358164 -- 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: backport upstream landscape-client fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1788219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
