Hello Bryce, or anyone else affected,
Accepted bind-dyndb-ldap into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/bind-dyndb-
ldap/11.2-1ubuntu0.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package
Hello Bryce, or anyone else affected,
Accepted bind-dyndb-ldap into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/bind-dyndb-
ldap/11.9-5ubuntu0.22.04.9 in a few hours, and then in the -proposed
repository.
Please help us by testing this new p
Hello Bryce, or anyone else affected,
Accepted bind-dyndb-ldap into noble-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/bind-dyndb-
ldap/11.10-6ubuntu11.24.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
3 13:20:06
-0700
bind9 (1:9.18.16-1ubuntu4) mantic; urgency=medium
* d/t/dyndb-ldap: allow writing to the dns tree (LP: #2034250)
-- Andreas Hasenack Tue, 05 Sep 2023
10:20:27 -0300
bind9 (1:9.18.16-1ubuntu3) mantic; urgency=medium
* d/t/control: exclude the i386 architectur
This was fix released for lunar on
https://launchpad.net/ubuntu/+source/bind-dyndb-ldap/11.10-4ubuntu0.1
** Changed in: bind-dyndb-ldap (Ubuntu Lunar)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to bi
This was fix released for lunar on
https://launchpad.net/ubuntu/+source/bind-dyndb-ldap/11.10-4ubuntu0.1
** Changed in: bind-dyndb-ldap (Ubuntu Lunar)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to bi
This bug is awaiting verification for a long time now, could someone
affected please perform the verification from the test plan?
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to certmonger in Ubuntu.
https://bugs.launchpad.net/bugs/1987276
Title:
** Description changed:
This bug tracks an update for the bind9 package, moving to versions:
* lunar (23.04): bind9 9.18.18
* jammy (22.04): bind9 9.18.18
* focal (20.04): bind9 9.16.43
These updates include bug fixes following the SRU policy exception
defined at https://wiki.
The dep8 tests are green.
Jammy: https://ubuntu-archive-team.ubuntu.com/proposed-
migration/jammy/update_excuses.html#bind-dyndb-ldap
Lunar: https://ubuntu-archive-team.ubuntu.com/proposed-
migration/lunar/update_excuses.html#bind-dyndb-ldap
The security team just released USN-6390-1, which is a
For the jammy verification:
DEP8 tests are green:
https://ubuntu-archive-team.ubuntu.com/proposed-migration/jammy/update_excuses.html#bind-dyndb-ldap
Package built correctly in all arches:
https://launchpad.net/ubuntu/+source/bind-dyndb-
ldap/11.9-5ubuntu0.22.04.2
And was test-installed in comme
Lunar verification
DEP8 results are green: https://ubuntu-archive-team.ubuntu.com/proposed-
migration/lunar/update_excuses.html#bind-dyndb-ldap
Build OK in all arches: https://launchpad.net/ubuntu/+source/bind-dyndb-
ldap/11.10-4ubuntu0.1
Also did a quick manual install of the proposed package:
** Description changed:
+ [ Impact ]
+
+ * An explanation of the effects of the bug on users and
+
+ * justification for backporting the fix to the stable release.
+
+ * In addition, it is helpful, but not required, to include an
+explanation of how the upload fixes this bug.
+
+ [ Test
** Description changed:
+ [ Impact ]
+
bind-dyndb-ldap breaks very frequently with bind9 updates. Both must
have DEP8 tests so these breakages can be caught before a release.
+
+ [ Test Plan ]
+
+ For both packages, the test plan consists in having the new dyndb-ldap
+ DEP8 test run and suc
Oops, this was fixed in bind9 already.
** No longer affects: bind9 (Ubuntu)
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to bind-dyndb-ldap in Ubuntu.
https://bugs.launchpad.net/bugs/2034251
Title:
Incorrect rdn in the bind9 dn entry in the DE
freeipa-
team/bind-dyndb-ldap/-/commit/6b5096776ee0502d9cac3966b6aa5f4da4cef664
** Affects: bind-dyndb-ldap (Ubuntu)
Importance: Low
Assignee: Andreas Hasenack (ahasenack)
Status: In Progress
** Affects: bind9 (Ubuntu)
Importance: Low
Assignee: Andreas Hasenack
p_bind9_dn}" read by * none
+olcAccess: {1}to dn.subtree="ou=dns,${ldap_suffix}" by
dn.exact="${ldap_bind9_dn}" write by * none
EOF
}
```
** Affects: bind-dyndb-ldap (Ubuntu)
Importance: Undecided
Assignee: Andreas Hasenack (ahasenack)
Status: In Progres
** Tags added: block-proposed-jammy block-proposed-lunar
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to bind-dyndb-ldap in Ubuntu.
https://bugs.launchpad.net/bugs/2032650
Title:
Add DEP8 tests for bind-dyndb-ldap integration
Status in bind-dy
The focal situation explained in the last comments above is still more
complicated than originally thought. Looks like bind-dyndb-ldap never
really worked in focal.
Some options:
a) fire up gdb, and see where exactly it's failing. It could be a symbol clash,
an incorrect library being linked in,
So in focal we get this missing symbol:
04-Sep-2023 14:33:22.532 failed to dynamically load instance 'ldap_zone'
driver '/usr/lib/bind/ldap.so': /usr/lib/bind/ldap.so: undefined symbol:
cfg_parse_buffer2 (failure)
That comes from the libisccfg library. If I link with it, however, we get:
04-Sep
** Changed in: bind-dyndb-ldap (Ubuntu Lunar)
Status: New => In Progress
** Changed in: bind-dyndb-ldap (Ubuntu Jammy)
Status: New => In Progress
** Changed in: bind-dyndb-ldap (Ubuntu Lunar)
Importance: Undecided => High
** Changed in: bind-dyndb-ldap (Ubuntu Jammy)
Importan
nce: Undecided
Status: New
** Also affects: bind-dyndb-ldap (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: bind-dyndb-ldap (Ubuntu Focal)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: bind-dyndb-ldap (Ubuntu Jammy)
As
Given that the soname in bind9-libs is an exact copy of the package
version, including the ubuntu suffix, it will change with even a no-
change rebuild:
$ objdump -x
usr/lib/x86_64-linux-gnu/libbind9-9.18.12-0ubuntu0.22.04.3~local1-Ubuntu.so |
grep SONAME
SONAME libbind9-9.18.12-
There is nothing to do in the bind9 package, so marking that task as
invalid. The DEP8 test was added to bind in a separate bug (#2032650).
** Changed in: bind9 (Ubuntu Mantic)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of FreeIPA,
which
Summary:
# focal
focal's src:bind-dyndb-ldap situation is more complicated, a simple
rebuild won't fix it. In focal we have two bind9 sources:
src:bind9-libs, and src:bind9, at very different versions. Focal's bind-
dyndb-ldap does not work with the version of src:bind9 shipped there,
hence src:b
; Andreas Hasenack (ahasenack)
** Changed in: bind-dyndb-ldap (Ubuntu Lunar)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to bind-dyndb-ldap in Ubuntu.
https://bugs.launchpad.net/
I verified the test results for bind-dyndb-ldap and am satisfied that
they show the executed planned test case, and that the results are
correct.
I noticed that this upload happens to (very probably) also fix bug
#1978849, which was missed in the changelog/changes file. I added a
comment to the bu
This is being fixed in bug #2003586, and the package is already in
proposed:
https://launchpad.net/ubuntu/+source/bind-dyndb-ldap/11.9-5ubuntu0.22.04.1
https://launchpad.net/ubuntu/+source/bind-dyndb-ldap/11.10-1ubuntu0.22.10.1
Unfortunately the changes file doesn't list this bug, so it won't be
I flipped the tags back to verification-needed, but this applies to
bind-dyndb-ldap, not bind (which was already released for jammy and
kinetic even).
** Tags removed: verification-done-jammy verification-done-kinetic
** Tags added: verification-needed-jammy verification-needed-kinetic
--
You re
Hi all,
what's the test plan for bind-dyndb-ldap? It's not in the bug
description. From a few comments, I see that it was just an install
test? That's a bit superficial, specially given the amount of patches
that it got. There are also no DEP8 tests, nor build-time tests.
I think we need a test r
Confirmed in bionic. This seems to be a known issue and needs further
investigation to see if it was fixed upstream of if there is a
workaround available. maybe via gss-proxy? Have to check.
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to freeipa
I'm having a hard time reproducing the bug in bionic nowadays. It feels
like a timing issue, because right after it complains about a connection
refused, I can connect just fine:
(...)
[24/28]: migrating certificate profiles to LDAP
[error] NetworkError: cannot connect to
'https://bionic-free
It's this one:
bind9 (1:9.11.3+dfsg-1ubuntu1.3) bionic; urgency=medium
[ Karl Stenerud ]
* d/p/skip-rtld-deepbind-for-dyndb.diff: fix named-pkcs11 crashing on
startup. Thanks to Petr Menšík (LP: #1769440)
-- Andreas Hasenack Wed, 10 Oct 2018 14:33:34
-0300
It's st
Uploaded to bionic unapproved, waiting for SRU team's approval.
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to freeipa in Ubuntu.
https://bugs.launchpad.net/bugs/1769440
Title:
freeipa server install fails - named-pkcs11 fails to run
Status i
I'll take care of this for bionic.
** Changed in: bind9 (Ubuntu Bionic)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: bind9 (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: bind9 (Ubuntu Bionic)
Status: Confirmed => In Pro
I don't think there is anything to do here for freeipa itself, just
bind9. Marking the freeipa task as invalid.
** Changed in: freeipa (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to freeipa in Ubuntu.
Timo, where is the patch in debian git? I'm looking at
g...@salsa.debian.org:dns-team/bind9.git (https://salsa.debian.org/dns-
team/bind9) but can't find it. It's currently at debian/1%9.11.4+dfsg-4
which is what was released last.
I also checked https://salsa.debian.org/dns-team/bind
--
You rec
I wonder if this patch shouldn't be applied only when doing the -pkcs11
rebuild
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to freeipa in Ubuntu.
https://bugs.launchpad.net/bugs/1769440
Title:
freeipa server install fails - named-pkcs11 fails
I just finished an ipa-server-install run on cosmic where I hit the
abort error. But when using the patched bind9 package from
https://launchpad.net/~kstenerud/+archive/ubuntu/bind9-rtld-
deepbind-1769440/ which has the patch from fedora and Timo, it worked.
--
You received this bug notification
** Changed in: freeipa (Ubuntu)
Status: New => Triaged
** Changed in: freeipa (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to freeipa in Ubuntu.
https://bugs.launchpad.net/bugs/1788497
Title:
Public bug reported:
The freeipa DEP8 test in cosmic are currently giving a false pass
result. See http://autopkgtest.ubuntu.com/packages/freeipa/cosmic/amd64
Here is an example:
(...)
self.start_creation(runtime=runtime)
File "/usr/lib/python2.7/dist-packages/ipaserver/install/service.py",
We can take on this.
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to freeipa in Ubuntu.
https://bugs.launchpad.net/bugs/1769440
Title:
freeipa server install fails - named-pkcs11 fails to run
Status in bind9 package in Ubuntu:
Confirmed
Stat
I think he means it was fixed with the package that Timo upload to the
ppa, not with the package in the archive.
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to freeipa in Ubuntu.
https://bugs.launchpad.net/bugs/1769440
Title:
freeipa server in
Outside of freeipa, I can get it to crash with multiple different
assertion errors, just not yet the one we get when using it with
freeipa. It doesn't look like a very robust system.
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to freeipa in Ubunt
Has anybody reproduced this on debian? I confirm it happening then
deploying freeipa, but I'm also looking at a simpler test case now.
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to freeipa in Ubuntu.
https://bugs.launchpad.net/bugs/1769440
Titl
** Changed in: bind9 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to freeipa in Ubuntu.
https://bugs.launchpad.net/bugs/1769440
Title:
freeipa server install fails - named-pkcs11 fails to run
Status in
Thanks, he definitely knows more about bind than I do :)
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to freeipa in Ubuntu.
https://bugs.launchpad.net/bugs/1769440
Title:
freeipa server install fails - named-pkcs11 fails to run
Status in bind9
I'll take a look
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to freeipa in Ubuntu.
https://bugs.launchpad.net/bugs/1769440
Title:
freeipa server install fails - named-pkcs11 fails to run
Status in bind9 package in Ubuntu:
Triaged
Status in
** Tags added: server-next
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to dogtag-pki in Ubuntu.
https://bugs.launchpad.net/bugs/1747411
Title:
Change of default database file format to SQL
Status in certmonger package in Ubuntu:
Fix Release
I'm down to this issue now:
root@freeipa:~# getcert list
Number of certificates and requests being tracked: 1.
Request ID '20180328210952':
status: CA_UNREACHABLE
ca-error: Error 77 connecting to
https://freeipa.lxd:8443/ca/agent/ca//profileReview: Problem with the SSL CA
cert (pa
So far my investigation is revolving around a java9 incompatibility,
which is the default jre/jdk in bionic.
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to freeipa in Ubuntu.
https://bugs.launchpad.net/bugs/1754936
Title:
freeipa cleint missin
I'm taking a look
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to freeipa in Ubuntu.
https://bugs.launchpad.net/bugs/1754936
Title:
freeipa cleint missing
Status in freeipa package in Ubuntu:
Confirmed
Bug description:
Cant`find freeipa p
51 matches
Mail list logo
