[Group.of.nepali.translators] [Bug 1580385] Re: /usr/bin/nmap:11:hascaptures:hascaptures:hascaptures:hascaptures:hascaptures
** Also affects: lua-lpeg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1580385 Title: /usr/bin/nmap:11:hascaptures:hascaptures:hascaptures:hascaptures:hascaptures Status in lua-lpeg package in Ubuntu: New Status in nmap package in Ubuntu: Confirmed Status in lua-lpeg source package in Xenial: New Status in nmap source package in Xenial: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nmap. This problem was most recently seen with version 7.01-2ubuntu2, the problem page at https://errors.ubuntu.com/problem/5e852236a443bab0279d47c8a9b7e55802bfb46f contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lua-lpeg/+bug/1580385/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1804594] Re: fanotify09 test case 1 in LTP failed with first group got more than 2 events
Testcase fix applied to autotest-client-tests repo: https://kernel.ubuntu.com/git/ubuntu/autotest-client- tests.git/commit/?id=4d83ea486a463a89e726715c55e037b479205f0d ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1804594 Title: fanotify09 test case 1 in LTP failed with first group got more than 2 events Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Bug description: There is a new test cases added into fanotify09: 457e13c (fanotify09: check merging of events on child subdir) tag=fanotify09 stime=1542775332 cmdline="fanotify09" contacts="" analysis=exit <<>> tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s fanotify09.c:161: INFO: Test #0: Events on children with both inode and mount marks fanotify09.c:150: PASS: group 0 got event: mask 2 pid=19769 fd=23 path=/tmp/ltp-2Jj8lWaBTL/UT3GCK/mntpoint/tfile_19769 fanotify09.c:234: PASS: group 1 got no event fanotify09.c:234: PASS: group 2 got no event fanotify09.c:161: INFO: Test #1: Events on children and subdirs with both inode and mount marks fanotify09.c:150: PASS: group 0 got event: mask 2 pid=19769 fd=23 path=/tmp/ltp-2Jj8lWaBTL/UT3GCK/mntpoint/tfile_19769 fanotify09.c:150: PASS: group 0 got event: mask 10 pid=19769 fd=24 path=/tmp/ltp-2Jj8lWaBTL/UT3GCK/mntpoint/testdir fanotify09.c:202: FAIL: first group got more than 2 events (72 > 48) fanotify09.c:234: PASS: group 1 got no event fanotify09.c:234: PASS: group 2 got no event Summary: passed 7 failed 1 skipped 0 warnings 0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-42-generic 4.15.0-42.45 ProcVersionSignature: User Name 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 22 06:27 seq crw-rw 1 root audio 116, 33 Nov 22 06:27 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Nov 22 06:45:22 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R320 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=7e417b15-9c42-401c-b706-06eb693e6d19 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.4 dmi.board.name: 0DY523 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd05/11/2012:svnDellInc.:pnPowerEdgeR320:pvr:rvnDellInc.:rn0DY523:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R320 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1804594/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1846126] Re: xenial/linux-gcp: 4.15.0-1047.50 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1846131 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Testing - phase-changed: Friday, 04. October 2019 18:46 UTC + phase: Signoff + phase-changed: Wednesday, 09. October 2019 14:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-gcp/gcp-kernel: bug 1846124 xenial/linux-gcp/gke-kernel: bug 1846125 variant: debs -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1846126 Title: xenial/linux-gcp: 4.15.0-1047.50 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1846131 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Signoff phase-changed: Wednesday, 09. October 2019 14:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-gcp/gcp-kernel: bug 1846124 xenial/linux-gcp/gke-kernel: bug 1846125 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846126/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1847512] [NEW] xenial: leftover scope units for Kubernetes transient mounts
Public bug reported: [Impact] When running Kubernetes on Xenial there's a leftover scope unit for the transient mounts used by a pod (eg, secret volume mount) together with its associate cgroup dirs, after the pod completes, almost every time such pod is created: $ systemctl list-units --type=scope | grep 'Kubernetes transient mount for' run-r560fcf858630417780c258c55fa21c8b.scope loaded active running Kubernetes transient mount for /var/snap/microk8s/common/var/lib/kubelet/pods/(...)/volumes/kubernetes.io~secret/(...) /sys/fs/cgroup/devices/system.slice/run-r560fcf858630417780c258c55fa21c8b.scope /sys/fs/cgroup/pids/system.slice/run-r560fcf858630417780c258c55fa21c8b.scope /sys/fs/cgroup/blkio/system.slice/run-r560fcf858630417780c258c55fa21c8b.scope /sys/fs/cgroup/memory/system.slice/run-r560fcf858630417780c258c55fa21c8b.scope /sys/fs/cgroup/cpu,cpuacct/system.slice/run-r560fcf858630417780c258c55fa21c8b.scope /sys/fs/cgroup/systemd/system.slice/run-r560fcf858630417780c258c55fa21c8b.scope This problem becomes noticeable with Kubernetes CronJobs as time goes by, as it repeatedly recreates pods to run the cronjob task. Over time, the leftover units (and associated cgroup directories) pile up to a significant amount, and start to cause problems for other components, with effects on /sys/fs/cgroup/ scanning: - Kubelet CPU/Memory Usage linearly increases using CronJob [1] and systemd commands time out, breaking things like Ansible: - failed: [...] (item=apt-daily-upgrade.service) => {[...] "msg": "Unable to disable service apt-daily-upgrade.service: Failed to execute operation: Connection timed out\n"} The problem seems to be related to empty cgroup notification on the legacy/classic hierarchy; it doesn't happen on hybrid or unified hierarchies. The fix is upstream systemd commit d8fdc62037b5 ("core: use an AF_UNIX/SOCK_DGRAM socket for cgroup agent notification"). That patch is already in progress/review in bug 1846787 [2], and is present on Bionic and later, only Xenial is required. [Test Case] Create K8s pods with secret volume mounts (example below) on Xenial/4.15 kernel, and check this after it completes: $ sudo systemctl list-units --type=scope | grep 'Kubernetes transient mount for' (With the fix applied, there are zero units reported) Steps: - Create a Xenial VM: $ uvt-simplestreams-libvirt sync release=xenial arch=amd64 $ uvt-kvm create --memory 8192 --cpu 8 --disk 8 vm-xenial release=xenial arch=amd64 Install the HWE/4.15 kernel and MicroK8s on it: $ uvt-kvm wait vm-xenial $ uvt-kvm ssh vm-xenial $ sudo apt update $ sudo apt install linux-image-4.15.0-65-generic $ sudo reboot $ uvt-kvm wait vm-xenial $ uvt-kvm ssh vm-xenial $ sudo snap install microk8s --channel=1.16/stable --classic $ sudo snap alias microk8s.kubectl kubectl $ sudo usermod -a -G microk8s $USER $ exit Check package versions: $ uvt-kvm ssh vm-xenial $ lsb_release -cs xenial $ uname -rv 4.15.0-65-generic #74~16.04.1-Ubuntu SMP Wed Sep 18 09:51:44 UTC 2019 $ snap list microk8s Name Version Rev Tracking Publisher Notes microk8s v1.16.0 920 1.16 canonical✓ classic $ dpkg -s systemd | grep ^Version: Version: 229-4ubuntu21.22 Create a pod with a secret/volume: $ cat < pod-with-secret.yaml apiVersion: v1 kind: Pod metadata: name: pod-with-secret spec: containers: - name: container image: debian:stretch args: ["/bin/true"] volumeMounts: - name: secret mountPath: /secret volumes: - name: secret secret: secretName: secret-for-pod restartPolicy: Never EOF $ kubectl create secret generic secret-for-pod --from- literal=key=value Notice it leaves a transient scope unit running even after complete: $ systemctl list-units --type=scope | grep 'Kubernetes transient mount for' $ $ kubectl create -f pod-with-secret.yaml $ kubectl get pods NAME READY STATUS RESTARTS AGE pod-with-secret 0/1 Completed 0 30s $ systemctl list-units --type=scope | grep 'Kubernetes transient mount for' run-r560fcf858630417780c258c55fa21c8b.scope loaded active running Kubernetes transient mount for /var/snap/microk8s/common/var/lib/kubelet/pods/7baa3896-a4ef-4c11-a2c2-09f94ca565f7/volumes/kubernetes.io~secret/default-token-24k4f And more transient scope units are left running as the pod is created again (e.g., like cronjob). $ kubectl delete pods pod-with-secret $ kubectl create -f pod-with-secret.yaml $ systemctl list-units --type=scope | grep 'Kubernetes transient mount for' run-r560fcf858630417780c258c55fa21c8b.scope loaded active running Kubernetes transient mount for /var/snap/microk8s/common/var/lib/kubelet/pods/7baa
[Group.of.nepali.translators] [Bug 1847512] Re: xenial: leftover scope units for Kubernetes transient mounts
*** This bug is a duplicate of bug 1846787 *** https://bugs.launchpad.net/bugs/1846787 Marking this bug as a duplicate of bug 1846787 for the systemd fix. ** This bug has been marked a duplicate of bug 1846787 systemd-logind leaves leftover sessions and scope files -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1847512 Title: xenial: leftover scope units for Kubernetes transient mounts Status in systemd package in Ubuntu: Invalid Status in systemd source package in Xenial: In Progress Bug description: [Impact] When running Kubernetes on Xenial there's a leftover scope unit for the transient mounts used by a pod (eg, secret volume mount) together with its associate cgroup dirs, after the pod completes, almost every time such pod is created: $ systemctl list-units --type=scope | grep 'Kubernetes transient mount for' run-r560fcf858630417780c258c55fa21c8b.scope loaded active running Kubernetes transient mount for /var/snap/microk8s/common/var/lib/kubelet/pods/(...)/volumes/kubernetes.io~secret/(...) /sys/fs/cgroup/devices/system.slice/run-r560fcf858630417780c258c55fa21c8b.scope /sys/fs/cgroup/pids/system.slice/run-r560fcf858630417780c258c55fa21c8b.scope /sys/fs/cgroup/blkio/system.slice/run-r560fcf858630417780c258c55fa21c8b.scope /sys/fs/cgroup/memory/system.slice/run-r560fcf858630417780c258c55fa21c8b.scope /sys/fs/cgroup/cpu,cpuacct/system.slice/run-r560fcf858630417780c258c55fa21c8b.scope /sys/fs/cgroup/systemd/system.slice/run-r560fcf858630417780c258c55fa21c8b.scope This problem becomes noticeable with Kubernetes CronJobs as time goes by, as it repeatedly recreates pods to run the cronjob task. Over time, the leftover units (and associated cgroup directories) pile up to a significant amount, and start to cause problems for other components, with effects on /sys/fs/cgroup/ scanning: - Kubelet CPU/Memory Usage linearly increases using CronJob [1] and systemd commands time out, breaking things like Ansible: - failed: [...] (item=apt-daily-upgrade.service) => {[...] "msg": "Unable to disable service apt-daily-upgrade.service: Failed to execute operation: Connection timed out\n"} The problem seems to be related to empty cgroup notification on the legacy/classic hierarchy; it doesn't happen on hybrid or unified hierarchies. The fix is upstream systemd commit d8fdc62037b5 ("core: use an AF_UNIX/SOCK_DGRAM socket for cgroup agent notification"). That patch is already in progress/review in bug 1846787 [2], and is present on Bionic and later, only Xenial is required. [Test Case] Create K8s pods with secret volume mounts (example below) on Xenial/4.15 kernel, and check this after it completes: $ sudo systemctl list-units --type=scope | grep 'Kubernetes transient mount for' (With the fix applied, there are zero units reported -- see comment #1) Steps: - Create a Xenial VM: $ uvt-simplestreams-libvirt sync release=xenial arch=amd64 $ uvt-kvm create --memory 8192 --cpu 8 --disk 8 vm-xenial release=xenial arch=amd64 Install the HWE/4.15 kernel and MicroK8s on it: $ uvt-kvm wait vm-xenial $ uvt-kvm ssh vm-xenial $ sudo apt update $ sudo apt install linux-image-4.15.0-65-generic $ sudo reboot $ uvt-kvm wait vm-xenial $ uvt-kvm ssh vm-xenial $ sudo snap install microk8s --channel=1.16/stable --classic $ sudo snap alias microk8s.kubectl kubectl $ sudo usermod -a -G microk8s $USER $ exit Check package versions: $ uvt-kvm ssh vm-xenial $ lsb_release -cs xenial $ uname -rv 4.15.0-65-generic #74~16.04.1-Ubuntu SMP Wed Sep 18 09:51:44 UTC 2019 $ snap list microk8s Name Version Rev Tracking Publisher Notes microk8s v1.16.0 920 1.16 canonical✓ classic $ dpkg -s systemd | grep ^Version: Version: 229-4ubuntu21.22 Create a pod with a secret/volume: $ cat < pod-with-secret.yaml apiVersion: v1 kind: Pod metadata: name: pod-with-secret spec: containers: - name: container image: debian:stretch args: ["/bin/true"] volumeMounts: - name: secret mountPath: /secret volumes: - name: secret secret: secretName: secret-for-pod restartPolicy: Never EOF $ kubectl create secret generic secret-for-pod --from- literal=key=value Notice it leaves a transient scope unit running even after complete: $ systemctl list-units --type=scope | grep 'Kubernetes transient mount for' $ $ kubectl create -f pod-with-secret.yaml $ kubectl get
[Group.of.nepali.translators] [Bug 1820075] Re: [Packaging] Improve config annotations check on custom kernels
This bug was fixed in the package linux-gcp - 5.0.0-1020.20~18.04.1 --- linux-gcp (5.0.0-1020.20~18.04.1) bionic; urgency=medium * bionic/linux-gcp: 5.0.0-1020.20~18.04.1 -proposed tracker (LP: #1846012) [ Ubuntu: 5.0.0-1020.20 ] * disco/linux-gcp: 5.0.0-1020.20 -proposed tracker (LP: #1846015) * disco/linux: 5.0.0-31.33 -proposed tracker (LP: #1846026) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * /proc/self/maps paths missing on live session (was vlc won't start; eoan 19.10 & bionic 18.04 ubuntu/lubuntu/kubuntu/xubuntu/ubuntu-mate dailies) (LP: #1842382) - SAUCE: Revert "UBUNTU: SAUCE: shiftfs: enable overlayfs on shiftfs" -- Khalid Elmously Fri, 04 Oct 2019 04:26:12 -0400 ** Changed in: linux-gcp (Ubuntu Bionic) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1820075 Title: [Packaging] Improve config annotations check on custom kernels Status in linux-azure package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-azure source package in Xenial: Fix Released Status in linux-gcp source package in Xenial: New Status in linux-oracle source package in Xenial: New Status in linux-azure source package in Bionic: Fix Released Status in linux-gcp source package in Bionic: Fix Released Status in linux-oracle source package in Bionic: New Status in linux-azure source package in Cosmic: Fix Released Status in linux-gcp source package in Cosmic: Fix Released Status in linux-oracle source package in Cosmic: New Status in linux-azure source package in Disco: Fix Released Status in linux-gcp source package in Disco: New Status in linux-oracle source package in Disco: New Bug description: [Impact] Currently for custom kernels, it's necessary to keep a separate annotations file that often gets out of sync with the corresponding file in debian.master/. The "debian/scripts/config-check" script can be changed to allow additional annotations files to act as overlays over the original annotations file, allowing custom kernels to override the policies just for the relevant configs. The proposal is to add support for an include directive in the annotations file so custom kernels can include the annotations file from its base kernel and override policies on a config basis. [Test Case] A kernel build should complete successfully after the change. [Regression Potential] Low regression potential since that's a change on the build process that doesn't affect the final kernel that is built. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1820075/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1840766] Re: Roll bionic/linux-gcp to 5.0
This bug was fixed in the package linux-gcp - 5.0.0-1020.20~18.04.1 --- linux-gcp (5.0.0-1020.20~18.04.1) bionic; urgency=medium * bionic/linux-gcp: 5.0.0-1020.20~18.04.1 -proposed tracker (LP: #1846012) [ Ubuntu: 5.0.0-1020.20 ] * disco/linux-gcp: 5.0.0-1020.20 -proposed tracker (LP: #1846015) * disco/linux: 5.0.0-31.33 -proposed tracker (LP: #1846026) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * /proc/self/maps paths missing on live session (was vlc won't start; eoan 19.10 & bionic 18.04 ubuntu/lubuntu/kubuntu/xubuntu/ubuntu-mate dailies) (LP: #1842382) - SAUCE: Revert "UBUNTU: SAUCE: shiftfs: enable overlayfs on shiftfs" -- Khalid Elmously Fri, 04 Oct 2019 04:26:12 -0400 ** Changed in: linux-gcp (Ubuntu Bionic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1840766 Title: Roll bionic/linux-gcp to 5.0 Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Fix Released Status in linux-gcp source package in Bionic: Fix Released Bug description: With consent of Google we roll the GCP kernel in Bionic forward to be based on kernel version 5.0. This was provided as linux-gcp-edge before. While not directly related, this requires changes to how xenial/linux- gcp is maintained. Until now this was done as a backport of the bionic /linux-gcp but as xenial/linux-gcp is supposed to remain at kernel version 4.15 it has to become a derivative of bionic/linux. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1840766/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
This bug was fixed in the package systemd - 237-3ubuntu10.31 --- systemd (237-3ubuntu10.31) bionic; urgency=medium [ Dimitri John Ledkov ] * Add conflicts with upstart and systemd-shim. (LP: #1773859) * d/p/debian/UBUNTU-units-disable-journald-watchdog.patch - units: Disable journald Watchdog (LP: #1773148) * d/p/cryptsetup-add-support-for-sector-size-option-8881.patch - cryptsetup: add support for sector-size= option (LP: #1776626) * d/p/systemctl-correctly-proceed-to-immediate-shutdown-if-sche.patch - systemctl: correctly proceed to immediate shutdown if scheduling fails (LP: #1670291) * d/p/networkd-add-support-to-configure-IPv6-MTU-8664.patch - networkd: add support to set IPv6MTUBytes (LP: #1671951) -- Balint Reczey Mon, 30 Sep 2019 17:23:17 +0200 ** Changed in: systemd (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot Status in landscape-client package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in landscape-client source package in Trusty: Fix Released Status in systemd source package in Trusty: New Status in landscape-client source package in Xenial: Fix Released Status in systemd source package in Xenial: Fix Released Status in landscape-client source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in landscape-client source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: https://github.com/systemd/systemd/pull/10061 [Impact] * When logind is not available, shutdown command fails to schedule a shutdown, and despite its intentions to immediately shutdown, does not do so. [Test Case] sudo systemctl mask systemd-logind.service sudo systemctl stop systemd-logind.service shutdown +1 The expectation is that system goes to shutdown. It is buggy if the system remains up - i.e. command returns to shell with exit code 1. [Regression Potential] * It is a corner case to run against systemd-shim logind / or logind not otherwise available. The function still performs a clean-shutdown, and should not cause loss of work. [Other Info] * Original bug report, running against systemd-shim/systemd-service post trusty->xenial upgrade, pre-reboot. Used Landscape (Paid Canonical Subscription) to upgrade one of my machines. Landscape only shows "In Progress" for more than 8 hours now and asked for a reboot of the machine in a second alert. In the reboot attempt I get the message: = Failed to set wall message, ignoring: Method "SetWallMessage" with signature "sb" on interface "org.freedesktop.login1.Manager" doesn't exist Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Method "ScheduleShutdown" with signature "st" on interface "org.freedesktop.login1.Manager" doesn't exist = Steps to reproduce: * Fully updated 14.04.5 machine * Open Landscape * Choose the machine * Choose Packages * This computer can be upgraded to a newer release * Apply * Wait 2 hours * Alert comes in a seperate Landscape message Machine is ready for reboot * Choose Info... Power * Deliver to selected computers as soon as possible * Error message I found this thread on reddit about this issue maybe the solution can be built into the upgrade script https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1773148] Re: /lib/systemd/systemd-journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate
This bug was fixed in the package systemd - 237-3ubuntu10.31 --- systemd (237-3ubuntu10.31) bionic; urgency=medium [ Dimitri John Ledkov ] * Add conflicts with upstart and systemd-shim. (LP: #1773859) * d/p/debian/UBUNTU-units-disable-journald-watchdog.patch - units: Disable journald Watchdog (LP: #1773148) * d/p/cryptsetup-add-support-for-sector-size-option-8881.patch - cryptsetup: add support for sector-size= option (LP: #1776626) * d/p/systemctl-correctly-proceed-to-immediate-shutdown-if-sche.patch - systemctl: correctly proceed to immediate shutdown if scheduling fails (LP: #1670291) * d/p/networkd-add-support-to-configure-IPv6-MTU-8664.patch - networkd: add support to set IPv6MTUBytes (LP: #1671951) -- Balint Reczey Mon, 30 Sep 2019 17:23:17 +0200 ** Changed in: systemd (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1773148 Title: /lib/systemd/systemd- journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate Status in systemd: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * systemd aborts journald, upon watchdog expiry and generates lots of crash reports * it appears that journald is simply stuck in fsync * it has been agreed to disable watchdog timer on journald [Test Case] * watch drop-off of errors w.r.t. watchdog timer [Regression Potential] * Potentially journald does get stuck, and thus is no longer automatically restarted with a sigabrt crash. However, so far, it is not known to do that. [Other Info] * Original bug report The Ubuntu Error Tracker has been receiving reports about a problem regarding systemd. This problem was most recently seen with package version 237-3ubuntu10, the problem page at https://errors.ubuntu.com/problem/ff29f7ff39be0e227f0187ad72e5d458e95f6fcf contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1773148/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp