** Description changed:
- It was brought to my attention (by others) that ifupdown runs into race
- conditions on some specific cases.
-
- [Impact]
-
- When trying to deploy many servers at once (higher chances of happening)
- or from time-to-time, like any other intermittent race-condition.
-
CORRECT WAY OF SETTING INTERFACES FILE FOR BONDING:
1) This model has race conditions.
2) YOU HAVE to have both scripts running (networking and network-interfaces)
# /etc/network/interfaces
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
auto eth1
iface eth1 inet manual
I have introduced one big lock for ifupdown. The ifup, ifdown or ifquery
commands cannot be run simultaneously.
Since SEVERAL ifupdown pre/post scripts do need to make reentrant calls
do these commands I created on environment variable that disabled the
locking when reentrant calls are made to
Let's try everything again from the beggining but now with a fixed
ifupdown version (no race conditions between upstart and sysv scripts
). My interfaces file will be exactly the same as the one proposed for
ifenslave examples:
---
auto eth1
iface eth1 inet manual
bond-master bond0
auto eth2
And you can check that upstart got deadlocked:
---
root@provisioned:~# ps -ef | grep ifup
root 618 1 0 10:21 ?00:00:00 ifup --allow auto eth2
root 619 1 0 10:21 ?00:00:00 ifup --allow auto eth1
root 620 1 0 10:21 ?00:00:00 ifup --allow auto
YES!
---
root@provisioned:~# pstree -a
...
├─ifup --allow auto eth2
│ └─sh -c run-parts /etc/network/if-pre-up.d
│ └─run-parts /etc/network/if-pre-up.d
│ └─ifenslave /etc/network/if-pre-up.d/ifenslave
│ └─sleep 0.1
---
One slave interface, eth2 in this case, got
Checking Ubuntu bzr tree...
---
inaddy@trusty.00064811:/bugs/00064811/sources/bazaar/ubuntu/$ git clone
bzr::lp:ubuntu/ifenslave
Cloning into 'ifenslave'...
Most recent Ubuntu version: 3
Packaging branch version: 2.5ubuntu1
Packaging branch status: OUT-OF-DATE
Most recent Ubuntu version: 3
After talking to Stéphane Graber, from Ubuntu Core Foundations Team, we
decided that I should implement independent locking for every interface
(like I have already proposed to Debian upstream project) and to
implement locking mechanisms for dependent interfaces inside the hooks.
So:
1) ifupdown
This bug is being fixed upstream together with the developer. I'll
provide the fix here as soon as it gets accepted upstream:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753755
Thank you.
** Patch removed: ifupdown_0.7.47.2ubuntu4.2~lp1337873.diff
Im getting back to this after sometime. After the discussion was brought
to upstream we did not get feedback regarding proposed changes but
investigating further it is clear that ifupdown is suffering from race
conditions that cannot be solved simply by creating:
1) big lock - since its
** Changed in: isc-dhcp (Ubuntu)
Assignee: (unassigned) = Rafael David Tinoco (inaddy)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1401141
Title:
IPoIB does
Tks Mathieu,
Description was made based on a fast look into what was needed.
Thank you very much for your comment. I'll work on that as soon as I get some
free time.
Feel free to provide any other comment that might be useful to this.
--
You received this bug notification because you are a
** Changed in: isc-dhcp (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1401141
Title:
IPoIB does not work on Ubuntu due to DHCP
** Summary changed:
- IPoIB does not work on Ubuntu due to DHCP
+ DHCP server does not work for IPoIB (Infiniband)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1401141
Hello Brian, sorry I was out due to end-of-year holidays + vacation :o).
I'll be providing them a hotfixed dhcp server and asking for SRU
sponsorship soon.
Tks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in
I've provided the following PPA:
https://launchpad.net/~inaddy/+archive/ubuntu/lp1401141
# add-apt-repository ppa:inaddy/lp1401141
# apt-get update
# apt-get install isc-dhcp-server
(make sure to have version 4.2.4-7ubuntu13~lp1401141~1 installed)
Could you please test and provide feedback if
Attaching fix for Vivid.
Asking for sponsorship and for the Stable Release Update to be accepted.
Thank you
Rafael Tinoco
** Patch added: vivid_isc-dhcp_4.3.1-5ubuntu3.debdiff
** Patch removed: utopic_isc-dhcp_4.2.4-7ubuntu15.debdiff
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1401141/+attachment/4335363/+files/utopic_isc-dhcp_4.2.4-7ubuntu15.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Providing debdiff for Trusty (fixes the issue)
** Patch added: trusty_isc-dhcp_4.2.4-7ubuntu13.debdiff
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1401141/+attachment/4335337/+files/trusty_isc-dhcp_4.2.4-7ubuntu13.debdiff
--
You received this bug notification because you are a
Providing debdiff for Utopic (fixes the issue)
** Patch added: utopic_isc-dhcp_4.2.4-7ubuntu15.debdiff
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1401141/+attachment/4335363/+files/utopic_isc-dhcp_4.2.4-7ubuntu15.debdiff
--
You received this bug notification because you are a
isc-dhcp-server | 4.2.4-7ubuntu12 | trusty | amd64,
arm64, armhf, i386, powerpc, ppc64el
isc-dhcp-server | 4.2.4-7ubuntu14 | utopic | amd64,
arm64, armhf, i386, powerpc, ppc64el
I'll have to adequate the backport to Vivid:
isc-dhcp-server |
** Description changed:
+ [Impact]
+
+ * DHCP for InfiniBand IPoIB does not work currently.
+ * After providing missing GPXE patch it had problems (by Mellanox tests).
+ * IPoIB patches from Fedora project (out-of-upstream-tree) were outdated.
+
+ [Test Case]
+
+ * To have IPoIB devices
Kamal,
Sorry does that mean the issue was fixed or the issue is still there ?
We are finishing setting our IB environment here and I'll be able to
test it myself, just wanted to clarify meanwhile.
Thank you
Rafael Tinoco
--
You received this bug notification because you are a member of Ubuntu
Awesome!! I'll clarify what was done in this bug case and ask for the
fix to be accepted as a Stable Release Update for our isc-dhcp-package
(showing that our IB support was broken). I may need you to verify the
fix after it gets released to -proposed.
Thank you
Rafael
--
You received this bug
Fixed utopic SRU patch and attached it again.
** Patch added: utopic_isc-dhcp_4.2.4-7ubuntu15.debdiff
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1401141/+attachment/4335719/+files/utopic_isc-dhcp_4.2.4-7ubuntu15.debdiff
--
You received this bug notification because you are a
** Changed in: ifupdown (Ubuntu)
Assignee: Rafael David Tinoco (inaddy) = (unassigned)
--
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/1337873
Title:
Precise, Trusty
** Changed in: isc-dhcp (Ubuntu Trusty)
Assignee: (unassigned) = Rafael David Tinoco (inaddy)
** Changed in: isc-dhcp (Ubuntu Utopic)
Assignee: (unassigned) = Rafael David Tinoco (inaddy)
** Changed in: isc-dhcp (Ubuntu Vivid)
Assignee: (unassigned) = Rafael David Tinoco (inaddy
I'm reattaching debdiff for Trusty since a version was uploaded to
-proposed while this was waiting for sponsorship. Please include Trusty
in the affected list and consider this patch, being attached, as the
fix for Trusty.
Thank you
Rafael Tinoco
** Patch removed:
you!
Rafael Tinoco
** Changed in: e2fsprogs (Ubuntu)
Status: Confirmed = In Progress
** Changed in: e2fsprogs (Ubuntu)
Assignee: Theodore Ts'o (tytso) = Rafael David Tinoco (inaddy)
** Tags added: cts
--
You received this bug notification because you are a member of Ubuntu
Touch
Okay, I have provided one PPA for precise for this particular case:
https://launchpad.net/~inaddy/+archive/ubuntu/lp1321418
Cherry-picking 2 needed patches from upstream.
I have tested also the fsck with the filesystem that Theo provided and
version from PPA fixes the problems.
Second fsck run
I have tested ISC-DHCP for Trusty, Utopic Vivid for InfiniBand IPoIB
and it is working as expected.
Flagging as verification-done.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I received good feedback from a User by email:
Dear sir,
A couple of days ago I ran a manual update on Zorin OS 9 32 bits (based on
Ubuntu 14.04 LTS).
The only update offered at that time was isc-dhcp.
How interesting, I thought ... will this fix my WIFI connection problems?
I think it did!
*** This bug is a duplicate of bug 1401141 ***
https://bugs.launchpad.net/bugs/1401141
** Changed in: isc-dhcp (Ubuntu)
Assignee: (unassigned) = Rafael David Tinoco (inaddy)
** This bug has been marked a duplicate of bug 1401141
DHCP server does not work for IPoIB (Infiniband
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (inaddy)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1317437
Ti
This bug is being reported to happen also after a clonezilla based
installation for Trusty.
"""
The issue with /tmp will timeout and continue to boot, / will hand the boot up
unless there is some user intervention to continue the boot. The work around I
mentioned came from a suggestion in the
t;
>From "bcbc" is what this bug is all about.
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (inaddy)
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification beca
** Changed in: initramfs-tools (Ubuntu)
Assignee: Rafael David Tinoco (inaddy) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1317437
Ti
** Changed in: libnl3 (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (inaddy)
--
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/1312419
Title:
nl_cache_ref
Kamal,
As we talked about, I'm making the following PPA available:
https://launchpad.net/~inaddy/+archive/ubuntu/lp1312419
It contains Trusty version + commit:
>From 3700cc1ad3a3b507848deb401b9d0f41ff7010bb Mon Sep 17 00:00:00 2001
From: Thomas Graf
Date: Fri, 1 Feb 2013
It looks like that Trusty version also suffers from:
root@dixie:~# virsh start maas
error: Failed to start domain maas
error: internal error: missing IFLA_VF_INFO in netlink response
Whenever we try to start a VFIO (or KVM passthrough) SR-IOV based
machine.
I don't think this happens under
** Changed in: libnl3 (Ubuntu)
Status: Confirmed => In Progress
--
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/1312419
Title:
nl_cache_refill; rtnl_neigh_get fail
ubuntu/ trusty/main amd64
> Packages
> 100 /var/lib/dpkg/status
> libnl-route-3-200:
> Installed: 3.2.21-1
> Candidate: 3.2.21-1
> Version table:
> *** 3.2.21-1 0
> 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64
> Packages
>
The PPA for tests is:
https://launchpad.net/~inaddy/+archive/ubuntu/lp1529815
$ sudo add-apt-repository ppa:inaddy/lp1529815
$ sudo apt-get update && sudo apt-get dist-upgrade
Using a versioning schema that will be superseded by the final SRU.
PS: I'm also attaching the Trusty debdiff if this
** Changed in: isc-dhcp (Ubuntu Trusty)
Status: New => In Progress
** Changed in: isc-dhcp (Ubuntu Wily)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
** Attachment added: "dhclient.conf"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1529815/+attachment/4568545/+files/dhclient.conf
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
** Patch removed: "trusty_isc-dhcp_4.2.4-7ubuntu12.5.debdiff"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1529815/+attachment/4568495/+files/trusty_isc-dhcp_4.2.4-7ubuntu12.5.debdiff
** Patch added: "trusty_isc-dhcp_4.2.4-7ubuntu12.5.debdiff"
** Attachment added: "dhcpd.conf"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1529815/+attachment/4568546/+files/dhcpd.conf
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
Last test I did was to see if IB DHCP would get the BROADCAST flag on IB
interfaces. It did. Now, I removed:
ip->client->config->bootp_broadcast_always = 1;
from setup_ib_interface (when preparing for DHCP REQUEST), so I could
check if the option:
bootp-broadcast-always
from the config file
** Changed in: isc-dhcp (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1529815
Title:
InfiniBand DHCP flow with PRA and
I think during the fix of:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1529815
I accidentally missed the following:
> + /* Set the broadcast flag */
> + ip->client->config->bootp_broadcast_always = 1;
> +
in find_subnet.
This comes from: dhcp-4.2.5-lpf-ib.patch in tag
PAD Option 0, length 0, occurs 19
** Changed in: isc-dhcp (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (inaddy)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.laun
RFC 4390 from 2006:
https://tools.ietf.org/html/rfc4390
(Dynamic Host Configuration Protocol (DHCP) over InfiniBand) also stipulates:
As described above, the link-layer address is unavailable to the DHCP
server because the link-layer address is larger than the "chaddr"
field length. As a
I think during the fix of:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1401141
I accidentally missed the following:
> + /* Set the broadcast flag */
> + ip->client->config->bootp_broadcast_always = 1;
> +
in find_subnet.
This comes from: dhcp-4.2.5-lpf-ib.patch in tag
Talat,
I was able to set the Broadcast flag in a DHCP negotiation when using IB
interface.
Trusty patch is possibly ready.
TCPDUMP from the OFFER and ACK:
$ sudo tcpdump -i ib0 -nn -vvv -S
tcpdump: listening on ib0, link-type LINUX_SLL (Linux cooked), capture size
65535 bytes
04:38:01.051682
As David stated,
Per RFC 1541:
https://tools.ietf.org/html/rfc1541
"DHCP uses the 'flags' field [21]. The leftmost bit is defined as the
BROADCAST (B) flag"
Taking us to RFC 1542:
https://tools.ietf.org/html/rfc1542
3.1 Client use of the 'flags' field
3.1.1 The BROADCAST flag
Normally,
Continuation of RFC 1541 is RFC 2131:
https://tools.ietf.org/html/rfc2131 (adding DHCP INFORM msg type)
RFC 4390 from 2006:
https://tools.ietf.org/html/rfc4390
(Dynamic Host Configuration Protocol (DHCP) over InfiniBand) stipulates:
2.2. Use of the BROADCAST flag
A DHCP client on IPoIB
Okay, I just provisioned 2 servers (ConnectX-3 & ConnectX-4) so I could
reproduce this issue and work on it. I'll try to start reproducing the
issue now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
** Changed in: initramfs-tools (Ubuntu)
Status: In Progress => Incomplete
** Changed in: initramfs-tools (Ubuntu)
Assignee: Rafael David Tinoco (inaddy) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Though,
For comments:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1373070/comments/7
If you remove /dev/log rwx from /etc/apparmor.d/usr.sbin.rsyslog :
Using kernel Ubuntu-3.13.x DOES NOT show any DENIALS (Ubuntu-3.16,
Ubuntu-3.19 and Ubuntu-4.2 HWE kernels shows).
Using upstream
Yep, you're right. It was getting /dev/log from abstractions/base for
write only. My bad.
Though,
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1373070/comments/6
Shows same issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
I am able to reproduce this just by having apparmor.d profile
usr.sbin.rsyslogd removed from disable/ directory.
[ 674.165128] audit: type=1400 audit(1456491880.616:134): apparmor="DENIED"
operation="sendmsg" profile="/usr/sbin/rsyslogd" name="/dev/log" pid=3639
comm="dhclient"
Pavel, Déziel,
Im reproducing the same issue with dnsmasq + openstack + neutron:
Feb 16 18:35:01 juju-inaddy-machine-12 kernel: [ 4357.680900] audit:
type=1400 audit(1455647701.796:121): apparmor="DENIED"
operation="sendmsg" info="Failed name lookup - disconnected path"
error=-13
Okay, so, I had more time to dig a bit into this and, after some
analysis, I got:
Errors being reproduced:
[1668392.078137] audit: type=1400 audit(1459311786.129:1375455):
apparmor="DENIED" operation="sendmsg" info="Failed name lookup -
disconnected path" error=-13 profile="/usr/sbin/dnsmasq"
** Tags added: sts sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1529815
Title:
InfiniBand DHCP flow with PRA and DHCP relay not working
Status in isc-dhcp
It was brought to my attention a crash just like this one. Here is my
analsysis:
## INTRODUCTION
# From plugins/sudoers/pwutil.c:
/*
* Get a password entry by uid and allocate space for it.
*/
struct passwd *
sudo_getpwuid(uid_t uid)
{
struct cache_item key, *item;
struct rbnode
Summary:
Users coming from LDAP in groups ADMIN or SUDO will experience this
problem.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1565567
Title:
segv in sudo_getgrgid
This patch caused a regression that I'm going to fully explain in case:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1565567
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
(2)
Going back to backtrace we have:
mode_run -> policy_check -> sudoers_policy_main -
>create_admin_success_flag -> user_in_group (global sudo_user)
/* Check whether the user is in the admin group. */
if (!user_in_group(sudo_user.pw, "admin") &&
!user_in_group(sudo_user.pw,
(3)
Unfortunately this was caused by patch:
"also_check_sudo_group.diff"
Description: also check the sudo group to create the admin flag file
Author: Marc Deslauriers
Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1387347
Updated: 2016-03-30
--
Following execution path I get:
(1)
mode_run -> policy_check -> sudoers_policy_main -> sudoers_policy_init:
- init_vars (fills global variable sudo_user)
- sudo_user->pwd (from global struct passwd) will be used in "user_in_group"
as "struct passwd" of executing user
- it will check
(IPoIB)
+ DHCP CLIENT (IPoIB)
Ubuntu 14.04 kernel 3.13.0-74
Mellanox OFED 3.1-1.0.3 or inbox driver
isc-dhcp-client 4.2.4-7ubuntu12.3
** Changed in: isc-dhcp (Ubuntu Wily)
Assignee: (unassigned) => Rafael David Tinoco (inaddy)
** Changed in: isc-dhcp (Ubuntu Tru
** Patch removed: "trusty_isc-dhcp_4.2.4-7ubuntu12.5.debdiff"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1529815/+attachment/4568523/+files/trusty_isc-dhcp_4.2.4-7ubuntu12.5.debdiff
** Patch added: "trusty_isc-dhcp_4.2.4-7ubuntu12.6.debdiff"
** Patch added: "wily_isc-dhcp_4.3.1-5ubuntu3.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1529815/+attachment/4656430/+files/wily_isc-dhcp_4.3.1-5ubuntu3.2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Patch added: "xenial_isc-dhcp_4.3.3-5ubuntu13.debdiff"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1529815/+attachment/4656431/+files/xenial_isc-dhcp_4.3.3-5ubuntu13.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
I just verified that sudo fix seems good within yakkety. Marking it as
verification-done.
** 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 sudo in Ubuntu.
Okay, Tks Talat.
Ill propose this fix into all versions relying on the IB patches
submitted in fix:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1401141
Check:
https://bugs.launchpad.net/ubuntu/+source/isc-
dhcp/+bug/1401141/comments/31
--
You received this bug notification
Pls check:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1565567
If facing seg-faults in Xenial.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1387347
Title:
sudo
This patch was exposed by:
"also_check_sudo_group.diff"
(since user was in "sudo" group and should have stopped user_in_group
before)
Right after being caused by:
commit a1663632dc5ab7e7c01e17206854b6f0ba0347dd
Author: Todd C. Miller
Date: Fri Jan 22 17:04:59 2016
Verification for Xenial:
ubuntu@dixie:~$ uname -a
Linux dixie 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64
x86_64 x86_64 GNU/Linux
ubuntu@dixie:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.1 LTS
Release:16.04
I think I should skip Wily verification (EOL) and pursue Trusty verification.
It looks like Trusty fix wasn't committed. Could you commit Trusty so I can
verify it ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp
Subscribing sponsors again so Trusty can be sponsored. Still waiting on
SRU for Trusty.
** Tags removed: verification-needed-trusty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
** Tags added: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1550983
Title:
Fails to start with "Couldn't open libGL.so.1" (missing dependency?)
Status in
After long time I got the lab back so I'm verifying Trusty right now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1529815
Title:
InfiniBand DHCP flow with PRA and
Okay, bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1496942
Is avoiding me to verify this.
The lab I was able to get was a ConnectX-4 HCA lab (I was planning to use
SR-IOV).
I'll check if I can have two ConnectX-3 servers to verify this.
Be back soon.
--
You received this bug
Verification for Trusty:
## server
root@dixie:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.5 LTS
Release:14.04
Codename: trusty
root@dixie:~# dpkg -l | grep dhcp
ii isc-dhcp-client 4.2.4-7ubuntu12.6
@Sponsors
(Yakkety) Facing intermittent seg faults in multiple PDFs here. If
opening it with strace it rarely occurs, suggesting it is a timing/sync
issue.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x7f3e05ed1940 in cmsGetColorSpace () from
Another thing. Please check for containers referencing the filesystems
in question. When you have _netdev filesystems, it is possible that the
"mount --shared" characteristics of containers (different mount
namescapes) are holding references to the filesystem in question.
A good test is to test
Anyone facing this..
Could you please make sure to propagate I/O errors properly to
filesystem in order for it to call its automatically shutdown procedure.
After that, the mount won't reference the super block in kernel and that
will allow the device mapper to be closed/destroyed (this can be
Anyone facing this..
Could you please make sure to propagate I/O errors properly to
filesystem in order for it to call its automatically shutdown procedure.
After that, the mount won't reference the super block in kernel and that
will allow the device mapper to be destroyed (this can be seen by
** Changed in: systemd (Ubuntu Xenial)
Assignee: (unassigned) => Rafael David Tinoco (inaddy)
** Changed in: systemd (Ubuntu Xenial)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
Hello Matt,
Good to read your feedback. When you have multipath AND iscsi, the error
propagation timeout can be given by one or both, that is why I explained
both. This issue is not an iscsi or multipath problem, it is a systemd
problem related to the fact that the network is removed before the
I've made a small change creating a unit file slightly different from
the one already present in systemd-204, considering different
dependencies for this usage (mounting/umounting volumes when upstart has
already taken part on it).
The result is here: http://pastebin.ubuntu.com/25663762/
As you
Meanwhile I have created a PPA containing the fix for all those affected
users:
https://launchpad.net/~inaddy/+archive/ubuntu/lp1718966
$ sudo add-apt-repository ppa:inaddy/lp1718966
$ sudo apt-get update
$ sudo apt-get dist-upgrade
Is likely enough for you to have a temporary fix.
--
You
** Changed in: libnl3 (Ubuntu)
Assignee: Rafael David Tinoco (inaddy) => (unassigned)
--
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/1312419
Title:
nl_cache_ref
After fixing this BUG (for canonical-livepatch snap to work, but being
affected by broken systemd in Trusty due to the lack of systemd-
fsck@.service unit file, I'm facing the following opened BUG:
https://bugs.launchpad.net/snapd/+bug/1721518 for canonical-livepatch
(or any other snap) to work).
Verifying...
http://pastebin.ubuntu.com/25753116/
After using -proposed version:
http://paste.ubuntu.com/25753146/
Considering this fixed. Verified!
** Tags removed: verification-needed verification-needed-trusty
** Tags added: verification-done verification-done-trusty
--
You received this
** Changed in: systemd (Ubuntu Trusty)
Assignee: (unassigned) => Rafael David Tinoco (inaddy)
--
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/1718966
Title:
Can
Ok so in systemd-204, in TRUSTY, you will find the following logic to
create the mount units:
- manager_loop
- process-event (WATCH_MOUNT)
- mount_fd_event
- mount_load_proc_self_mountinfo
- mount_add_one (if load_extras == true)
- mount_add_extras
-
Okay, so another quick workaround, now keeping the fsck enabled for the
volumes:
Create a file called "/lib/systemd/upstart/systemd-fsck@.service" with:
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU
** Description changed:
[Impact]
Installing snaps is not possible on Ubuntu 14.04 when having /var on its
own partition, whether its LVM or not.
The issue is with the core snap being unable to mount:
The error with /var isolated and using LVM:
root@ubuntu:~# snap install
1 - 100 of 283 matches
Mail list logo