Tarball of a source package with a fix for this issue:
bcache-tools_1.0.8.orig.tar.gz
bcache-tools_1.0.8-4ubuntu1_amd64.build
bcache-tools_1.0.8-4ubuntu1_amd64.buildinfo
bcache-tools_1.0.8-4ubuntu1_amd64.changes
bcache-tools_1.0.8-4ubuntu1_amd64.deb
bcache-tools_1.0.8-4ubuntu1.debian.tar.xz
bcache
Updated test to be a bit more resilient.
** Attachment added: "test-bcache-byuuid-links-fixed.sh"
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1861941/+attachment/5375723/+files/test-bcache-byuuid-links-fixed.sh
--
You received this bug notification because you are a member of
systemd debdiff with a fix to skip creating /dev/disk/by-uuid for bcache
backing, caching devices.
** Patch added: "lp1861941-skip-bcache-links.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+attachment/5375730/+files/lp1861941-skip-bcache-links.debdiff
--
You r
** Attachment added: "curtin vmtest logs for ipv6 mtu verification"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1671951/+attachment/5325665/+files/bug-1671951-curtin-vmtest-verification.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pac
Curtin vmtest verification for bionic using systemd from -proposed has
run successfully.
(neipa) ipv6_mtu % egrep "237-3ubuntu10.34"
output/BionicTestNetworkMtu/logs/install-serial.log
[ 126.923480] cloud-init[1176]: Get:10 http://archive.ubuntu.com/ubuntu
bionic-proposed/main amd64 libsystemd
Curtin vmtest verification for eoan using systemd from -proposed has run
successfully.
(neipa) ipv6_mtu % egrep "242-7ubuntu3.3"
output/EoanTestNetworkMtu/logs/install-serial.log
[ 136.520219] cloud-init[765]: Get:12 http://archive.ubuntu.com/ubuntu
eoan-proposed/main amd64 libnss-systemd amd64
** Attachment added: "curtin vmtest logs for vlan mtu issue"
https://bugs.launchpad.net/curtin/+bug/1846232/+attachment/5325684/+files/bug-1846232-curtin-vmtest-verification.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscri
Eoan vmtests for vlan MTU checks now pass:
(neipa) vlan-mtu % egrep "242-7ubuntu3.3"
output/EoanTestNetworkVlan/logs/install-serial.log
[ 131.271209] cloud-init[765]: Get:12 http://archive.ubuntu.com/ubuntu
eoan-proposed/main amd64 libnss-systemd amd64 242-7ubuntu3.3 [126 kB]
[ 131.281683] cl
Cloud-init service starts and will run growpart, etc
Feb 06 00:37:26 ubuntu systemd[1]: Starting Initial cloud-init job
(pre-networking)...
Feb 06 00:37:37 test-xrdpdnvfctsofyygmzan systemd[1]: Starting Initial
cloud-init job (metadata service crawler)...
Something has modified sdb1 (growpart/s
Verified VLANs on Eoan using systemd 242-7ubuntu3.7 from -proposed
correctly set the MTU to 1500 when specified in the netplan config.
** Attachment added: "curtin vmtest logs for vlan mtu verification"
https://bugs.launchpad.net/curtin/+bug/1846232/+attachment/5326388/+files/bug-1846232-curt
Verified Eoan systemd 242-7ubuntu3.7 correctly sets IPv6 MTU
Verified Bionic systemd 237-3ubuntu10.39 correctly sets IPv6 MTU
** Attachment added: "curtin vmtest logs for ipv6 mtu verification"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1671951/+attachment/5326389/+files/bug-167195
Yes, this is my read on the issue as well. The trigger is related to
the inotify watch that systemd-udevd puts on the disk. Something that
might help that we could try per xnox's comment around use of flock.
if growpart were to flock /dev/sda (we need to sort out what flags are
needed to prevent
** Also affects: util-linux (Ubuntu)
Importance: Undecided
Status: New
** Tags added: rls-ff-incoming
** Also affects: util-linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: curtin (Ubuntu Focal)
Importance: High
Status: Triaged
** Also affect
@Lee Thanks for tracking down the util-linux bug.
Since this is broken in 2.34 (eoan/focal); I'm thinking we should use
sysfs to find the parent via device name walking;
Given a kname (nvme0n1p1) of the target partition
# look up sysfs path from kname
% realpath /sys/class/block/nvme0n1p1
/sys/
@Alberto
> I thought the installer would work similarly to what the desktop installer
> does with btrfs, where it creates subvolumes for / and /home in the root
> partition (as @ and @home).
>
> On my desktop, when I upgrade I just move @ out of the way (by renaming it)
> and the installer crea
** Merge proposal linked:
https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/379024
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1862846
Title:
Crash a
** Changed in: curtin (Ubuntu Focal)
Status: Triaged => In Progress
** Changed in: curtin (Ubuntu Focal)
Assignee: (unassigned) => Ryan Harper (raharper)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util
Here's the upstream changes to growpart I'm suggesting:
https://code.launchpad.net/~raharper/cloud-utils/+git/cloud-
utils/+merge/379177
I've also proposed on modifications to cloud-init's cc_growpart as a further
method
to aid debugging if this hit as well as some mitigation around the race.
h
@Scott,
cloud-utils isn't quite new-upstream-snapshot out of the box; the debian
dir does not contain the changelog; however, I think I've got this
sorted out. I've a MP I can put up; but it only will show the add of
the changelog file. I'll attach a debdiff and a source package.
--
You recei
** Patch added: "debdiff showing the changes to upload to fix the bug."
https://bugs.launchpad.net/cloud-init/+bug/1834875/+attachment/5330894/+files/cloud-utils_0.31-6_to_0.31-7.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is s
** Attachment added: "tarball of source package to upload"
https://bugs.launchpad.net/cloud-init/+bug/1834875/+attachment/5330895/+files/cloud-utils_0.31-7-gd99b2d76-source.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscrib
On Tue, Feb 25, 2020 at 2:35 PM Scott Moser
wrote:
> this seemed to "just work" for me.
> http://paste.ubuntu.com/p/93dWDPZfZT/
Ah, I didn't check that there was an existing ubuntu/devel branch. Sorry.
I've pushed a MR here:
https://code.launchpad.net/~raharper/cloud-utils/+git/cloud-utils/
** Also affects: ifupdown (Ubuntu)
Importance: Undecided
Status: New
** Tags added: uec-images
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1867029
Title:
Pa
Probert PR to drop --mknodes:
https://github.com/canonical/probert/pull/88
Curtin MP to drop --mknodes
https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/383141
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
I built a new UC16 image with the systemd proposed package. Initially
networkd running early is fine. However, under closer inspection, in a
networkd-only image, DNS (resolvconf) was not running early enough to
allow DNS service to be available at the time that cloud-init.service
runs (which may
I've tested Before=network-pre.target; that works fine. However, for
the networkd case, systemd-networkd-wait-online.target should ensure
that systemd-networkd-resolvconf-update.service has run first otherwise
there might a window where interfaces are configured, but DNS is not.
The following cha
Adding xenial debdiff for resolvconf changes.
** Patch added: "xenial_resolvconf-lp1636912.debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1636912/+attachment/4788512/+files/xenial_resolvconf-lp1636912.debdiff
--
You received this bug notification because you are a member of
Adding yakkety debdiff for resolvconf changes.
** Patch added: "yakkety_resolvconf-lp1636912.debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1636912/+attachment/4788513/+files/yakkety_resolvconf-lp1636912.debdiff
--
You received this bug notification because you are a member
Add a Wants=network-pre.target for resolvconf
** Patch added: "yakkety_resolvconf-lp1636912-v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1636912/+attachment/4788949/+files/yakkety_resolvconf-lp1636912-v2.debdiff
--
You received this bug notification because you are a me
Testing in debian shows that to use network-pre.target, resolvconf needs
to include a Wants=network-pre.target to ensure that it gets pulled in
as a unit. I'm attaching updated debdiffs for xenial and yakkety.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Add a Wants=network-pre.target to resolvconf service.
** Patch added: "xenial_resolvconf-lp1636912-v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1636912/+attachment/4788950/+files/xenial_resolvconf-lp1636912-v2.debdiff
--
You received this bug notification because you ar
Filed in Debian (resolvconf) https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=847440
** Bug watch added: Debian Bug tracker #847440
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847440
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which i
On Tue, Dec 13, 2016 at 10:02 AM, Martin Pitt
wrote:
> Ryan Harper [2016-12-06 12:54 -]:
> > The following change should go against systemd-networkd-wait-
> > online.service
> >
> > + # Ensure that DNS is working before reaching online target
> > +
Public bug reported:
Currently resolvconf and systemd-networkd don't ensure DNS has been
configured before allowing network-online.target to be reached.
This was discussed in https://launchpad.net/bugs/1636912 however it was
not a regression since there aren't any users of networkd + DNS early in
I've opened a new bug for the DNS networkd/resolvconf issue:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1649931
We'll track a new SRU for fixing that issue separately.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscri
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1636912
Title:
systemd-networkd runs too late for clou
** Patch added: "xenial_resolvconf-lp1649931.diff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1649931/+attachment/4792030/+files/xenial_resolvconf-lp1649931.diff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Description changed:
Currently resolvconf and systemd-networkd don't ensure DNS has been
configured before allowing network-online.target to be reached.
This was discussed in https://launchpad.net/bugs/1636912 however it was
not a regression since there aren't any users of networkd +
** Patch added: "xenial-dns-before-online-target-lp1649931.debdiff"
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1649931/+attachment/4792126/+files/xenial-dns-before-online-target-lp1649931.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch see
On Thu, Dec 15, 2016 at 10:27 PM, Brian Murray wrote:
> How is this fixed in the development release?
>
For systemd portion, we carry the
systemd-networkd-resolvconf-update.service as a delta from Debian
Ryan
--
You received this bug notification because you are a member of Ubuntu
Touch seede
On Thu, Dec 15, 2016 at 10:27 PM, Brian Murray wrote:
> How is this fixed in the development release?
>
There is an upstream resolvconf bug that addresses that package portion:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847440
> Also the having a "Regression Potential" of low just bec
** Bug watch added: Debian Bug tracker #847440
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847440
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1649931
Title:
Public bug reported:
Ubuntu Core 16 images using cloud-init fail to function when the
DataSource is over the network (Like OpenStack) as networking is not yet
available when cloud-init.service runs.
cloud-init service unit deps look like this:
[Unit]
Description=Initial cloud-init job (metadata
On Wed, Oct 26, 2016 at 6:41 PM, Steve Langasek <
steve.langa...@canonical.com> wrote:
> Note that the systemd dependencies shown for cloud-init in xenial (on
> which Ubuntu Core 16 is based) don't match those listed in the bug
> description. Instead, xenial currently has:
>
> After=cloud-init-lo
On Thu, Oct 27, 2016 at 5:59 AM, Martin Pitt
wrote:
> So did I understand this right:
>
> * In current xenial, cloud-init runs in late boot, so there is no
> principal ordering problem between cloud-init and networkd, other than
> that cloud-init.service should declare After=systemd-networkd.ser
On Thu, Oct 27, 2016 at 8:43 AM, Ryan Harper
wrote:
>
>
> On Thu, Oct 27, 2016 at 5:59 AM, Martin Pitt
> wrote:
>
>> So did I understand this right:
>>
>> * In current xenial, cloud-init runs in late boot, so there is no
>> principal ordering problem betw
networkd bringing up eth0 (virtio) on qemu user-net is taking like 40
seconds... why?
root@localhost:~# journalctl --unit systemd-networkd.service | egrep
"(Started|Configured)"
Oct 27 16:31:59 localhost.localdomain systemd[1]: Started Network Service.
Oct 27 16:32:32 localhost.localdomain system
It appears that the networkd in Xenial is sensitive to dbus service
being available; it times out a bit waiting for dbus before continuing;
this is the delay.
If I drop cloud-init.service 'Before=dbus.socket' and
'Before=basic.target'; Add 'After=systemd-networkd-wait-online.service';
then ensure
Oct 27 19:22:27 localhost.localdomain systemd[1]: writable.mount: Unit is bound
to inactive unit dev-vda3.device. Stopping, too.
Oct 27 19:22:27 localhost.localdomain systemd[1]: systemd-networkd.service:
Found ordering cycle on systemd-networkd.service/start
Oct 27 19:22:27 localhost.localdomain
On Thu, Oct 27, 2016 at 2:50 PM, Martin Pitt
wrote:
> > oddly though when using the ifupdown 'networking.service'; we don't
> need to use that target.
>
> Yes, that's a Type=oneshot, as it just calls "ifup -a". So that's more
> or less equivalent to s-n-wait-online --timeout=30 or After=s-n-wait-
On Thu, Oct 27, 2016 at 3:57 PM, Martin Pitt
wrote:
> > cloud-init expects networking to be up, like 'networking.service'
> before it runs..
>
>
> I think it needs to make up its mind -- why does it want to run
> Before=network-online.target then? I thought the idea was that cloud-init
> is able
On Thu, Oct 27, 2016 at 3:57 PM, Martin Pitt
wrote:
> > cloud-init expects networking to be up, like 'networking.service'
> before it runs..
>
>
> It seems to me that this might have to be split into two parts then -- one
> that can provide network config which runs early and does not require
> n
On Fri, Oct 28, 2016 at 1:02 PM, Martin Pitt
wrote:
> > However, if there isn't a local seed, then we must search again *once*
> networking is up.
>
> Fair enough, but you can then of course not use that unit to configure
> the network.
Of course we can. We need to cycle the network though.
curtin does not do any read-ahead configuration;
** Changed in: curtin
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ureadahead in Ubuntu.
https://bugs.launchpad.net/bugs/1643838
Title:
urea
** Changed in: ifupdown (Ubuntu)
Importance: Undecided => Medium
** Changed in: ifupdown (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.laun
Hi Dan,
Yes; I have a curtin modification and test-cases to handle all of our
scenarios.
https://code.launchpad.net/~raharper/curtin/trunk.more-ipv6
In particular, you can see the final scripts (a pre-hook and post is
needed)
http://bazaar.launchpad.net/~raharper/curtin/trunk.more-
ipv6/view/he
** Branch linked: lp:~raharper/curtin/trunk.more-ipv6
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1609367
Title:
ifupdown does not set ipv6-only large mtu
Status in i
Hi,
>From what I can tell, looking at the existing slapd apparmor profile, it
does not include access to the kcm socket in /run as you say. However,
I've yet to discover how to have slapd attempt to access this particular
socket.
I've examined a number of Kerberos + OpenLDAP setups and there's n
Tested:
a37843379dd7061c2c1dc87ed215a284 *xenial-server-amd64.iso
And selected "No Automatic updates" when prompted.
After install there is no longer a /etc/apt/apt.conf.d/20auto-upgrades
file present.
ubuntu@ubuntu:~$ cat /etc/apt/apt.conf.d/20auto-upgrades
cat: /etc/apt/apt.conf.d/20auto-upgr
Public bug reported:
This seems to happen regardless of wether or not the monitor is plugged
in - program crash upon login. Please advise.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: sudo 1.8.16-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-
** Patch added: "fix-bridge-port-settings.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1576858/+attachment/4665495/+files/fix-bridge-port-settings.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribe
Update manpage documentation.
** Patch added: "fix-bridge-port-settings-v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1576858/+attachment/4665565/+files/fix-bridge-port-settings-v2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touc
Do you have a specific guide or sequence you followed?
1. apt-get install slapd krb5* heimdal-kdc .. etc?
And then the various config changes applied?
I'll keep digging.
On Wed, Jul 20, 2016 at 11:31 AM, Kartik Subbarao
wrote:
> Hi Ryan,
>
> Thanks for looking into this. Unfortunately I don'
>From what I understand, systemd does not rename devices a second time:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1579130
So, it's possible that existing udev rules have already applied to the
device in question and your .link file is "too late".
This maybe a dupe of that; but provi
Can you explain which part fails?
"ifupdown fails to set the device's mtu, which causes its attempt to set
the ipv6 mtu to fail"
This is the change that drove the use of sysctl to set mtu:
https://anonscm.debian.org/git/collab-
maint/ifupdown.git/commit/?id=a1b2cfea935d91961dc2df3ac5cfe6668b
On Thu, Aug 4, 2016 at 5:21 PM, Dan Streetman <
dan.streetman+launch...@canonical.com> wrote:
> > In the original bug where one is comparing ip output of MTU; is there
> something *not* working ?
>
> in that original bug, the user is trying to set up ipv6 tunneling:
>
> "This scenario is quiet com
There also seems to be another bug for ipv6 only; the sysctl setting of
mtu happens before the ip link set dev up; which means, at up time, the
interface gets the default mtu which clobbers the ipv6 mtu.
/sbin/sysctl -q -e -w net.ipv6.conf.ens8.autoconf=0
/sbin/sysctl -q -e -w net.ipv6.conf.ens8.m
On Tue, Aug 9, 2016 at 12:56 PM, Dan Streetman <
dan.streetman+launch...@canonical.com> wrote:
> > I understand this scenario; however, what I don't understand is why
> > if we're setting mtu 9002 on the underlying devices, why the mtu on the
> > "virtual" device (bond0)
> > matters vs. the mtu se
** Description changed:
- Copying large (>10GB) files with rsync -z (compression) leads to a long
- hang and eventual error after transferring part of the file. The error
- is consistent. The file copies at normal speed until it reaches its
- maximum size (1.4 GB out of 20 GB for one, 6.9 GB out
Hi,
For now, you'll need to downgrade your libnl-3 packages:
% apt-get install libnl-3-200=3.2.21-1 libnl-genl-3-200=3.2.21-1 libnl-
route-3-200=3.2.21-1
And you may need to apply a hold until a fix for NetworkManager can be
released.
% sudo apt-mark hold libnl-3-200 libnl-genl-3-200 libnl-rout
** Description changed:
+ [Impact]
+
+ * NetworkManager depends on libnl (libnl-3-200 libnl-genl-3-200
+libnl-route-3-200) and when libnl is updated to proposed
+3.2.21-1ubuntu1 NM segfaults due to libnl exposing a bug in NM
+validation packets.
+
+This affects the 0.98 release
v2
- Add DEP3 header to patches
** Patch added: "nm_fix_updated_libnl_regression_v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1539634/+attachment/4562007/+files/nm_fix_updated_libnl_regression_v2.debdiff
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1539634 ***
https://bugs.launchpad.net/bugs/1539634
** This bug has been marked a duplicate of bug 1539634
network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Touch seede
I've run the 'Successful upgrade Test' steps from the SRU text
successfully. Verified working. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1539634
Title
This has not been released; this version is only available in trusty-
proposed. It's not been verified at this point.
** Changed in: libnl3 (Ubuntu Trusty)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded package
I've retagged this as verification-needed since we've had one regression
(NetworkManager, a bug there) and we'd like to request other users of
libnl to test out the version included in proposed so we can ensure
we're flushing out other applications that may be exposed due to the
behavior changed in
Correct. We pushed the nm fix so anyone using trusty-proposed would be
fixed but the libnl fix needs more time to test. Only users who have
trusty-proposed are affected and this fixes that while we do further
validation on libnl dependent applications for regressions.
On Feb 2, 2016 7:26 PM, "dyn
I've updated the debdiff to include a Breaks: network-manager (<<
0.9.8.8-0ubuntu7.3) to ensure that users are forced to use the newer
network-manager (ie, this libnl won't install unless user has already
updated their network-manager) Thanks Mathew for the suggestion.
I've built and tested thi
v3 debdiff
- Removed unneeded spaces in debian/control Breaks entry
- Fixed up libnl-3-200.symbols file to tag private symbols as optional
(removes dpkg-gensymbols warning)
- Removed invalid use of Closes() for Debian bugs; instead use LP: #
** Patch added: "lp_1511735_libnl3_v3.diff"
owpan-test-tools
lowpan-tools
neard
neard-tools
ntrack-module-libnl-0
plainbox-provider-resource-generic
sssd-common
wpasupplicant
** Changed in: libnl3 (Ubuntu Trusty)
Assignee: Ryan Harper (raharper) => (unassigned)
--
You received this bug notification because you are a member of
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1539634
Title:
network-manager crashes when us
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libnl3 in Ubuntu.
https://bugs.launchpad.net/bugs/1511735
Title:
libnl: fail to bind() netlink sockets
S
If you remove the eth1 manual stanza above, does it then work?
auto eth1
iface eth1 inet manual
mtu 1500
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1565804
Title:
Thank you for taking the time to report this bug and helping to make Ubuntu
better.
Unfortunately, we cannot work on this bug because your description didn't
include enough information.
Which Ubuntu release and ntp version you using?
1. lsb_release -dcr
2. apt-cache policy ntp
3. Any steps and
Attaching debdiff with changes needed to resolve the bug.
** Patch added: "lp_1511735_libnl3.diff"
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735/+attachment/4535780/+files/lp_1511735_libnl3.diff
--
You received this bug notification because you are a member of Ubuntu
Touch se
Tarball of the test-case used to confirm failure and fix.
** Attachment added: "lp_1511735_test.tar"
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735/+attachment/4535781/+files/lp_1511735_test.tar
** Description changed:
- The following upstream patches are needed in order to av
On Wed, Dec 16, 2015 at 11:29 AM, Nicolas Dichtel wrote:
> Thank you.
>
> Note that the last three patches are not included in libnl 3.2.26, which
> is the version of ubuntu 16.04 /Xenial (
> https://launchpad.net/ubuntu/+source/libnl3/3.2.26-1).
>
Thank you for mentioning this.
> Should I mak
Public bug reported:
Xenial amd64 VM running lvm2 commands returns this output:
various vgcreate/lvcreate returns this message:
allocation/use_blkid_wiping=1 configuration setting is set while LVM is not
compiled with blkid wiping support.
Falling back to native LVM signature detection.
Log
Public bug reported:
1.
% lsb_release -rd
Description:Ubuntu 16.04 LTS
Release:16.04
2. % apt-cache policy bridge-utils
bridge-utils:
Installed: 1.5-9ubuntu1
Candidate: 1.5-9ubuntu1
Version table:
*** 1.5-9ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu xenial/mai
Public bug reported:
1. % lsb_release -rd
Description:Ubuntu 16.04 LTS
Release:16.04
2. % apt-cache policy bridge-utils
bridge-utils:
Installed: 1.5-9ubuntu1
Candidate: 1.5-9ubuntu1
Version table:
*** 1.5-9ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main
Public bug reported:
1. % lsb_release -rd
Description:Ubuntu 16.04 LTS
Release:16.04
2. % apt-cache policy bridge-utils
bridge-utils:
Installed: 1.5-9ubuntu1
Candidate: 1.5-9ubuntu1
Version table:
*** 1.5-9ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main
Not sure why the proposed pocket didn't have the 1ubuntu2 that included
the breaks. When we encountered this, I asked that the 1ubuntu2 of
libnl3 be uploaded and staged such that everyone gets the libnl3 with
the Breaks n-m first.
** Patch added: "libnl3_breaks_nm.debdiff"
https://bugs.launch
Can you attach cloud-init*.log to the bug?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1569064
Title:
ifupdown wants to configure interfaces it shouldn't (lxdbr0)
Sta
Public bug reported:
1. % lsb_release -rd
Description:Ubuntu 16.04 LTS
Release:16.04
2. % apt-cache policy apparmor
apparmor:
Installed: 2.10.95-0ubuntu2
Candidate: 2.10.95-0ubuntu2
Version table:
*** 2.10.95-0ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu xenial
iscsid.service: Failed to read PID from file /run/iscsid.pid: Invalid
argument
When runnig iscsid -f -d7, we see the issue:
root@x1:~# iscsid -f -d 7
iscsid: sysfs_init: sysfs_path='/sys'
iscsid: InitiatorName=iqn.1993-08.org.debian:01:32a765bb043
iscsid: InitiatorName=iqn.1993-08.org.debian:01
Actually, ooms are non-fatal, but the mlockall is.
strace shows:
[pid 521] mlockall(MCL_CURRENT|MCL_FUTURE
[pid 522] <... getdents resumed> /* 2 entries */, 32768) = 48
[pid 522] getdents(5, /* 0 entries */, 32768) = 0
[pid 522] close(5)= 0
[pid 522] exit_group(0)
Unpriv containers don't have CAP_IPC_LOCK at this time; we need to
determine if that's requirement , or if it's actually non-fatal.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bug
Possibly related to ifupdown since:
$ dpkg -S /etc/network/if-up.d/upstart
ifupdown: /etc/network/if-up.d/upstart
** Project changed: curtin => ifupdown (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in
If anyone wants to reproduce:
1. uvt-simplestreams-libvirt sync release=trusty arch=amd64
2. uvt-kvm create --memory 1024 --cpu 2 --disk 10 t1 release=trusty
3. uvt-kvm wait --insecure t1
4. uvt-kvm ssh --insecure t1
# inside t1 vm
5. edit /etc/network/interfaces to look like:
auto eth0
iface et
It's definitely not the fix we want. Here's what's happening (after discussing
with smoser).
Each of the physical devices are brough up via ifup, and all semephor on
/run/networking/ looking for ifup.eth0, ifup.eth1 and ifup.eth1:1.
The first two files are written when /etc/init/network-interfa
201 - 300 of 321 matches
Mail list logo
