[Bug 1791710] [NEW] tar 1.29b-2 breaks pristine-tar
Public bug reported:
Steps to reproduce:
docker run -ti ubuntu:18.04 /bin/bash
apt-get update
apt-get install git build-essential tar pristine-tar
git clone git://git.launchpad.net/~ubuntu-server-dev/ubuntu/+source/neutron
cd neutron/
for i in `git branch -a | grep remote | grep -v HEAD | grep -v master`; do git
branch --track ${i#remotes/origin/} $i; done
# this command will fail
pristine-tar -v checkout neutron_10.0.7.orig.tar.gz
# to fix it update tar
apt-get install wget && wget
http://mirrors.kernel.org/ubuntu/pool/main/t/tar/tar_1.30+dfsg-2_amd64.deb
apt-get install ./tar_1.30+dfsg-2_amd64.deb
# now it works
pristine-tar -v checkout neutron_10.0.7.orig.tar.gz
** Affects: pristine-tar (Ubuntu)
Importance: Undecided
Status: New
** Affects: tar (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791710
Title:
tar 1.29b-2 breaks pristine-tar
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pristine-tar/+bug/1791710/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738219] Re: the kernel is blackholing IPv6 packets to linkdown nexthops
** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738219 Title: the kernel is blackholing IPv6 packets to linkdown nexthops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738219] Re: the kernel is blackholing IPv6 packets to linkdown nexthops
I tested the proposed Kernel in Xenial and it is working for me -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738219 Title: the kernel is blackholing IPv6 packets to linkdown nexthops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742630] Re: Booting from 4.13 leads to Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci]
I have the kernel running and I confirm that it resolved the bug Linux s0008 4.13.0-25-generic #29~lp1742630 SMP Thu Jan 11 18:42:42 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux thank you -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742630 Title: Booting from 4.13 leads to Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci] To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1742630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742630] Re: Booting from 4.13.0-21-generic leads to Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci]
I have tested this version linux-image-generic-hwe-16.04 4.13.0.26.46 It does not work for me ** Summary changed: - Booting from 4.13.0-21-generic leads to Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci] + PTI Kernels: Booting from 4.13.0-21-generic leads to Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci] ** Summary changed: - PTI Kernels: Booting from 4.13.0-21-generic leads to Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci] + PTI Kernels: Booting from 4.13 leads to Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742630 Title: PTI Kernels: Booting from 4.13 leads to Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742630] Re: Booting from 4.13.0-21-generic leads to Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci]
The Kernel does not boot at all, so it is not possible to collect the data with apport-collect ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742630 Title: Booting from 4.13.0-21-generic leads to Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742630] [NEW] Booting from 4.13.0-21-generic leads to Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci]
Public bug reported: I cannot boot from 4.13.0-21-generic Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci] This Kernel bug was already fixed in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882414 Relevant discussion: https://marc.info/?l=linux-scsi=151523964725984=2 Ubuntu needs to fix this, because otherwise _many_ people will complain about crashes when they upgrade from 4.9 (or 4.4) to 4.13, which Ubuntu defined as their new “HWE” kernel. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Description changed: I cannot boot from 4.13.0-21-generic + + Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 + [isci] This Kernel bug was already fixed in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882414 Relevant discussion: https://marc.info/?l=linux-scsi=151523964725984=2 Ubuntu needs to fix this, because otherwise _many_ people will complain about crashes when they upgrade from 4.9 (or 4.4) to 4.13, which Ubuntu defined as their new “HWE” kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742630 Title: Booting from 4.13.0-21-generic leads to Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738219] Re: the kernel is blackholing IPv6 packets to linkdown nexthops
I tested the packages on Xenial: ; uname -a Linux s0006 4.4.0-103-generic #126~lp1738219 SMP Thu Dec 14 16:37:03 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux It LGTM. The bug is fixed when using this kernel. thank you -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738219 Title: the kernel is blackholing IPv6 packets to linkdown nexthops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738219] Re: the kernel is blackholing IPv6 packets to linkdown nexthops
I tested now with Kernel 4.4.0-103-generic + the patch from commit bbfcd7 and it works for me https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bbfcd77631573ac4a9f57eb6169e04256a111bc1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738219 Title: the kernel is blackholing IPv6 packets to linkdown nexthops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738219] Re: the kernel is blackholing IPv6 packets to linkdown nexthops
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738219 Title: the kernel is blackholing IPv6 packets to linkdown nexthops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738219] [NEW] the kernel is blackholing IPv6 packets to linkdown nexthops
Public bug reported:
When the 'ignore_routes_with_linkdown' sysctl is set, we should not
consider linkdown nexthops during route lookup.
While the code correctly verifies that the initially selected route
('match') has a carrier, it does not perform the same check in the
subsequent multipath selection, resulting in a potential packet loss.
In case the chosen route does not have a carrier and the sysctl is set,
choose the initially selected route.
Fixed in the upstream kernel with patch:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bbfcd77631573ac4a9f57eb6169e04256a111bc1
I think this patch must be backported to stable kernel in Xenial. I
tested in patching the Ubuntu Xenial 4.4.0-21-generic and it works for
me.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Affects: linux-lts-xenial (Ubuntu)
Importance: Undecided
Status: New
** Tags: xenial
** Also affects: linux-lts-xenial (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1738219
Title:
the kernel is blackholing IPv6 packets to linkdown nexthops
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738219/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705447] Re: misleading kernel warning skb_warn_bad_offload during checksum calculation
Hello, I still se this issue on Xenial with Kernel 4.4.0-93-generic #116-Ubuntu The server is bare-metal. It is just a cosmetic problem in the log files or I should upgrade as soon as possible ? I noticed the bad entries in my kern.log with my monitoring tool, but I dont see any side effect so far. Could anyone please clarify what is the operational impact of this bug ? thanks ! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705447 Title: misleading kernel warning skb_warn_bad_offload during checksum calculation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1706875] [NEW] libvirt's apparmor profile denies access to /tmp and snapshots failed
Public bug reported: Using Ubuntu Trusty and libvirt package 1.3.1-1ubuntu10.9~cloud0 libvirt-bin: Installed: 1.3.1-1ubuntu10.9~cloud0 Candidate: 1.3.1-1ubuntu10.9~cloud0 Version table: *** 1.3.1-1ubuntu10.9~cloud0 0 500 http://ubuntu-cloud.archive.canonical.com/ubuntu/ trusty-updates/mitaka/main amd64 Packages This is in Openstack installation. When trying to snapshot a instance I see the following in libvirt.log 2017-07-26 09:27:12.129+: 46621: warning : AppArmorSetFDLabel:982 : could not find path for descriptor /proc/self/fd/38, skipping 2017-07-26 09:27:12.131+: 46621: error : qemuMonitorJSONCheckError:382 : internal error: unable to execute QEMU command 'migrate': Migration disabled: failed to allocate shared memory In nova-compute.log I see: 2017-07-26 11:27:13.038 171589 ERROR oslo_messaging.rpc.dispatcher libvirtError: internal error: unable to execute QEMU command 'migrate': Migration disabled: failed to allocate shared memory I apply this patch to /etc/apparmor.dabstractions/libvirt-qemu and everything works: https://review.fuel-infra.org/#/c/28086/2/debian/apparmor/libvirt-qemu ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1706875 Title: libvirt's apparmor profile denies access to /tmp and snapshots failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1706875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1559072] Re: [SRU] exceptions.from_response with webob 1.6.0 results in "AttributeError: 'unicode' object has no attribute 'get'"
** Tags removed: verification-newton-needed ** Tags added: verification-newton-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1559072 Title: [SRU] exceptions.from_response with webob 1.6.0 results in "AttributeError: 'unicode' object has no attribute 'get'" To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1559072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1559072] Re: [SRU] exceptions.from_response with webob 1.6.0 results in "AttributeError: 'unicode' object has no attribute 'get'"
I tested the package on Newton. It LGTM. Thank you -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1559072 Title: [SRU] exceptions.from_response with webob 1.6.0 results in "AttributeError: 'unicode' object has no attribute 'get'" To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1559072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1583009] Re: Error starting domain since update
I confirm the workaround on commment 14 worked also for me. I had this bug after upgrading from Trusty to Xenial using Openstack Mitaka. You can see the problem in nova-compute.log For Openstack this is very nasty bug because everything will fail to be scheduled on that compute-node, but the neutron port will not be cleaned up. So when finally the instance will be spawned on another compute node, it will come up with two neutron ports and two IP addresses. ** Also affects: cloud-archive Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1583009 Title: Error starting domain since update To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1583009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570472] Re: Set systemd as default service provider
Hello Nish, what is the workflow for Xenial ? are we going to see new puppet packages in Xenial Proposed repo soon ? thank you -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570472 Title: Set systemd as default service provider To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1570472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570472] Re: Set systemd as default service provider
I tested the PPA from Nish Aravamudan https://launchpad.net/~nacc/+archive/ubuntu/lp1570472 It fixes the problem for me. Any chance to have this merged to the official packages ? Saverio -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570472 Title: Set systemd as default service provider To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1570472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1660634] [NEW] Enable CONFIG_NET_DROP_MONITOR=m in Ubuntu Kernel
Public bug reported: CONFIG_NET_DROP_MONITOR=m is needed for the dropwatch software. At the moment dropwatch is packaged only for Fedora: https://fedorahosted.org/dropwatch/ The kernel compiled with CONFIG_NET_DROP_MONITOR=n makes not possible to use this software. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Tim Gardner (timg-tpi) Status: Fix Committed ** Affects: linux (Ubuntu Trusty) Importance: Undecided Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux (Ubuntu Xenial) Importance: Undecided Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux (Ubuntu Yakkety) Importance: Undecided Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux (Ubuntu Zesty) Importance: Undecided Assignee: Tim Gardner (timg-tpi) Status: Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1660634 Title: Enable CONFIG_NET_DROP_MONITOR=m in Ubuntu Kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570631] Re: With hw:vif_multiqueue_enabled, libvirt driver fails with VM larger than 8 vCPU
The patch does not solve the problem for me. nova has to check the qemu version in addition to the kernel version and set its limit accordingly In the version I am using of qemu (Ubuntu Liberty UCA) I have: VIRTIO_PCI_QUEUE_MAX == 64 This leads to 31 max queues: (VIRTIO_PCI_QUEUE_MAX - 1) / 2 It is not just the Kernel version Please read also bug #1644839 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570631 Title: With hw:vif_multiqueue_enabled, libvirt driver fails with VM larger than 8 vCPU To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1570631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598575] [NEW] easy_install crash with KeyError
Public bug reported: There's a problem in setuptools 24.0.0 (released today). You can reproduce it just running on the shell easy_install: # easy_install Traceback (most recent call last): File "/usr/local/bin/easy_install", line 7, in from setuptools.command.easy_install import main File "/usr/local/lib/python2.7/dist-packages/setuptools/__init__.py", line 14, in from setuptools.extension import Extension File "/usr/local/lib/python2.7/dist-packages/setuptools/extension.py", line 11, in from . import msvc File "/usr/local/lib/python2.7/dist-packages/setuptools/msvc.py", line 244, in class PlatformInfo: File "/usr/local/lib/python2.7/dist-packages/setuptools/msvc.py", line 253, in PlatformInfo current_cpu = safe_env['processor_architecture'].lower() File "/usr/lib/python2.7/UserDict.py", line 23, in __getitem__ raise KeyError(key) KeyError: 'processor_architecture' ** Affects: python-setuptools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598575 Title: easy_install crash with KeyError To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1598575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1558166] Re: Xenial installer hangs for a long time with "Setting up the clock" message on IPv6-only systems
I confirm. I noticed that opening an alternate shell and giving commands will unlock immediately the operation. Even if it makes no sense I can reproduce it. The installation is blocked at "getting the time from a network time server " and typing return on the cancel button has no effect. I do CTRL+ALT+F2. I click enter to activate a new console. As soon as I type a command there like "ps" or "ls" the installation immediately continues on the F1 console. Note that my system is dual stack IPv4 and IPv6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1558166 Title: Xenial installer hangs for a long time with "Setting up the clock" message on IPv6-only systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1558166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
