[Group.of.nepali.translators] [Bug 1838961] Re: timer_create01 from ubuntu_ltp_syscalls failed on X-kvm / B-KVM
Passed on D-KVM ** Changed in: linux-kvm (Ubuntu) Status: In Progress => Fix Released ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released ** Package changed: linux-kvm (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Released ** Changed in: linux (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/1838961 Title: timer_create01 from ubuntu_ltp_syscalls failed on X-kvm / B-KVM Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Bug description: The timer_create01 failed on X-kvm Steps to reproduce: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "timer_create01 timer_create01" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs <<>> tag=timer_create01 stime=1565000454 cmdline="timer_create01" contacts="" analysis=exit <<>> tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s incrementing stop timer_create01.c:48: INFO: Testing notification type: SIGEV_NONE timer_create01.c:93: PASS: Timer successfully created for CLOCK_REALTIME timer_create01.c:93: PASS: Timer successfully created for CLOCK_MONOTONIC timer_create01.c:93: PASS: Timer successfully created for CLOCK_PROCESS_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_THREAD_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_BOOTTIME timer_create01.c:87: FAIL: Failed to create timer for CLOCK_BOOTTIME_ALARM: ??? timer_create01.c:87: FAIL: Failed to create timer for CLOCK_REALTIME_ALARM: ??? timer_create01.c:93: PASS: Timer successfully created for CLOCK_TAI timer_create01.c:48: INFO: Testing notification type: SIGEV_SIGNAL timer_create01.c:93: PASS: Timer successfully created for CLOCK_REALTIME timer_create01.c:93: PASS: Timer successfully created for CLOCK_MONOTONIC timer_create01.c:93: PASS: Timer successfully created for CLOCK_PROCESS_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_THREAD_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_BOOTTIME timer_create01.c:87: FAIL: Failed to create timer for CLOCK_BOOTTIME_ALARM: ??? timer_create01.c:87: FAIL: Failed to create timer for CLOCK_REALTIME_ALARM: ??? timer_create01.c:93: PASS: Timer successfully created for CLOCK_TAI timer_create01.c:48: INFO: Testing notification type: SIGEV_THREAD timer_create01.c:93: PASS: Timer successfully created for CLOCK_REALTIME timer_create01.c:93: PASS: Timer successfully created for CLOCK_MONOTONIC timer_create01.c:93: PASS: Timer successfully created for CLOCK_PROCESS_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_THREAD_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_BOOTTIME timer_create01.c:87: FAIL: Failed to create timer for CLOCK_BOOTTIME_ALARM: ??? timer_create01.c:87: FAIL: Failed to create timer for CLOCK_REALTIME_ALARM: ??? timer_create01.c:93: PASS: Timer successfully created for CLOCK_TAI timer_create01.c:48: INFO: Testing notification type: SIGEV_THREAD_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_REALTIME timer_create01.c:93: PASS: Timer successfully created for CLOCK_MONOTONIC timer_create01.c:93: PASS: Timer successfully created for CLOCK_PROCESS_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_THREAD_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_BOOTTIME timer_create01.c:87: FAIL: Failed to create timer for CLOCK_BOOTTIME_ALARM: ??? timer_create01.c:87: FAIL: Failed to create timer for CLOCK_REALTIME_ALARM: ??? timer_create01.c:93: PASS: Timer successfully created for CLOCK_TAI timer_create01.c:48: INFO: Testing notification type: NULL timer_create01.c:93: PASS: Timer successfully created for CLOCK_REALTIME timer_create01.c:93: PASS: Timer successfully created for CLOCK_MONOTONIC timer_create01.c:93: PASS: Timer successfully created for CLOCK_PROCESS_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_THREAD_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_BOOTTIME timer_create01.c:87: FAIL: Failed to create timer for CLOCK_BOOTTIME_ALARM: ??? timer_create01.c:87: FAIL: Failed to create timer for CLOCK_REALTIME_ALARM: ??? timer_create01.c:93: PASS: Timer successfully created for CLOCK_TAI Summary: passed 30 failed 10 skipped 0 warnings 0 <<>> ProblemType: Bug DistroRelease: Ubuntu 16.04
[Group.of.nepali.translators] [Bug 1849021] Re: xenial/linux-oracle: 4.15.0-1028.31~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/regression-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: 1849022 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 23. October 2019 09:41 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 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/1849021 Title: xenial/linux-oracle: 4.15.0-1028.31~16.04.1 -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: 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-oracle package in Ubuntu: Invalid Status in linux-oracle 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: 1849022 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 23. October 2019 09:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849021/+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 1843674] Re: FTBFS of libvirt in Xenial
This has now been resolved by Bug 1844504, mentioned above by Mauricio. Since the patches to fix the pty issues are no longer needed, I will not SRU them. Thanks for your help Christian and Mauricio. Successful build log of a new libvirt test package, dated today: https://launchpad.net/~mruffell/+archive/ubuntu/sf242822-test/+build/18001022/+files /buildlog_ubuntu-xenial- amd64.libvirt_1.3.1-1ubuntu10.28+sf242822v20191031b1_BUILDING.txt.gz ** Changed in: libvirt (Ubuntu Xenial) Status: New => Won't Fix -- 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/1843674 Title: FTBFS of libvirt in Xenial Status in libvirt package in Ubuntu: Fix Released Status in libvirt source package in Xenial: Won't Fix Bug description: [Impact] * libvirt became FTBFS in xenial due to other changes. Most likely a newer deboostrap that was used. * The fix just modifies the self-tests (not the active code that runs in an ubuntu users env) * The change is already active in Ubuntu in later releases via https://salsa.debian.org/libvirt-team/libvirt/commit/2be70b3 https://salsa.debian.org/libvirt-team/libvirt/commit/7baa0daf https://salsa.debian.org/libvirt-team/libvirt/commit/0ce5eb75 [Test Case] * Build libvirt in Xenial on LP infra and while doing so do not trigger test fails in test-openpty and test-posix_openpt [Regression Potential] * Since we only change self-test code that runs at build time the runtime should show now regressions. The one thing I can think of is that a rebuild could always change something (even a no change rebuild) but since we want to bundle it with other SRUs there would be a rebuild anyway - hence I'd think this has no regression risk of its own. [Other Info] * This should not be fixed standalone but bundled with some other SRU to avoid useless rebuilds - and even more so - users downloading updates for now gain. --- Due to a unknown other update libvirt became an FTBFS in Xenial. The issue shows up at build on launchpad infra and has two seld-tests broken. From the build log: FAIL: test-openpty == openpty returned -1 FAIL test-openpty (exit status: 1) FAIL: test-posix_openpt === ../../../../gnulib/tests/test-posix_openpt.c:52: assertion '0 <= master' failed FAIL test-posix_openpt (exit status: 134) This is somewhat familiar to bug 1641615 but showing up again in Xenial now for yet unknown reasons. The later re-occurrence of this outside of Xenial was later on fixed by [1] for good. Probably now triggering by some SRu of a lib into Xenial (or unlikely some change in the builder setup). We want to add that to Xenial as well to have it build fine again. [1]: https://salsa.debian.org/libvirt-team/libvirt/commit/2be70b3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1843674/+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 1850675] Re: ARM CPU support update
** No longer affects: linux-aws (Ubuntu Xenial) -- 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/1850675 Title: ARM CPU support update Status in linux-aws package in Ubuntu: In Progress Status in linux-aws source package in Bionic: In Progress Status in linux-aws source package in Disco: In Progress Status in linux-aws source package in Eoan: In Progress Bug description: linux-aws kernels need various arm64 commits from mainline to support latest ARM CPUs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1850675/+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 1842701] Re: Apache2 Balancer Manager mod_proxy_balancer not working after Update
** Changed in: apache2 (Debian)
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/1842701
Title:
Apache2 Balancer Manager mod_proxy_balancer not working after Update
Status in Apache2 Web Server:
Confirmed
Status in apache2 package in Ubuntu:
Confirmed
Status in apache2 source package in Xenial:
Fix Released
Status in apache2 source package in Bionic:
Fix Released
Status in apache2 source package in Disco:
Fix Released
Status in apache2 package in Debian:
Fix Released
Bug description:
OS
Description:Ubuntu 18.04.3 LTS
Release:18.04
Codename: bionic
I use this kind of configuration to reache the Balancer Manager.
-
|Bastian Host |
|Apache Proxy | ---> LB Apache Balancer Manger
-
After Apache Update
from: 2.4.29-1ubuntu4.8
to: 2.4.29-1ubuntu4.10
The Balancer Manager behind a Proxy is not Working and i think this is
comming with
the fix CVE-2019-10092
https://httpd.apache.org/security/vulnerabilities_24.html#CVE-2019-10092
http://changelogs.ubuntu.com/changelogs/pool/main/a/apache2/apache2_2.4.29-1ubuntu4.10/changelog
I strip down the configuration to try and explain the situation.
Install new Ubuntu 18.04 VirtualBox. From an another VM i saved the prior
Apache Packages from /var/cache/apt/archives
:~# apt-get install libapr1 libaprutil1 libaprutil1-dbd-sqlite3
libaprutil1-ldap liblua5.2-0
:~# dpkg -i apache2_2.4.29-1ubuntu4.8_amd64.deb
apache2-bin_2.4.29-1ubuntu4.8_amd64.deb apache2-data_2.4.29-1ubuntu4.8_all.deb
apache2-utils_2.4.29-1ubuntu4.8_amd64.deb
:~# dpkg -l | grep apache2
ii apache2 2.4.29-1ubuntu4.8 amd64Apache HTTP Server
ii apache2-bin 2.4.29-1ubuntu4.8 amd64Apache HTTP Server
(modules and other binary files)
ii apache2-data 2.4.29-1ubuntu4.8 all Apache HTTP Server
(common files)
ii apache2-utils2.4.29-1ubuntu4.8 amd64Apache HTTP Server
(utility programs for web servers)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
:~# vim /etc/apache2/sites-available/management.conf
Servername 127.0.0.1
ServerAdmin root@localhost
SetHandler balancer-manager
Require local
#Require ip 192.168.56.0/24 127.0.0.1/24
Require all granted
LogLevel warn
ErrorLog ${APACHE_LOG_DIR}/management_error.log
CustomLog ${APACHE_LOG_DIR}/management_access.log combined
# vim: syntax=apache ts=4 sw=4 sts=4 sr noet
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
:~# vim /etc/apache2/sites-available/proxytest.conf
BalancerMember "http://192.168.168.130/test;
BalancerMember "http://192.168.168.131/test; status=+H
ProxySet lbmethod=bybusyness
ServerAdmin root@localhost
ServerName testapp01
ServerAlias 127.0.0.1:8100
ProxyPass "/test" "balancer://test"
ProxyPassReverse"/test" "balancer://test"
CustomLog ${APACHE_LOG_DIR}/test-access.log combined
ErrorLog ${APACHE_LOG_DIR}/test-error.log
# vim: syntax=apache ts=4 sw=4 sts=4 sr noet
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
:~# a2enmod proxy_balancer proxy_http lbmethod_bybusyness lbmethod_byrequests
:~# a2ensite management proxytest
:~# vim /etc/apache2/ports.conf
[...]
Listen 81
Listen 8100
:~# systemctl restart apache2
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
At that point i install also some console Browsers for testing.
:~# apt-get install lynx elinks
:~# tail -f /var/log/apache2/management_error.log
:~# elinks 127.0.0.1:81/balancer-manager
:~# lynx 127.0.0.1:81/balancer-manager
i can do update the Load and made changes. i also connect from outside with
Firefox
http://192.168.56.211:81/balancer-manager
all this creates no error log entrys, the log is still empty
-
update apache
:~# apt-get update
:~# apt-get upgrade
:~# dpkg -l | grep apache2
ii apache22.4.29-1ubuntu4.10 amd64Apache HTTP Server
ii apache2-bin2.4.29-1ubuntu4.10 amd64Apache HTTP Server
(modules and other binary files)
ii apache2-data 2.4.29-1ubuntu4.10 all Apache HTTP Server
(common files)
ii apache2-utils 2.4.29-1ubuntu4.10 amd64Apache HTTP Server
(utility programs for web servers)
do the same with all the Browsers and have the error log in view.
http://192.168.56.211:81/balancer-manager
:~# tail -f /var/log/apache2/management_error.log
[Wed Sep 04 12:24:55.740457 2019]
[Group.of.nepali.translators] [Bug 1850675] Re: ARM CPU support update
** Also affects: linux-aws (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Xenial) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux-aws (Ubuntu Bionic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux-aws (Ubuntu Disco) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux-aws (Ubuntu Eoan) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux-aws (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Disco) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Eoan) Status: New => In Progress -- 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/1850675 Title: ARM CPU support update Status in linux-aws package in Ubuntu: In Progress Status in linux-aws source package in Xenial: In Progress Status in linux-aws source package in Bionic: In Progress Status in linux-aws source package in Disco: In Progress Status in linux-aws source package in Eoan: In Progress Bug description: linux-aws kernels need various arm64 commits from mainline to support latest ARM CPUs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1850675/+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 1848716] Re: Add Ubuntu Focal as a known release
This bug was fixed in the package debootstrap - 1.0.112ubuntu1.2 --- debootstrap (1.0.112ubuntu1.2) disco; urgency=medium * Add (Ubuntu) focal as a symlink to gutsy. (LP: #1848716) -- Łukasz 'sil2100' Zemczak Fri, 18 Oct 2019 14:15:12 +0100 ** Changed in: debootstrap (Ubuntu Disco) 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/1848716 Title: Add Ubuntu Focal as a known release Status in debootstrap package in Ubuntu: Fix Released Status in debootstrap source package in Xenial: Fix Committed Status in debootstrap source package in Bionic: Fix Committed Status in debootstrap source package in Disco: Fix Released Status in debootstrap source package in Eoan: Fix Released Bug description: [Impact] Without this update users cannot generate focal chroots for development. [Test Case] Attempt to debootstrap focal. [Regression Potential] Very low, this simply introduces a suite specific script which is not used unless you attempt to create and Ubuntu Focal chroot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1848716/+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 1848716] Re: Add Ubuntu Focal as a known release
This bug was fixed in the package debootstrap - 1.0.116ubuntu1.1 --- debootstrap (1.0.116ubuntu1.1) eoan; urgency=medium * Add (Ubuntu) eoan as a symlink to gutsy. (LP: #1848716) -- Łukasz 'sil2100' Zemczak Fri, 18 Oct 2019 14:01:45 +0100 ** Changed in: debootstrap (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/1848716 Title: Add Ubuntu Focal as a known release Status in debootstrap package in Ubuntu: Fix Released Status in debootstrap source package in Xenial: Fix Committed Status in debootstrap source package in Bionic: Fix Committed Status in debootstrap source package in Disco: Fix Released Status in debootstrap source package in Eoan: Fix Released Bug description: [Impact] Without this update users cannot generate focal chroots for development. [Test Case] Attempt to debootstrap focal. [Regression Potential] Very low, this simply introduces a suite specific script which is not used unless you attempt to create and Ubuntu Focal chroot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1848716/+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 1673247] Re: package snapd 2.23.1 failed to install/upgrade: trying to overwrite '/etc/apparmor.d/usr.lib.snapd.snap-confine', which is also in package snap-confine
I'm closing the snapd task, this is a bug in dpkg. ** Changed in: snapd Status: New => Won't Fix -- 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/1673247 Title: package snapd 2.23.1 failed to install/upgrade: trying to overwrite '/etc/apparmor.d/usr.lib.snapd.snap-confine', which is also in package snap-confine 2.23.1 Status in snapd: Won't Fix Status in dpkg package in Ubuntu: In Progress Status in snapd package in Ubuntu: In Progress Status in dpkg source package in Trusty: Confirmed Status in snapd source package in Trusty: In Progress Status in dpkg source package in Xenial: Confirmed Status in snapd source package in Xenial: Confirmed Status in dpkg source package in Yakkety: Invalid Status in snapd source package in Yakkety: Invalid Status in dpkg source package in Zesty: Confirmed Status in snapd source package in Zesty: Confirmed Bug description: When the ubuntu installer runs it has an option to download updates during the install. When this happens snapd/snap-confine 2.22.6 are installed on /target. The upgrade brings in snapd/snap-confine 2.23.1 which has a conffile in /etc/apparmor.d/usr.lib.snapd.snap-confine. The snapd packages declares a breaks/replaces: snapd-confine (<< 2.23) which works correctly on regular upgrades. However it does fail on upgrades with the "--root=/target" that is used by ubiquity. After a bit of debugging it turns out the reason is that src/archives.c:tarobject() has a check for obsolete conffiles in the block around "Is the file an obsolete conffile ...". There is a stat() here that checks that the conff->name and the fnamevb are the same file. This check fails to take the instdir into account and therefore the loop does not continue but falls through to the "does_replace()" checks. Snap 2.23.1 fails to upgrade from 2.21. Known facts: - reporters (and apport) indicate it fails during the install via the live-cd - not reproducible so far on an already installed system - breaks/replaces of snapd are correct - When adding "xenial-proposed" to apt-setup in ubiquity and installing Cause: - when ubiquity runs it uses "dpkg --root=/target --unpack ..." - however when doing the conffile checking dpkg does not handle the "--root" parameter correctly and checks something against "/" instead of "/target". - I really don't know what else to add... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: snapd 2.23.1 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CasperVersion: 1.376.2 Date: Wed Mar 15 16:03:33 2017 DuplicateSignature: package:snapd:2.23.1 Unpacking snapd (2.23.1) over (2.21) ... dpkg: error processing archive /target/var/cache/apt/archives/snapd_2.23.1_amd64.deb (--unpack): trying to overwrite '/etc/apparmor.d/usr.lib.snapd.snap-confine', which is also in package snap-confine 2.23.1 ErrorMessage: trying to overwrite '/etc/apparmor.d/usr.lib.snapd.snap-confine', which is also in package snap-confine 2.23.1 LiveMediaBuild: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: snapd Title: package snapd 2.23.1 failed to install/upgrade: trying to overwrite '/etc/apparmor.d/usr.lib.snapd.snap-confine', which is also in package snap-confine 2.23.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1673247/+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 1849042] Re: xenial/linux-kvm: 4.4.0-1061.68 -proposed tracker
4.4.0-1060.67 - kvm Regression test CMPL, RTB. Issue to note in amd64: ubuntu_ecryptfs - miscdev-bad-count.sh and lp-994247 on 5 filesystems (bug 1837523) ubuntu_kernel_selftests - psock_tpacket in net failed (bug 1812176) test_bpf in net (bug 1812189) test_user_copy return code in user (bug 1812352) ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) debug (bug 1821906) memory (bug 1845687) port80 (bug 1748105) vmx (bug 1821394) vmx_apic_passthrough_thread (bug 1822309) vmx_hlt_with_rvi_test (bug 1822308) ubuntu_ltp_syscalls - fallocate04, fallocate05, fdatasync03, fremovexattr01, fremovexattr02, fsync01, fsync04, msync04, preadv03, preadv03_64, preadv203, preadv203_64, pwritev03, pwritev03_64, sync03, syncfs01, sync_file_range02, copy_file_range01 (bug 1842270) fsetxattr01, fgetxattr01, fanotify13, fanotify14, lremovexattr01, setxattr01 (bug 1842270) fanotify06 (bug 1833028) fanotify10 (bug 1802454) quotactl02 / quotactl03 (bug 1848698) msgstress03 (bug 1783881) pkey01 failure cannot be reproduced ubuntu_lxc - ERROR: Unable to fetch GPG key from keyserver. proxy issue for Intel Cloud (bug 1838966) xfstests - no scratch drive available for the test Skipped / blacklisted: * ubuntu_blktrace_smoke_test * ubuntu_bpf * ubuntu_fan_smoke_test * ubuntu_ftrace_smoke_test * ubuntu_ltp * ubuntu_lttng_smoke_test * ubuntu_seccomp * ubuntu_sysdig_smoke_test ** 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/1849042 Title: xenial/linux-kvm: 4.4.0-1061.68 -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: 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 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-kvm package in Ubuntu: Invalid Status in linux-kvm 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: 1849051 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Tuesday, 22. October 2019 15:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849042/+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 1849051] Re: xenial/linux: 4.4.0-167.196 -proposed tracker
4.4.0-167.196 - generic Regression test CMPL, RTB. Issue to note in amd64: ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) debug (bug 1821906) ubuntu_ltp_syscalls - fallocate04, fallocate05, fdatasync03, fremovexattr01, fremovexattr02, fsync01, fsync04, msync04, preadv03, preadv03_64, preadv203, preadv203_64, pwritev03, pwritev03_64, sync03, syncfs01, sync_file_range02, copy_file_range01 (bug 1842270) fanotify06 (bug 1833028) fanotify10 (bug 1802454) fsetxattr01, fgetxattr01, fanotify13, fanotify14, lremovexattr01, setxattr01 (bug 1842270) ubuntu_xfstests_btrfs - btrfs/187 time out ubuntu_xfstests_xfs - generic/438 time out 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) gicv2 related test failed on ThunderX (bug 1828153) pmu on starmie (bug 1751000) ubuntu_ltp_syscalls - fallocate04, fallocate05, fdatasync03, fremovexattr01, fremovexattr02, fsync01, fsync04, msync04, preadv03, preadv03_64, preadv203, preadv203_64, pwritev03, pwritev03_64, sync03, syncfs01, sync_file_range02, copy_file_range01 (bug 1842270) fanotify06 (bug 1833028) fanotify10 (bug 1802454) fsetxattr01, fgetxattr01, fanotify13, fanotify14, lremovexattr01, setxattr01 (bug 1842270) 50 / 53 tests were run, missing: ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, ubuntu_xfstests_xfs Issue to note in i386: ubuntu_kvm_unit_tests - unable to build on X/T i386 (bug 1798007) ubuntu_ltp_syscalls - fallocate04, fallocate05, fdatasync03, fremovexattr01, fremovexattr02, fsync01, fsync04, msync04, preadv03, preadv03_64, preadv203, preadv203_64, pwritev03, pwritev03_64, sync03, syncfs01, sync_file_range02, copy_file_range01 (bug 1842270) fanotify06 (bug 1833028) fanotify10 (bug 1802454) fsetxattr01, fgetxattr01, fanotify13, fanotify14, lremovexattr01, setxattr01 (bug 1842270) 53 / 54 tests were run, missing: 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_ltp_syscalls - fallocate04, fallocate05, fsetxattr01, fdatasync03, fgetxattr01, fremovexattr01, fremovexattr02, fsync01, fsync04, fanotify13, fanotify14, fanotify15, lremovexattr01, msync04, preadv03, preadv03_64, preadv203, preadv203_64, pwritev03, pwritev03_64, setxattr01, sync03, syncfs01, sync_file_range02, copy_file_range01 (bug 1842270) fanotify06 (bug 1833028) fanotify10 (bug 1802454) move_pages12 (bug 1831043) ubuntu_xfstests_btrfs - btrfs/187 time out 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 - fallocate04, fallocate05, fdatasync03, fremovexattr01, fremovexattr02, fsync01, fsync04, msync04, preadv03, preadv03_64, preadv203, preadv203_64, pwritev03, pwritev03_64, sync03, syncfs01, sync_file_range02, copy_file_range01 (bug 1842270) fanotify06 (bug 1833028) fanotify10 (bug 1802454) fsetxattr01, fgetxattr01, fanotify13, fanotify14, lremovexattr01, setxattr01 (bug 1842270) 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 issue (bug 1729854) ubuntu_ltp_syscalls - fallocate04, fallocate05, fdatasync03, fremovexattr01, fremovexattr02, fsync01, fsync04, msync04, preadv03, preadv03_64, preadv203, preadv203_64, pwritev03, pwritev03_64, sync03, syncfs01, sync_file_range02, copy_file_range01 (bug 1842270) fanotify06 (bug 1833028) fanotify10 (bug 1802454) fsetxattr01, fgetxattr01, fanotify13, fanotify14, lremovexattr01, setxattr01 (bug 1842270) Issue to note in s390x (zVM): 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 - skey failed on zVM (bug 1778705) ubuntu_ltp_syscalls - fallocate04, fallocate05, fdatasync03, fremovexattr01, fremovexattr02, fsync01, fsync04, msync04, preadv03, preadv03_64, preadv203, preadv203_64, pwritev03, pwritev03_64,
