** Description changed:
With the switch to systemd, all support for iscsi root (and other)
filesystems disappeared, since shutdown yanks the rug out from under us.
Rather than just relying on /etc/iscsi/iscsi.initramfs (which d-i
creates..), the DEV check should be expanded to include
** No longer affects: ifupdown (Ubuntu)
** No longer affects: ifupdown (Ubuntu Xenial)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621507
Title:
initramfs-tools configure_networking() fails to
,
and networking.service ExecStop should honor those checks.
** Affects: maas
Importance: Undecided
Status: New
** Affects: ifupdown (Ubuntu)
Importance: Undecided
Assignee: LaMont Jones (lamont)
Status: New
** Affects: ifupdown (Ubuntu Xenial)
Importance
** Also affects: maas
Importance: Undecided
Status: New
** No longer affects: maas (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1629868
Title:
times out because of no dbus
To
** Changed in: open-iscsi (Ubuntu)
Assignee: LaMont Jones (lamont) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621507
Title:
initramfs-tools configure_networking() fa
** Also affects: ifupdown (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/1621507
Title:
initramfs-tools configure_networking() fails to dhcp ipv6
** Attachment added: "non-kernel processes on the machine (no dbus running)"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1629868/+attachment/4753473/+files/processes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "logs from the machine"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1629868/+attachment/4753475/+files/y-deploy.log.tar.gz
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
** Attachment added: "console log"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1629868/+attachment/4753474/+files/y-deploy.script
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Given this command line:
BOOT_IMAGE=ubuntu/amd64/hwe-y/yakkety/daily/boot-kernel nomodeset
iscsi_target_name=iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-amd64-hwe-y-yakkety-daily
iscsi_target_ip=2001:67c:1562:8010::2:1 iscsi_target_port=3260
iscsi_initiator=kearns
After further checking, comcast is sending them, my machine is just not
seeing them... Will file a separate bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609898
Title:
dhclient incorrectly
With this fix, my IPv6 service from Comcast broke.
Specifically, they hand out an IP on the /64 via dhcpv6, with the
default gateway being an IP on the same /64, along with an IA /56 for
the customer to use locally.
Adding the default route fails because there is no route to said gateway
(since
I have confirmed that the machine is accepting router advertisements,
and that comcast is not sending them.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609898
Title:
dhclient incorrectly assumes
Public bug reported:
I dist-upgrade a chroot'ed system as part of a process, which now breaks
because dirmngr (somewhere) decided that it should be running,
regardless of everything. The list below is from apt at the start of
the upgrade (specifically, dist-upgrading the current yakkety daily
** Also affects: cloud-initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: cloud-initramfs-tools (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621615
** Description changed:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1621507 talks of
- how ipv6 netboot with iscsi root disk doesn't work, blocking ipv6-only
+ how IPv6 netboot with iscsi root disk doesn't work, blocking IPv6-only
MAAS.
After I hand-walked busybox through
** Description changed:
- initramfs' configure_networking function uses ipconfig to configure the
- network.
-
- ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-
- bin/bugreport.cgi?bug=627164
-
- Anyone wanting to netboot in an ipv6-only environment is affected.
+
iproute2 turns out to be not needed for this.
** No longer affects: iproute2 (Ubuntu)
** No longer affects: iproute2 (Ubuntu Xenial)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621507
Title:
open-iscsi's part of this is fixed in open-
iscsi_2.0.873+git0.3b4b4500-14ubuntu4
** Changed in: open-iscsi (Ubuntu)
Status: New => Fix Committed
** Also affects: initramfs-tools (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: klibc (Ubuntu Xenial)
** Also affects: iproute2 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: open-iscsi (Ubuntu)
Importance: Undecided
Status: New
** Changed in: open-iscsi (Ubuntu)
Assignee: (unassigned) => LaMont Jones (lamont)
** Changed in: iproute2 (Ubuntu)
Assig
** Also affects: open-iscsi (Ubuntu)
Importance: Undecided
Status: New
** Changed in: open-iscsi (Ubuntu)
Status: New => Invalid
** Package changed: open-iscsi (Ubuntu) => ubuntu
** No longer affects: ubuntu
--
You received this bug notification because you are a member of
** Summary changed:
- lacks support for ipv6 addresses
+ impitool lacks support for ipv6 addresses
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621901
Title:
impitool lacks support for ipv6
** Attachment added: "cloud-init-output.log from the system"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1621615/+attachment/4743950/+files/cloud-init-output.log
** Changed in: maas
Milestone: None => 2.1.0
--
You received this bug notification because you are a member of
** Attachment added: "cloud-init.log"
https://bugs.launchpad.net/maas/+bug/1621615/+attachment/4743949/+files/cloud-init.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621615
Title:
network
/run/net-eno1.conf from the booted system. The various packages needed
to reproduce this are found in ppa:lamont/maas.
** Attachment added: "net-eno1.conf from the booted system"
https://bugs.launchpad.net/maas/+bug/1621615/+attachment/4743948/+files/net-eno1.conf
--
You received this bug
With the attached patch applied to0.7.8-1-g3705bb5-0ubuntu1~16.04.1, we
still fail.
Details of the failure are attached below.
** Attachment added: "A patch that does not fix the problem."
https://bugs.launchpad.net/maas/+bug/1621615/+attachment/4743947/+files/ipv6-config
--
You received
In the category of "highly related":
grep -v ^# /etc/network/interfaces.d/50-cloud-init.cfg
auto lo
iface lo inet loopback
iface eno1 inet dhcp
dns-nameservers 2001:67c:1562:8010::2:1
netmask 64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Tags added: maas-ipv6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621901
Title:
lacks support for ipv6 addresses
To manage notifications about this bug go to:
** Tags removed: needs-upstream-report
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618543
Title:
freeipmi lacks IPv6 support
To manage notifications about this bug go to:
https://github.com/chu11/freeipmi-mirror/issues/6
https://savannah.gnu.org/bugs/index.php?49037
** Bug watch added: github.com/chu11/freeipmi-mirror/issues #6
https://github.com/chu11/freeipmi-mirror/issues/6
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
# sudo ipmitool lan print
Set in Progress : Set Complete
Auth Type Support :
Auth Type Enable: Callback :
: User :
: Operator :
: Admin:
: OEM :
Public bug reported:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1621507 talks of
how ipv6 netboot with iscsi root disk doesn't work, blocking ipv6-only
MAAS.
After I hand-walked busybox through getting an IPv6 address, everything
worked just fine until cloud-init couldn't fetch the
** Summary changed:
- ipconfig lacks ipv6 support
+ initramfs-tools configure_networking() fails to dhcp ipv6 addresses
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621507
Title:
initramfs-tools
** Also affects: initramfs-tools (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/1621507
Title:
ipconfig lacks ipv6 support
To manage
Public bug reported:
initramfs' configure_networking function uses ipconfig to configure the
network.
ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=627164
Anyone wanting to netboot in an ipv6-only environment is affected.
** Affects: klibc (Ubuntu)
And after more investigation, I can see that what I really need is a
failing system where I can poke at it to understand what is going on --
the whole all-TLDs-are-signed-and-that's-why doesn't seem to pan out as
I tried to reproduce the issue.
--
You received this bug notification because you
When the config has "dnssec-validation auto;", BIND attempts to validate
all answers, and stops checking once it gets to a DNS zone that has no
signatures. Categorically, all TLDs have signatures, so the lack of a
signature on the .maas DNS zone is fatal to the DNSSEC validation.
If the domain
Having said that, if MAAS is going to continue to defualt to, and
RECOMMMEND that users use, a TLD of "maas", then MAAS should default
it's setting to "dnssec no" in the case where the default domain is
still named "maas" -- Open to discussion is whether this should be thru
chaning the global
The current state of the DNS is that the root zone is signed, and
EVERYTHING delegated from it is signed by the root zone. Once you get
below that, the lack of signatures on a zone is left as an exercise for
the admins of that zone. (example.com can be delegated from the
[signed] COM zone
Better yet, have dhclient retry that bind call itself, at least for a
short while, before throwing an error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447715
Title:
dhclient -6: Can't bind to
Public bug reported:
1.4.11 lacks any ipv6 support. 1.5.3 (current upstream from 1 Aug 2016)
also lacks ipv6 support.
Note that both ipmitool (since 2014 or so) and openipmi (since
2003-11-11) support IPv6.
** Affects: freeipmi (Ubuntu)
Importance: Undecided
Status: New
--
You
This landed in xenial.
** Changed in: freeipmi (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303692
Title:
New upstream version 1.4.1
To manage
Public bug reported:
With (self reported) version 0.7.7, when cloud-init displays the "Net
device info", it only reports 1 each IPv4 and IPv6 address per
interface, even if a second subnet has been configured on the interface
(via ens3:1, for example). This can be confusing to someone working on
** Attachment added: "screenshot of the failed attempt"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1229458/+attachment/4724000/+files/1229458-screenshot.jpg
** Changed in: grub2 (Ubuntu)
Status: Fix Released => In Progress
--
You received this bug notification because you
With this dhcpv6 and the bootloaders from yakkety (as of yesterday's
date), we get http://people.canonical.com/~lamont/1229458-screenshot.jpg
(I'll attach that momentarily). It appears that bootx64.efi finished
loading grub, released the IP, got the reply for the release, and
launched grubx64.efi
Public bug reported:
0.1~bzr42-0ubuntu2 (and earlier) fail to work for ipv6 clients, with the
following traceback:
File "/usr/lib/python3/dist-packages/tftp/protocol.py", line 95, in
_startSession
reactor.listenUDP(0, session)
File
Public bug reported:
Addresses of the form ":::169.254.169.254" are perfectly valid, but
not supported by django's http.request.
The following diff addresses the problem.
--- django/http/request.py 2015-11-24 10:21:15.0 -0700
+++ django/http/request.py.new 2016-08-10
What is not addressed by this patch is that twisted assumes that if it is given
a hostname, then the user clearly means IPv4. The web client setup is not in
the correct order, it should be:
1) resolve the hostname
2) iterate through the available IP addresses (probably preferring ipv6, like
With this patch, twisted behaves as expected when given an IPv6 IP
address in the standard URL format: scheme://[ip:v6::add:ress]:port/path
(port being optional, of course)
** Patch added: "Patch that has twisted use the standard
scheme://[ip:v6::add:ress]:port/path syntax for URL"
investigating this more, twisted's handling of ipv6 is fundamentally broken in
some bad ways:
1) it allows "2001:db8::1:80" as an IP/Port combination, deciding that what you
meant is [2001:db8::1]:80, rather than the default port on 2001:db8::1:80.
2001:db8::1:7f, on the other hand, means
getRequestHostname() has similar problems, which this addresses:
def new_getRequestHostname(self):
host = self.getHeader(b'host')
if host:
if host.startswith(b'['):
if host.find(b']') < host.rfind(b':'):
return
** No longer affects: python-formencode (Ubuntu Xenial)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1605726
Title:
url validation does not support ipv6 addresses
To manage notifications about
** Changed in: python-formencode (Ubuntu)
Assignee: (unassigned) => LaMont Jones (lamont)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1605726
Title:
url validation does not support i
The fix will be updated shortly.
** Changed in: python-formencode (Ubuntu)
Milestone: None => ubuntu-16.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1605726
Title:
url validation does not
Public bug reported:
The defacto standard "https://[2001:db8::3]:/path/to/location;
syntax is not supported for urls, nor is any ipv6 address.
** Affects: python-formencode (Ubuntu)
Importance: Undecided
Assignee: LaMont Jones (lamont)
Status: New
** Affects: p
Public bug reported:
If the client connecting to the twisted (16.0.0-1, still present in upstream
16.3.0), then twisted dies as follows:
2016-07-18 15:40:21 [HTTPChannel,468,:::127.0.0.1] Unhandled Error
Traceback (most recent call last):
File
As landed, the FQDN maps to the "primary" IP, and everything else gets
IFACE.FQDN -- with possible multi-address and/or multi-PTR RRs in the
RRset, which makes sense.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: maas
Milestone: None => 2.0.0
** Summary changed:
- ambigious reverse DNS lookups because MAAS creates multiple PTR records
+ [2.0] confusing reverse DNS lookups because MAAS creates multiple PTR records
--
You received this bug notification because you are a member of
Having said all that, I'm now leaning toward not putting the interface
name PTR on the IPs of boot interfaces, since that seems to be the more
general mode.
Note however: if multiple names resolve to the same IP, then all of them
will be in the PTR RRset. (Since this is a valid and often
For purposes of charming, the apache charm (or whatever) will need to
add all of the PTR RRset names to the authorized list, to work around
the apache bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This will be fixed by adding A/ RRsets for the interface names
(first format above). If the second format (non-interface) is given to
mod_authz_host, then either answer will work.
Having said that, this is actually a bug in mod_authz_host, which should
grant access if ANY of the PTR RRset
As the change was implemented in 2.0, backporting it to 1.9 would
require a data migration in 1.9, which we need to avoid.
As such, if we ever do backport this to 1.9, we'll probably need assume
rdns_mode=Enabled in the code, and if the admin wants
rdns_mode=rfc2317_glue (the 2.0 default), then
** Changed in: maas/trunk
Status: In Progress => Fix Committed
** Changed in: maas/trunk
Milestone: 1.10.0 => 2.0.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1356012
Title:
maas
Following apw's excellent advice pointing to
https://www.v13.gr/blog/?p=378 and abusing another ipv6 address on the
afflicted host:
tcpdump -npi br0 ip6 and not port 22 | grep -i neigh
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on br0, link-type EN10MB
apport-collect is not really an option on the machine, nor should any of
that really provide any additional information that's not already in the
bug report. holler at me if I missed anything relevant.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this
However, given that eth0.2 is seeing the solicitation, and br0 isn't,
I'm leaning strongly toward the bridge code being slightly buggy.
My next test will be to do a non-promisc tcpdump on eth0.2 and see if
_THAT_ sees the traffic. That may take me a week before I can do it
though, due to
One other tidbit: The gateway in question is using eth0.2 on a trunked
port to a Cisco WS-C2960G-24TC-L running
c2960-lanbasek9-mz.150-2.SE9.bin.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1597806
Public bug reported:
I have a xenial (4.4.0-24-generic) machine that loses ipv6 connectivity
every time I reboot the gateway it uses.
br0 is a bridge which has eth0.2 as its only member, with (currently) 6 "scope
global temporary deprecated dynamic" (privacy) addresses, and:
inet6
** Changed in: bind9 (Ubuntu)
Milestone: None => xenial-updates
** Changed in: bind9 (Ubuntu)
Assignee: (unassigned) => LaMont Jones (lamont)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
In /usr/lib/python3/dist-packages/twisted/conch/ssh/keys.py, fromString
does not support ed25519 and ecdsa keys.
** Changed in: twisted (Ubuntu)
Milestone: 2.1.0 => None
** Changed in: maas
Milestone: None => 2.1.0
** Also affects: twisted (Ubuntu)
Importance: Undecided
2016-06-08 13:01:15 [maasserver] ERROR: Invalid SSH public key
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/maasserver/models/sshkey.py", line 41,
in validate_ssh_public_key
key = Key.fromString(value.encode("utf-8"))
File
4.6 test kernel (2dcd0af568b0cf583645c8a317dd12e344b1c72a would seem to
be the base) does not exhibit the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1543683
Title:
Fails to detect (second)
Debian (and therefore ubuntu) policy 10.7.2 (configuration file
location):
"Any configuration files created or used by your package must reside in
/etc. If there are several, consider creating a subdirectory of /etc
named after your package."
That is what led to the choice to place them all in
It is defaulted to "auto" because more and more of the internet _IS_
enabling DNSSEC: all delegations from the root are signed, and most
registries will take care of getting the DS RRsets into the parent zone.
The only way to actually fix some of the DNS cache poisoning attacks is
to enable
Also, apport.py is python2, so this needs more work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578674
Title:
bind9 packages should not depend on python2 in xenial
To manage notifications
There are a sum total of 2 binaries affected by the change:
/usr/sbin/dnssec-checkds
/usr/sbin/dnssec-coverage
Both of which are in bind9utils, and used for verifying dnssec
configuration. Neither of them is actually required for the operation
of BIND.
--
You received this bug notification
** Changed in: bind9 (Ubuntu Xenial)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578674
Title:
bind9 packages should not depend on python2 in xenial
To
There are some utility scripts which are written in python. As part of
9.10, they were changed to be able to run with python2 or python3. This
change simply switches them from using python2 to using python3,
affecting the #! at the top of the generated script, but otherwise
changing nothing.
*** This bug is a duplicate of bug 1571174 ***
https://bugs.launchpad.net/bugs/1571174
** This bug has been marked a duplicate of bug 1571174
package squid3 failed to install/upgrade: dependency problems - leaving
triggers unprocessed
--
You received this bug notification because you
This also affects trusty->xenial upgrades (see 1575946)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571174
Title:
package squid3 failed to install/upgrade: dependency problems -
leaving
** Project changed: maas => squid3 (Ubuntu)
** Changed in: squid3 (Ubuntu)
Importance: Critical => Undecided
** Changed in: squid3 (Ubuntu)
Status: Triaged => New
** Changed in: squid3 (Ubuntu)
Milestone: 2.0.0 => None
** Changed in: squid3 (Ubuntu)
Assignee: Newell Jensen
** Changed in: inspircd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1334462
Title:
version of inspircd in repos is broken for all versions of ubuntu
To
** Changed in: bind9 (Ubuntu Xenial)
Milestone: None => xenial-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578674
Title:
bind9 packages should not depend on python2 in xenial
To
ial)
Status: Fix Committed => In Progress
** Changed in: bind9 (Ubuntu Xenial)
Assignee: (unassigned) => LaMont Jones (lamont)
** Changed in: bind9 (Ubuntu)
Milestone: None => ubuntu-16.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
** Patch added: "debdiff for 8ubuntu2"
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1578674/+attachment/4656508/+files/bind9_9.10.3.dfsg.P4-8ubuntu2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Fixed in 1:9.10.3.dfsg.P4-10 in yakkety.
** Changed in: bind9 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578674
Title:
bind9 packages should not
Public bug reported:
With the push to get python2.7 out of use in main, bind9utils et al
should be switched to use python3 (which 9.10 supports fully and
interchangeably with 2.7).
** Affects: bind9 (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: bind9 (Ubuntu
Running 1:9.10.3.dfsg.P4-8, I see core files in /var/crash. Upgrading
to 1:9.10.3.P4-8ubuntu1 (from xenial-proposed) I no longer see the error
(other than during the upgrade, when -8 shuts down for the last time.)
** Tags removed: verification-needed
** Tags added: verification-done
--
You
@@
+bind9 (1:9.10.3.dfsg.P4-8ubuntu1) xenial-proposed; urgency=medium
+
+ * Fix bad patch from when we switched to quilt. Closes: #820847 LP:
+#1552801, #1549788, #1553460
+
+ -- LaMont Jones <lam...@ubuntu.com> Tue, 26 Apr 2016 16:30:06 -0600
+
bind9 (1:9.10.3.dfsg.P4-8) unstable; urgency=
[Impact]
At shutdown, rather than terminating normally, named aborts with an
assertion failure, pointing at a memory leak. This is confusing to
users, and could potentially mask an actual memory-leak that could
affect runtime operation. (The actual leaked memory is a control
structure that is
Nevermind.. I've reproduced it, and will be working on it. FWIW, the
error is occurring during the daemon shutdown, though that's not really
a big help. :/
** Changed in: bind9 (Ubuntu)
Assignee: (unassigned) => LaMont Jones (lamont)
--
You received this bug notification because
Can I get your BIND configuration? Either to the bug, or privately to
lam...@ubuntu.com if you are not comfortable posting it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1552801
Title:
named
fixed in 1.3.0-0ubuntu4
** Changed in: python-formencode (Ubuntu)
Assignee: (unassigned) => LaMont Jones (lamont)
** Changed in: python-formencode (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
The Ubuntu (and Debian) tree for BIND includes a patch in 9.10 that
fixes this, and the bug has been filed upstream.
** Changed in: bind
Status: New => Fix Committed
** Changed in: bind9 (Ubuntu)
Assignee: (unassigned) => LaMont Jones (lamont)
** Changed in: bind
Statu
What does it say when you type:
dpkg -l | grep -ve ^ii -e ^rc
dpkg --status libgssapi-krb5-2
It may be that "apt-get install --reinstall libgssapi-krb5-2" may solve
your issue.
** Changed in: bind9 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are
The service s named "bind9", not "named"
** Changed in: bind9 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570524
Title:
/usr/sbin/named crashed while
This was fixed in 3.1.0-1
** Changed in: postfix (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1552295
Title:
Postfix 3 supports SMTPUTF8 but not
Fixed in 3.1.0-1
** Changed in: postfix
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1552295
Title:
Postfix 3 supports SMTPUTF8 but not enabled
To manage
This is in 1:9.10.3.dfsg.P4-8
** Changed in: bind9 (Ubuntu)
Status: Confirmed => 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/1565392
Title:
add support for native pkcs11
To
Fixed in python-formencode_1.3.0-0ubuntu3
** Changed in: python-formencode (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: python-formencode (Ubuntu)
Assignee: LaMont Jones (lamont) => (unassigned)
--
You received this bug notification because you are a
101 - 200 of 1183 matches
Mail list logo
