golang (2:1.5-0ubuntu1) wily; urgency=medium
* New upstream release.
- Drop debian/patches/disable-duffzero-ppc64el.patch
* Breaks/Replaces: older golang-go.tools (LP: 1486560)
** Changed in: golang (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification
I'm having a bit of trouble seeing why dm_udev_wait() would make this
work properly ... Seems like the device creation should happen
regardless of whether kpartx has done its job beforehand, at least from
my quick look at the code in parted.
Also, this patch seems to be for parted 3.2; but in
** Changed in: samba (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1472584
Title:
ISST-LTE: Samba server doesn't work well on
It seems to me like this was largely covered by further ipmitool SRUs.
We're now at 1.8.13-1ubuntu0.3; which includes patches for the USB
interface support (although there is a bug open for it, too).
Should we consider this bug no longer necessary and ready to be closed?
--
You received this
Thierry, could you please simply attach the patch you used instead?
I've been looking into this today, I can't reproduce the issue with the
default settings (without user_friendly_names), as expected. I can see
how this would happen with friendly-names though, because then the parts
of
Is it possible that the issue might be something else that is directly
related to the devices themselves rather than the behavior in multipath-
tools?
I haven't looked very far yet, but maybe we're missing some other
commit, too.
** Tags removed: verification-needed
** Changed in:
** Changed in: multipath-tools (Ubuntu)
Status: New = Invalid
** Changed in: multipath-tools (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (mathieu-tl) = (unassigned)
** Changed in: parted (Ubuntu)
Status: New = Triaged
** Changed in: parted (Ubuntu)
Importance: Undecided
Ah, and I almost forgot, please describe the changes since RC 1 (from
the upstream changelog or wherever) since this will require a feature
freeze exception.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang in Ubuntu.
** Changed in: golang (Ubuntu)
Status: New = Triaged
** Changed in: golang (Ubuntu)
Importance: Undecided = Medium
** Changed in: golang (Ubuntu)
Assignee: (unassigned) = Michael Hudson-Doyle (mwhudson)
--
You received this bug notification because you are a member of Ubuntu
My concern isn't so much in that these binaries come with the source --
it sounds suboptimal, but it's not quite as bad as shipping binary blobs
we haven't built ourselves...
That's the main issue I have with it and with removing the line from
rules which deletes .syso files (note that we
This is already fixed in wily by way of multipath 0.5.0.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1386637
Title:
multipath shows non-mpath disks as being multipath
** Changed in: multipath-tools (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1386637
Title:
multipath shows non-mpath disks
** Changed in: multipath-tools (Ubuntu)
Assignee: brandyseres...@gmail.com (brandyseres256) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1386637
Title:
and not lagging behind would be good, I think. I'll
complete the bug on Monday when I am back home, we just need to list things
from the upstream ChangeLog.
Mathieu Trudel-Lapierre mathieu...@gmail.com
Freenode: cyphermox, Jabber: mathieu...@gmail.com
4096R/DC95CA5A 36E2 CF22 B077 FEFE 725C 80D3
Unfortunately we missed the Feature Freeze cutoff (and I realise it's
partly my fault). Let's fix this bug up to add the details needed for a
Freeze Exception (https://wiki.ubuntu.com/FreezeExceptionProcess)
** Changed in: rrdtool (Ubuntu)
Status: New = Triaged
--
You received this bug
** Description changed:
+ [Impact]
+ Users installing with a USB key attached to the installing system, or adding
a USB key on an installed system with multipath enabled will see the USB
devices picked up by multipath. This is confusing because it changes the paths
required to be used to
** Description changed:
[Impact]
Users of multipath-tools on systems which exhibit both multipathed and
non-multipathed drives or some USB devices (some USB devices may still be
picked up by multipath-tools if multipath-capable).
[Test case]
- Boot on a system with multipathed disks
Actually, this would be more of a partman-multipath issue, but it seems
to me like it would anyway be fixed by partman-multipath 4ubuntu0.1; but
you'll only find this version number from within the installer; looking
at /var/lib/dpkg/status.
Seeing as we didn't make any additional changes which
** Changed in: samba (Ubuntu)
Status: Confirmed = In Progress
** Changed in: samba (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
** Description changed:
+ [Impact]
+ Users of multipath-tools on systems which exhibit both multipathed and
non-multipathed drives or some USB devices (some USB devices may still be
picked up by multipath-tools if multipath-capable).
+
+ [Test case]
+ - Boot on a system with multipathed disks
All the fixes for this should have landed already, in parted, partman,
and multipath-tools. Could you please re-test this on 14.04 with all
updates applied?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
) = Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: ipmitool (Ubuntu Trusty)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: ipmitool (Ubuntu Vivid)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification
** Description changed:
+ [Impact]
+ New hardware enablement: enables IPMI usage over USB transport, for those
systems providing such an interface.
+
+ [Test case]
+ 1) run 'ipmitool -I usb sensor'
+
+ Without a patched ipmitool, this will not work. With a version of
+ ipmitool with USB
** Also affects: multipath-tools (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: multipath-tools (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: multipath-tools (Ubuntu Trusty)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu
** Changed in: multipath-tools (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: multipath-tools (Ubuntu)
Importance: Undecided = High
** Changed in: multipath-tools (Ubuntu)
Status: New = Triaged
--
You received this bug notification because
** Attachment added: boot.log
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1480399/+attachment/4437052/+files/boot.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
Public bug reported:
Wily, using multipath-tools 0.5.0-7ubuntu2
Installing Ubuntu on LVM over multipath disks fails to boot, falls to
the recovery console from systemd (not the initramfs console).
This is likely to be because of a race between LVM and multipath -- if
LVM tries to pick up the
Additional information. Output of multipath -v4 (as opposed to -v3)
shows that the ioctl reload can't happen because something else already
has a lock on it. I will need to dig in some more to verify whether that
really is LVM, and how to correct this.
Shipping the wwids file from multipath
Tried to extract as much information as possible from this system while
in the recovery console.
Note, this does not happen at all when installing directly to the
multipath device, only with LVM on top of multipath.
** Attachment added: typescript
partman-multipath also needs to ship the wwids file in post-
installations steps so that first boot will work.
** Also affects: partman-multipath (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Landed this in wily; with multipath-tools 0.5.0-7ubuntu2. Closing as Fix
Released.
** Changed in: multipath-tools (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in
Public bug reported:
Booting a multipathed systems can fail in initramfs if the wwids file is
not present and multipath-tools (with find_multipaths enabled) runs its
detection before udev has completely detected all disk paths.
Solution would be to either copy wwids file on the initramfs image
Reopening, since this was reverted in the updates, work is still in
progress.
** Changed in: multipath-tools (Ubuntu Trusty)
Status: Fix Released = New
** Changed in: multipath-tools (Ubuntu Trusty)
Status: New = In Progress
--
You received this bug notification because you are a
This particular bug does not need to be verified, as mentioned, this is
a revert of a fix in proposed, not the fix itself. The other bugs
attached to the multipath-tools upload for ubuntu7.4 do need to be
verified however.
--
You received this bug notification because you are a member of Ubuntu
@drbrent, provided verification passes for both the affected packages
(and that, as soon as possible), there is enough time for this update to
make it into 14.04.3.
parted changes needed to be vastly adapted to apply on parted 2.3. Be
warned that you'll need to enable the proposed repository *in
verification-failed: multipath-tools still claims USB devices (as tested
in cert lab). I'm doing some more backporting to try to identify the
patch that will fix this correctly.
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this bug notification because
Let's re-test with my PPA.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1441930
Title:
Fix handling of multipathed disks with 4k-sectors
To manage notifications about
** Changed in: parted (Ubuntu Trusty)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1441930
Title:
Fix handling of multipathed disks
** Also affects: multipath-tools (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1445973
Title:
multipathd
** Package changed: multipath-tools (Ubuntu) = partman-multipath
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1445973
Title:
multipathd changes the underlying
Testing this on Trusty (and for some reason, my overlay not working), it
looks as through 4k disks are already working properly in Trusty.
@Mauricio, could you please confirm this? I've prepared a patched parted
in my installer-dev PPA, but it seems like it's not necessary for
trusty.
--
You
** Also affects: parted (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: multipath-tools (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Description changed:
+ [Impact]
+ This bug impacts multipath users who need to tweak timeout values for DevLoss
and FastIoFail for performance reasons.
+
+ [Test Case]
+ On a multipath system, attempt to modify DevLossTO or FastIoFailTO, then
verify that the values got applied with
** Description changed:
+ [Impact]
+ Impacts any user of multipath, regardless of release. Users who do not
currently see issues may see them on upgrade to a newer version of systemd/udev.
+
+ [Test case]
+ See below. Test case can be summarized as boot on a multipath system.
+
+ [Regression
(Ubuntu Vivid)
Status: New = In Progress
** Changed in: multipath-tools (Ubuntu Trusty)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: multipath-tools (Ubuntu Vivid)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
** Changed
Digging deeper, looks like the DevLossTO and FastIoFailTO settings fixes
are already in 0.5.0; so the changes are in wily.
Moving on to SRU this to vivid, trusty.
** Changed in: multipath-tools (Ubuntu)
Status: In Progress = Fix Released
** Changed in: multipath-tools (Ubuntu Vivid)
We landed a fix for this in partman-multipath (4ubuntu2); the bug was
not closed because I forgot to add a bug tag. Closing as Fix Released.
** Changed in: multipath-tools (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
)
Importance: Undecided = Medium
** Changed in: multipath-tools (Ubuntu)
Importance: Undecided = Medium
** Changed in: multipath-tools (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: multipath-tools (Ubuntu Vivid)
Assignee: (unassigned) = Mathieu
Could you please run 'udevadm info --query=all --name=/dev/sda' so we
know whether there are attributes we can use to differentiate these
drives?
** Changed in: multipath-tools (Ubuntu)
Status: Triaged = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Status: New
** Changed in: multipath-tools (Ubuntu Trusty)
Status: New = Triaged
** Changed in: multipath-tools (Ubuntu Trusty)
Importance: Undecided = Medium
** Changed in: multipath-tools (Ubuntu Trusty)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl
Yes, it needs to be backported since it was meant for 0.5.0.
** Changed in: multipath-tools (Ubuntu Trusty)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath
** Changed in: debian-installer-utils (Ubuntu Trusty)
Status: New = In Progress
** Changed in: debian-installer-utils (Ubuntu Trusty)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: debian-installer-utils (Ubuntu Precise)
Status: New = In Progress
.
** Changed in: multipath-tools (Ubuntu)
Assignee: Chris J Arges (arges) = Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: multipath-tools (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
In light of this, I'm guessing we'll need to special-case these devices
to use page 0x80 to decide whether to consider them as multipath
devices, at least on 14.04.
For 15.10; I'd like to run a bit more testing, I believe multipath-tools
0.5.0 / sg3-utils will make changes unnecessary and
Still working on it. With sg3-utils adapted to also ship a sg3-udeb
package for use by the installer (which multipath-udeb can depend on so
it's available to the installer), things appear to work more or less
properly. To be able to ship this we still need the dm-service-time
module available in
I pulled both multipath-tools directly from Debian and did a merge of
multipath-tools 0.5.0 with Ubuntu changes; both seem to currently be
unable to notice that QEMU harddrives should be multipathed. I'm
investigating the situation.
--
You received this bug notification because you are a member
Well, that change was made for a good reason; multipath now no longer
depends on scsi_id to be able to pick drives to use to multipath, and we
can explicitly whitelist (or use blacklist_exclusions) devices or re-
enable ID_SERIAL by modifying multipath.conf. Is this affecting other
drives than the
** Changed in: multipath-tools (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1455482
Title:
Multipath: upgrade
The devices don't appear to have the same serial or even the same
product name, I'm unsure why they're be considered as multipathed even
with the apparent same scsi_id as you've discovered.
What does multipath -ll output on this system? Also, could you please
run the following commands:
for d in
Ideal for that would be to convince the Debian maintainers to drop the
patch.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1455482
Title:
Multipath: upgrade
I went ahead and asked about a timeline for a next multipath-tools
release on the dm-devel mailing list. Timeline was said to be before
summer holidays.
I'll do the multipath-tools merge with Debian so we get 0.5.0, and once
there is a new release we'll see if it can make it into 15.10, if it
No idea. I think can operate with the usual procedures: merge now with
0.5.0, and either merge or do an updated package once a new release is
available, provided it happens before Feature Freeze (August 20).
I'll include patches for the above bugs as I merge multipath-tools.
--
You received
I looked at this as well, it looks like it probably would benefit from
preparing the 0.2.3 release instead of patching things. I haven't looked
very closely, but it seems as though the patches may already be included
in uptream git (and thus in 0.2.3, which seems to be the latest revision
on
Now that the vivid release is done, let's revisit these patches. I'll do
some testing on my end, but looking briefly at them, they make sense.
What other installer changes (since you mention them in your comment
#20) are necessary?
** Changed in: multipath-tools (Ubuntu)
Status: Confirmed
** Changed in: multipath-tools (Ubuntu)
Importance: Undecided = High
** Changed in: multipath-tools (Ubuntu)
Status: New = In Progress
** Changed in: multipath-tools (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification
** Changed in: parted (Ubuntu)
Importance: Undecided = High
** Changed in: multipath-tools (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: parted (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug
*** This bug is a duplicate of bug 1431650 ***
https://bugs.launchpad.net/bugs/1431650
** This bug has been marked a duplicate of bug 1431650
Multipath devices take long to initialize during initramfs
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Well, not necessarily. The swap issue is the same as the rootfs one-- at
some point multipath times out, and other init jobs would also timeout
trying to bring up the swap (which can't be identified from the UUID)
whereas the rootfs got brought up on a single path using the UUID.
The debdiff
]+(-part[0-9]+)?) but may instead be using the
first single drive it found matching the proper UUID. (see also bug
1429327)
** Affects: multipath-tools (Ubuntu)
Importance: Medium
Assignee: Mathieu Trudel-Lapierre (mathieu-tl)
Status: In Progress
--
You received this bug
= In Progress
** Changed in: multipath-tools (Ubuntu)
Importance: Undecided = Medium
** Changed in: multipath-tools (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
-tools (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: multipath-tools (Ubuntu)
Importance: Medium = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https
I see delays in the devices being detected, which means after running
through the initramfs scripts and other startup scripts, the installed
system will come up using /dev/sdb1 (for example) rather than the
equivalent device mapper device, and no swap.
If you can point me to the bug you filed
: Undecided = Medium
** Changed in: multipath-tools (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1432062
As a first thing to investigate, there in fact was a grub-installer
upload on Feb 19. I'll start by checking if it could be as simple as
that upload breaking things.
** Changed in: debian-installer (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you
Looks like it really is the latest grub-intaller upload that breaks
this; reverted. The fix should be available in a few moments.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to a duplicate bug report (1429849).
** Package changed: debian-installer (Ubuntu) = grub-installer (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to a duplicate bug report (1429849).
https://bugs.launchpad.net/bugs/1427821
Title:
server iso install fails during
: No upgrade log present (probably fresh install)
UserGroups:
defaults.conf:
lxc.network.type = veth
lxc.network.link = lxcbr0
lxc.network.flags = up
lxc.network.hwaddr = 00:16:3e:xx:xx:xx
upstart.lxc-net.override: manual
** Affects: lxc (Ubuntu)
Importance: High
Assignee: Mathieu Trudel
** Patch added: no_name_build_path.patch
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1277450/+attachment/3972302/+files/no_name_build_path.patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
I'm fixing this since it's so obvious... package is building in sbuild
right now, will test and upload shortly.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1277450
Title:
Actually, even better yet, the new patched attached.
Otherwise:
# lxc-autostart -L
lxc-autostart: could not build log path
lxc-autostart: could not build log path
lxc-autostart: could not build log path
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Patch added: dont_crash_log_init.patch
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1277450/+attachment/3972362/+files/dont_crash_log_init.patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Now that we can use bind-dynamic, I have nothing against setting that
value instead of bind-interfaces, if it indeed solves the latest issues
that were reported.
However, I'd really appreciate if separate bugs could be opened rather
than reopening this bug, it would make each individual issue
I uploaded a new package to the precise queue last week.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1004775
Title:
NetworkManager restarts dnsmasq and adds host route on every
dnsmasq is now in updates, and there is no SRU blocking network-manager
-- I'll upload the fix for this in -proposed today.
** Changed in: dnsmasq (Ubuntu Precise)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team,
** Description changed:
+ [Impact]
+ This issue affects all users of NetworkManager in a dual stack (IPv4 w/ IPv6
on the same network) environment. When any router advertisement is received,
NetworkManager restarts dnsmasq in order to update the DNS configuration it
uses.
+ This change
** Changed in: network-manager (Ubuntu)
Status: Confirmed = In Progress
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
** Branch unlinked: lp:~mathieu-tl/network-manager/0.9.4.0-0ubuntu4.2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1004775
Title:
NetworkManager restarts dnsmasq and adds host
** Changed in: dnsmasq (Ubuntu Precise)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1029977
Title:
dnsmasq-base should ship the dnsmasq dbus
in: dnsmasq (Ubuntu Quantal)
Status: New = Fix Released
** Changed in: dnsmasq (Ubuntu Precise)
Status: New = In Progress
** Changed in: dnsmasq (Ubuntu Precise)
Importance: Undecided = High
** Changed in: dnsmasq (Ubuntu Precise)
Assignee: (unassigned) = Mathieu Trudel-Lapierre
I didn't try to reproduce yet, but I definitely believe there might be a
problem; so I'll look into it.
It's probably my fault too ;)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
(Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
** Package changed: dnsmasq (Ubuntu) = network-manager (Ubuntu)
** Changed in: network-manager (Ubuntu)
Milestone: None = ubuntu-12.10
--
You received this bug notification because you are a member of Ubuntu
Server
I'm reassinging this to network-manager. The issue here is not related
to that upstream thread. Unfortunately, we don't have enough information
to debug this. Please answer the following questions:
Is 'dnsmasq' (the package), installed? (check with dpkg -l dnsmasq)
If so, what is its
(Ubuntu Precise)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/959037
Title:
NM-controlled dnsmasq prevents other
in: dnsmasq (Ubuntu Precise)
Status: Confirmed = Triaged
** Changed in: dnsmasq (Ubuntu Precise)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: network-manager (Ubuntu Precise)
Importance: Low = High
--
You received this bug notification because you
This remains a bug, but fixing bug 1044388 is going to make this a much
more rare occurence.
Unassigning for now, the bug needs to be filed upstream and fixed by the
upstream maintainer.
** Changed in: dnsmasq (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (mathieu-tl) = (unassigned)
--
You
Thomas: no, this is a dnsmasq bug. Even if nothing is set to listen on
127.0.0.1, if dnsmasq is configured to avoid lo and bind to interfaces
(as it is per the network-manager provided configuration) it should
still do so and not write out lo.dnsmasq.
** Package changed: network-manager (Ubuntu)
in: dnsmasq (Ubuntu)
Importance: Undecided = Medium
** Changed in: dnsmasq (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https
** Changed in: network-manager (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1034946
Title:
dnsmasq and network manager broken
Thomas, it would be best to open a bug upstream for documentation for
VLAN... and/or anyway file a new bug here for the documentation too
rather than reusing old bugs.
Michael: I think all you need for this is that the top section
('[connection]') is set autoconnect=true or so. It does work
** Also affects: dnsmasq (Ubuntu)
Importance: Undecided
Status: New
** Changed in: dnsmasq (Ubuntu)
Status: New = In Progress
** Changed in: dnsmasq (Ubuntu)
Importance: Undecided = High
** Changed in: dnsmasq (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre
101 - 200 of 240 matches
Mail list logo
