[Group.of.nepali.translators] [Bug 1870657] Re: xenial/linux-fips: 4.4.0-1033.38 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** 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: 1870660 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips - phase: Promote to Proposed - phase-changed: Tuesday, 14. April 2020 08:31 UTC + phase: Testing + phase-changed: Tuesday, 14. April 2020 08:42 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-signing-to-proposed: Stalled -- review in progress + regression-testing: Ongoing -- testing in progress + verification-testing: Ongoing -- testing in progress variant: debs versions: main: 4.4.0-1033.38 meta: 4.4.0.1033.35 signed: 4.4.0-1033.38 -- 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/1870657 Title: xenial/linux-fips: 4.4.0-1033.38 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux source package in Xenial: New 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: 1870660 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Testing phase-changed: Tuesday, 14. April 2020 08:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs versions: main: 4.4.0-1033.38 meta: 4.4.0.1033.35 signed: 4.4.0-1033.38 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1870657/+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 1860813] Re: LXC container reports spike in swap occasionally
This bug was fixed in the package lxcfs - 3.0.3-0ubuntu1~18.04.2 --- lxcfs (3.0.3-0ubuntu1~18.04.2) bionic; urgency=medium * d/p/0001-better-handle-swapfree-calculation.patch: (LP: #1860813) - bindings: fix swapFree calculation with swap accounting enabled -- Kellen Renshaw Tue, 31 Mar 2020 16:20:51 + ** Changed in: lxcfs (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: lxcfs (Ubuntu Eoan) 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/1860813 Title: LXC container reports spike in swap occasionally Status in lxcfs package in Ubuntu: Fix Released Status in lxcfs source package in Xenial: Invalid Status in lxcfs source package in Bionic: Fix Released Status in lxcfs source package in Eoan: Fix Released Bug description: [Impact] * lxcfs provides a container-specific view of /proc/meminfo. Occasionally, with near zero or zero swap usage *and* swap accounting turned on (kernel parameter swapaccount=1), the container will report 100% swap utilization. * This issue has been encountered and could result in unecessary alerts or potential automated attempts at remediating a non-existent "full swap" issue. * This fix changed the logic used for SwapFree when swap accounting is enabled to better handle situations where memswusage is less than memusage, caused by the fuzziness of the usage_in_bytes counters used as the source. Specifically, it added a check for memusage being larger than memswusage and if so, sets 0 as the value of swapusage. Otherwise the calculation (memswusage - memusage) remains the same. [Test Case] * Requires a Bionic (18.04) or Eoan (19.10) host with swap space. * Enable swap accounting with the "swapaccount=1" kernel parameter on the kernel command line. Edit /etc/default/grub, add "swapaccount=1" to the GRUB_CMDLINE_LINUX_DEFAULT="other parameters" line, then run "update-grub" and reboot to make the change active. * Ensure lxd is installed, "sudo apt install lxd" * Create a lxd/lxc container with "lxc launch ubuntu:X container_name" with X being either b[ionic] or e[oan]. * Open two shells to the container with "lxc shell container_name" * In one of the shells, run: watch -n 0.1 "grep Swap /proc/meminfo" * In the other, run: while true; do free; done * You should see SwapFree intermittently drop to zero in the first terminal. * The fix results in small non-zero swap "usage" intermittently instead of intermittent SwapFree = 0. [Regression Potential] * Low, as swap accounting must be enabled to encounter the bug and the fix. * Potential for unanticipated edge cases in the values of memusage and memswusage to cause incorrect swap reporting within the container, with swap accounting turned on. * Any tooling that expected, compensated, or relied on the behavior may no longer work as expected. [Other Info] * Cherrypick of a one line fix to address this specific situation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxcfs/+bug/1860813/+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 1837914] Re: restart systemd-jounald fails
** Also affects: systemd (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: Incomplete => Fix Released ** Changed in: systemd (Ubuntu Xenial) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: systemd (Ubuntu Eoan) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: systemd (Ubuntu Eoan) Status: New => In Progress ** Changed in: systemd (Ubuntu Xenial) Status: New => In Progress ** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress ** Changed in: systemd (Ubuntu Eoan) Importance: Undecided => Low ** Description changed: + [impact] + + in some situations, restarting journald causes assertion failure. + + [test case] + + TDB + + [regression potential] + + this adjusts the journal file destructor, so any regression would likely + occur when cleaning up journal files and/or stopping/restarting. + + [scope] + + this is fixed by commit c377a6f3ad3d9bed4ce7e873e8e9ec6b1650c57d which + is included in Focal. This is needed for Eoan and earlier. + + [original description] + While restarting systemd-jounald, the following error message occurs: systemd-journald[28007]: Assertion 'f' failed at ../src/journal/journal- file.c:143, function journal_file_close(). Aborting. release: Ubuntu 16.04.5 LTS systemd version: 229-4ubuntu21.22 This issue is reported at https://github.com/systemd/systemd/issues/12400 and solved at https://github.com/systemd/systemd/pull/12679 Please cherry-pick this fix to the ubuntu16.04 package. -- 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/1837914 Title: restart systemd-jounald fails Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Eoan: In Progress Bug description: [impact] in some situations, restarting journald causes assertion failure. [test case] intermittently, when restarting journald. See upstream bug for repro details. [regression potential] this adjusts the journal file destructor, so any regression would likely occur when cleaning up journal files and/or stopping/restarting. [scope] this is fixed by commit c377a6f3ad3d9bed4ce7e873e8e9ec6b1650c57d which is included in Focal. This is needed for Eoan and earlier. [original description] While restarting systemd-jounald, the following error message occurs: systemd-journald[28007]: Assertion 'f' failed at ../src/journal /journal-file.c:143, function journal_file_close(). Aborting. release: Ubuntu 16.04.5 LTS systemd version: 229-4ubuntu21.22 This issue is reported at https://github.com/systemd/systemd/issues/12400 and solved at https://github.com/systemd/systemd/pull/12679 Please cherry-pick this fix to the ubuntu16.04 package. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1837914/+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 1864233] Re: Commits to resolve high network latency
** Changed in: linux-azure (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Also affects: linux-azure-4.15 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-azure-4.15 (Ubuntu Xenial)
Status: New => Invalid
** Also affects: linux-azure (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux-azure-4.15 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux-azure-4.15 (Ubuntu Bionic)
Status: New => Fix Committed
** Changed in: linux-azure (Ubuntu Bionic)
Status: New => Invalid
--
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/1864233
Title:
Commits to resolve high network latency
Status in linux-azure package in Ubuntu:
New
Status in linux-azure-4.15 package in Ubuntu:
New
Status in linux-azure source package in Xenial:
Fix Committed
Status in linux-azure-4.15 source package in Xenial:
Invalid
Status in linux-azure source package in Bionic:
Invalid
Status in linux-azure-4.15 source package in Bionic:
Fix Committed
Bug description:
An issue has been identified with the NETVSC driver on Azure VMs. This
issues has been fixed by four patches, which are available in the
mainline kernel.
The issues is the following:
Outgoing traffic is sent from the guest to the Azure host over multiple
parallel channels. The issue causes the traffic to be unevenly balanced across
the channels, which results in a physical CPU on the Azure host becoming
overloaded. In turn, the network traffic on the overloaded channel experiences
significantly higher latency. This higher latency is causing issues for
customers.
This issue is resolved by the following four mainline commits:
71f21959dd55 ("hv_netvsc: Fix offset usage in netvsc_send_table()")
171c1fd98df3 ("hv_netvsc: Fix send_table offset in case of a host bug")
c39ea5cba5a2 ("hv_netvsc: Fix tx_table init in rndis_set_subchannel()")
b0689faa8efc ("hv_netvsc: Fix unwanted rx_table reset")
These four commits have been submitted to upstream stable.
We would like to request these commits in Azure kernels for Xenial and
Bionic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1864233/+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 1864669] Re: [linux-azure] overlayfs regression - internal getxattr operations without sepolicy checking
** Also affects: linux-azure-4.15 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux-azure-4.15 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux-azure-4.15 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Focal)
Importance: Undecided
Status: Fix Released
** Also affects: linux-azure-4.15 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: linux-azure-4.15 (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: linux-azure-4.15 (Ubuntu Xenial)
Status: New => Invalid
** Changed in: linux-azure-4.15 (Ubuntu Bionic)
Status: New => Fix Committed
** Changed in: linux-azure-4.15 (Ubuntu Eoan)
Status: New => Invalid
** Changed in: linux-azure-4.15 (Ubuntu Focal)
Status: New => Invalid
** Changed in: linux-azure (Ubuntu Eoan)
Status: New => Fix Committed
** Changed in: linux-azure (Ubuntu Bionic)
Status: New => Fix Committed
** Changed in: linux-azure (Ubuntu Xenial)
Status: New => Fix Committed
--
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/1864669
Title:
[linux-azure] overlayfs regression - internal getxattr operations
without sepolicy checking
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-4.15 package in Ubuntu:
Invalid
Status in linux-azure source package in Xenial:
Fix Committed
Status in linux-azure-4.15 source package in Xenial:
Invalid
Status in linux-azure source package in Bionic:
Fix Committed
Status in linux-azure-4.15 source package in Bionic:
Fix Committed
Status in linux-azure source package in Eoan:
Fix Committed
Status in linux-azure-4.15 source package in Eoan:
Invalid
Status in linux-azure source package in Focal:
Fix Released
Status in linux-azure-4.15 source package in Focal:
Invalid
Bug description:
Bug description and repro:
Run the following commands on host instances:
Prepare the overlayfs directories:
$ cd /tmp
$ mkdir -p base/dir1/dir2 upper olwork merged
$ touch base/dir1/dir2/file
$ chown -R 10:10 base upper olwork merged
Verify that the directory is owned by user 10:
$ ls -al merged/
total 8
drwxr-xr-x 2 10 10 4096 Nov 1 07:08 .
drwxrwxrwt 16 root root 4096 Nov 1 07:08 ..
We use lxc-usernsexec to start a new shell as user 10.
$ lxc-usernsexec -m b:0:10:1 -- /bin/bash
$$ ls -al merged/
total 8
drwxr-xr-x 2 root root4096 Nov 1 07:08 .
drwxrwxrwt 16 nobody nogroup 4096 Nov 1 07:08 ..
Notice that the ownership of . and .. has changed because the new shell is
running as the remapped user.
Now, mount the overlayfs as an unprivileged user in the new shell. This is
the key to trigger the bug.
$$ mount -t overlay -o lowerdir=base,upperdir=upper,workdir=olwork none merged
$$ ls -al merged/dir1/dir2/file
-rw-r--r-- 1 root root 0 Nov 1 07:09 merged/dir1/dir2/file
We can see the file in the base layer from the mount directory. Now trigger
the bug:
$$ rm -rf merged/dir1/dir2/
$$ mkdir merged/dir1/dir2
$$ ls -al merged/dir1/dir2
total 12
drwxr-xr-x 2 root root 4096 Nov 1 07:10 .
drwxr-xr-x 1 root root 4096 Nov 1 07:10 ..
File does not show up in the newly created dir2 as expected. But it will
reappear after we remount the filesystem (or any other means that might evict
the cached dentry, such as attempt to delete the parent directory):
$$ umount merged
$$ mount -t overlay -o lowerdir=base,upperdir=upper,workdir=olwork none merged
$$ ls -al merged/dir1/dir2
total 12
drwxr-xr-x 1 root root 4096 Nov 1 07:10 .
drwxr-xr-x 1 root root 4096 Nov 1 07:10 ..
-rw-r--r-- 1 root root0 Nov 1 07:09 file
$$ exit
$
This is a recent kernel regression. I tried the above step on an old
kernel (4.4.0-1072-aws) but cannot reproduce.
I looked up linux source code and figured out where the "regression" is
coming from. The issue lies in how overlayfs checks the "opaque" flag from the
underlying upper-level filesystem. It checks the "trusted.overlay.opaque"
extended attribute to decide whether to hide the directory content from the
lower level. The logic are different in 4.4 and 4.15 kernel.
In 4.4: https://elixir.bootlin.com/linux/v4.4/source/fs/overlayfs/super.c#L255
static bool ovl_is_opaquedir(struct dentry *dentry)
{
int res;
char val;
struct inode *inode = dentry->d_inode;
if (!S_ISDIR(inode->i_mode) || !inode->i_op->getxattr)
[Group.of.nepali.translators] [Bug 1870683] Re: xenial/linux-azure: 4.15.0-1082.92~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => 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 -- kernel-stable-master-bug: 1870673 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Packaging - phase-changed: Tuesday, 14. April 2020 21:36 UTC + phase: Holding before Promote to Proposed + phase-changed: Tuesday, 14. April 2020 22:57 UTC reason: - prepare-package: Pending -- tag not published and package not - uploaded - prepare-package-meta: Pending -- tag not published and package not - uploaded - prepare-package-signed: Pending -- tag not published and package not - uploaded + build-packages-ppa: Ongoing -- building in ppa main:building trackers: trusty/linux-azure: bug 1870682 xenial/linux-azure/azure-kernel: bug 1870681 variant: debs + versions: + main: 4.15.0-1082.92~16.04.1 + meta: 4.15.0.1082.81 + signed: 4.15.0-1082.92~16.04.1 -- 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/1870683 Title: xenial/linux-azure: 4.15.0-1082.92~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New 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: New 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure source package in Xenial: New 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 -- kernel-stable-master-bug: 1870673 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Tuesday, 14. April 2020 22:57 UTC reason: build-packages-ppa: Ongoing -- building in ppa main:building trackers: trusty/linux-azure: bug 1870682 xenial/linux-azure/azure-kernel: bug 1870681 variant: debs versions: main: 4.15.0-1082.92~16.04.1 meta: 4.15.0.1082.81 signed: 4.15.0-1082.92~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1870683/+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 1870688] Re: xenial/linux-hwe: 4.15.0-97.98~16.04.1 -proposed tracker
4.15.0-97.98~16.04.1 - lowlatency Regression test CMPL, RTB. 56 / 59 tests were run, missing: ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, ubuntu_xfstests_xfs Issue to note in amd64: ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) vmx_host_state_area (bug 1866585) vmx_intr_window_test (bug 1866586) vmx_nm_test (bug 1866587) vmx_nmi_window_test (bug 1866588) vmx_pending_event_test (bug 1866591) ubuntu_ltp_syscalls - add_key05 (bug 1869644) btrfs fill_fs test in fallocate06 (bug 1866323) quotactl04 (bug 1854153) statx05 (bug 1798524) kill11 (bug 1865965) 50 / 54 tests were run, missing: ubuntu_kvm_unit_tests, ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, ubuntu_xfstests_xfs Issue to note in i386: ubuntu_ltp_syscalls - add_key05 (bug 1869644) btrfs fill_fs test in fallocate06 (bug 1866323) quotactl04 (bug 1854153) statx05 (bug 1798524) kill11 (bug 1865965) 4.15.0-97.98~16.04.1 - generic Regression test CMPL, RTB. 56 / 59 tests were run, missing: ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, ubuntu_xfstests_xfs Issue to note in amd64: ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) vmx_host_state_area (bug 1866585) vmx_intr_window_test (bug 1866586) vmx_nm_test (bug 1866587) vmx_nmi_window_test (bug 1866588) vmx_pending_event_test (bug 1866591) ubuntu_ltp_syscalls - add_key05 (bug 1869644) btrfs fill_fs test in fallocate06 (bug 1866323) quotactl04 (bug 1854153) statx05 (bug 1798524) kill11 (bug 1865965) 50 / 53 tests were run, missing: ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, ubuntu_xfstests_xfs Issue to note in arm64: hwclock - issue for HP m400 (bug 1716603) ubuntu_kernel_selftests - cpu-hotplug failed on moonshot (bug 1809701) ubuntu_kvm_smoke_test - unable to create KVM with uvtool (bug 1749427) ubuntu_kvm_unit_tests - gicv2-ipi (bug 1790825) gicv2-mmio-3p (bug 1828027) gicv2-mmio-up (bug 1828026) gicv2 related test failed on ThunderX (bug 1828153) pmu on starmie (bug 1751000) ubuntu_ltp_syscalls - add_key05 (bug 1869644) btrfs fill_fs test in fallocate06 (bug 1866323) quotactl04 (bug 1854153) statx05 (bug 1798524) kill11 (bug 1865965) 50 / 54 tests were run, missing: ubuntu_kvm_unit_tests, ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, ubuntu_xfstests_xfs Issue to note in i386: ubuntu_ltp_syscalls - add_key05 (bug 1869644) btrfs fill_fs test in fallocate06 (bug 1866323) quotactl04 (bug 1854153) statx05 (bug 1798524) kill11 (bug 1865965) 52 / 55 tests were run, missing: ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, ubuntu_xfstests_xfs Issue to note in ppc64le (P8): ubuntu_fan_smoke_test - Failed to fetch file from http://ports.ubuntu.com (bug 1864140) ubuntu_kernel_selftests - reuseport_bpf_cpu in net (bug 1872652) reuseport_bpf_numa in net (bug 1867570) reuseport_bpf in net (bug 1868654) TRACE_syscall.ptrace_syscall_errno in seccomp (bug 1829359) TRACE_syscall.ptrace_syscall_faked in seccomp (bug 1829363) ubuntu_ltp_syscalls - add_key05 (bug 1869644) btrfs fill_fs test in fallocate06 (bug 1866323) move_pages12 (bug 1831043) quotactl04 (bug 1854153) statx05 (bug 1798524) kill11 (bug 1865965) ubuntu_seccomp - 36-sim-ipc_syscalls, 37-sim-ipc_syscalls_be failed on s390x / PowerPC (bug 1850904) ubuntu_sysdig_smoke_test - Unable to build sysdig module on PowerPC with X-4.15 (bug 1810916) ** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- 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/1870688 Title: xenial/linux-hwe: 4.15.0-97.98~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: In Progress 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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-hwe source package in Xenial: New 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-sr
[Group.of.nepali.translators] [Bug 1870651] Re: xenial/linux-cascade: 4.4.0-1017.19 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** 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 -- kernel-stable-master-bug: 1870660 packages: main: linux-cascade meta: linux-meta-cascade signed: linux-signed-cascade - phase: Ready for Packaging - phase-changed: Monday, 06. April 2020 06:40 UTC + phase: Packaging + phase-changed: Wednesday, 15. April 2020 05:06 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- tag not published and package not + uploaded + prepare-package-meta: Pending -- tag not published and package not + uploaded + prepare-package-signed: Pending -- tag not published and package not + uploaded trackers: xenial/linux-cascade/cascade-kernel: bug 1870650 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/1870651 Title: xenial/linux-cascade: 4.4.0-1017.19 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux source package in Xenial: New 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 -- kernel-stable-master-bug: 1870660 packages: main: linux-cascade meta: linux-meta-cascade signed: linux-signed-cascade phase: Packaging phase-changed: Wednesday, 15. April 2020 05:06 UTC reason: prepare-package: Pending -- tag not published and package not uploaded prepare-package-meta: Pending -- tag not published and package not uploaded prepare-package-signed: Pending -- tag not published and package not uploaded trackers: xenial/linux-cascade/cascade-kernel: bug 1870650 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1870651/+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 1870660] Re: xenial/linux: 4.4.0-178.208 -proposed tracker
4.4.0-178.208 - lowlatency Regression test CMPL, RTB. 58 / 59 tests were run, missing: ubuntu_xfstests_ext4 Issue to note in amd64: ubuntu_kvm_unit_tests - apic (bug 1748103) debug (bug 1821906) vmx (bug 1821394) vmx_host_state_area (bug 1866585) vmx_intr_window_test (bug 1866586) vmx_nm_test (bug 1866587) vmx_nmi_window_test (bug 1866588) vmx_pending_event_test (bug 1866591) ubuntu_ltp_syscalls - add_key05 (bug 1869644) btrfs fill_fs test in fallocate06 (bug 1866323) fanotify06 (bug 1833028) fanotify10 (bug 1802454) kill11 (bug 1865965) ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 1854298) ubuntu_xfstests_btrfs - no scratch drive for the test ubuntu_xfstests_xfs - no scratch drive for the test 50 / 54 tests were run, missing: ubuntu_kvm_unit_tests, ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, ubuntu_xfstests_xfs Issue to note in i386: ubuntu_ltp_syscalls - add_key05 (bug 1869644) btrfs fill_fs test in fallocate06 (bug 1866323) fanotify06 (bug 1833028) fanotify10 (bug 1802454) kill11 (bug 1865965) ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 1854298) 4.4.0-178.208 - generic Regression test CMPL, RTB. 58 / 59 tests were run, missing: ubuntu_xfstests_ext4 Issue to note in amd64: ubuntu_kvm_unit_tests - apic (bug 1748103) debug (bug 1821906) vmx (bug 1821394) vmx_host_state_area (bug 1866585) vmx_intr_window_test (bug 1866586) vmx_nm_test (bug 1866587) vmx_nmi_window_test (bug 1866588) vmx_pending_event_test (bug 1866591) ubuntu_ltp_syscalls - add_key05 (bug 1869644) btrfs fill_fs test in fallocate06 (bug 1866323) fanotify06 (bug 1833028) fanotify10 (bug 1802454) kill11 (bug 1865965) ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 1854298) ubuntu_xfstests_btrfs - no scratch drive for the test ubuntu_xfstests_xfs - no scratch drive for the test 51 / 54 tests were run, missing: ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, ubuntu_xfstests_xfs Issue to note in arm64: hwclock - issue for HP m400 (bug 1716603) ubuntu_kernel_selftests - cpu-hotplug failed on moonshot (bug 1809701) ubuntu_kvm_smoke_test - unable to create KVM with uvtool (bug 1749427) ubuntu_kvm_unit_tests - gicv2-mmio on X-ARM64 (bug 1828165) gicv2-mmio-3p (bug 1828027) gicv2-mmio-up (bug 1828026) pmu on ms10-34-mcdivittB0-kernel (bug 1751000) ubuntu_ltp_syscalls - add_key05 (bug 1869644) btrfs fill_fs test in fallocate06 (bug 1866323) fanotify06 (bug 1833028) fanotify10 (bug 1802454) kill11 (bug 1865965) ubuntu_unionmount_ovlfs - failed with commit dc24a45a upstream (bug 1854298) 50 / 54 tests were run, missing: ubuntu_kvm_unit_tests, ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, ubuntu_xfstests_xfs Issue to note in i386: ubuntu_ltp_syscalls - add_key05 (bug 1869644) btrfs fill_fs test in fallocate06 (bug 1866323) fanotify06 (bug 1833028) fanotify10 (bug 1802454) kill11 (bug 1865965) ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 1854298) 52 / 55 tests were run, missing: ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, ubuntu_xfstests_xfs Issue to note in ppc64le (P8): ubuntu_btrfs_kernel_fixes - Unable to mount a btrfs filesystem smaller than 320M on Xenial P8 (bug 1813863) ubuntu_fan_smoke_test - Failed to fetch file from http://ports.ubuntu.com (bug 1864140) ubuntu_ltp_syscalls - add_key05 (bug 1869644) copy_file_range01, fallocate04, fanotify13, fanotify14, fanotify15, fdatasync03, fgetxattr01,fremovexattr01, fremovexattr02, fsetxattr01, fsync01, fsync04, lremovexattr01, msync04, preadv03, preadv03_64, preadv203, preadv203_64, pwritev03, pwritev03_64, pwritev03, pwritev03_64, setxattr01, sync03, syncfs01 (bug 1842270) btrfs fill_fs test in fallocate06 (bug 1866323) fanotify06 (bug 1833028) fanotify10 (bug 1802454) move_pages12 (bug 1831043) kill11 (bug 1865965) ubuntu_seccomp - 36-sim-ipc_syscalls, 37-sim-ipc_syscalls_be failed on s390x / PowerPC (bug 1850904) ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 1854298) Issue to note in s390x (KVM): libhugetlbfs - failed 5 (Address is not hugepage, Heap not on hugepages) killed by signal 1 bad config 1 ubuntu_bpf_jit - 4 failures reported for X s390x (bug 1768452) ubuntu_kernel_selftests - test_bpf in net (bug 1768452) ubuntu_kvm_smoke_test - uvtool issue (bug 1729854) ubuntu_kvm_unit_tests - test should be skipped for X s390x KVM ubuntu_ltp_syscalls - add_key05 (bug 1869644) btrfs fill_fs test in fallocate06 (bug 1866323) fanotify06 (bug 1833028) fanotify10 (bug 1802454) kill11 (bug 1865965) ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 1854298) Issue to note in s390x (Ubuntu on LPAR): libhugetlbfs - failed 5 (Address is not hugepage, Heap not on hugepages) killed by signal 1 bad config 1 ubuntu_bpf_jit - 4 failures reported for X s390x (bug 1768452) ubuntu_kernel_selftests - test_bpf in net (bug 1768452) ubuntu_kvm_smoke_test - uvtool is
