** Tags added: testcase
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/658227
Title:
upgrade process does not upgrade underlying BDB format from 4.7 to 4.8
(so slapd aborts with
Copied to natty as well.
** Changed in: openldap (Ubuntu Natty)
Status: Triaged = Fix Released
--
upgrade process does not upgrade underlying BDB format from 4.7 to 4.8 (so
slapd aborts with Program version 4.8 doesn't match environment version 4.7
error message)
This bug was fixed in the package openldap - 2.4.23-0ubuntu3.2
---
openldap (2.4.23-0ubuntu3.2) maverick-proposed; urgency=low
* debian/slapd.templates: re-add slapd/move_old_database template as it's
used during the package upgrade. Thanks to James Page for pointing it.
*
Yay!
Thanks guys, that was fast work.
--
upgrade process does not upgrade underlying BDB format from 4.7 to 4.8 (so
slapd aborts with Program version 4.8 doesn't match environment version 4.7
error message)
https://bugs.launchpad.net/bugs/658227
You received this bug notification because you
Tested successfully when upgrading slapd from Lucid
(slapd-2.4.21-0ubuntu5.3) - Maverick (2.4.23-0ubuntu3.2). Database
dumped, backed-up and reloaded post upgrade OK.
--
upgrade process does not upgrade underlying BDB format from 4.7 to 4.8 (so
slapd aborts with Program version 4.8 doesn't
Tested upgrade from Lucid ((slapd-2.4.21-0ubuntu5.3) - Maverick
(2.4.23-0ubuntu3) - Maverick (2.4.23-0ubuntu3.2). Manual recovery
steps as detailed in this bug still required as first step of upgrade
process left underlying database in an in-accessible state. This is the
expected behaviour in
** Tags added: verification-done
** Tags removed: verification-needed
--
upgrade process does not upgrade underlying BDB format from 4.7 to 4.8 (so
slapd aborts with Program version 4.8 doesn't match environment version 4.7
error message)
https://bugs.launchpad.net/bugs/658227
You received
Tested successfully on full upgrade from Lucid to Maverick using do-
release-upgrade -d.
--
upgrade process does not upgrade underlying BDB format from 4.7 to 4.8 (so
slapd aborts with Program version 4.8 doesn't match environment version 4.7
error message)
I have capability to easily test both a clean upgrade scenario and one
where an existing upgrade to ubuntu3 has already failed.
As soon as the package is in maverick-proposed I will pick this up.
--
upgrade process does not upgrade underlying BDB format from 4.7 to 4.8 (so
slapd aborts with
James, would you also be able to re-try an upgrade from Lucid to the
current Maverick version (slapd 2.4.23-0ubuntu3), and then confirm that
the slapcat command does fail at that point (i.e. without having done
the manually recovery steps)?
(I'd just like to be sure that once 2.4.23-0ubuntu3 is
On Fri, 2010-10-15 at 13:18 +, Nathan Stratton Treadway wrote:
James, would you also be able to re-try an upgrade from Lucid to the
current Maverick version (slapd 2.4.23-0ubuntu3), and then confirm that
the slapcat command does fail at that point (i.e. without having done
the manually
Accepted openldap into maverick-proposed, the package will build now and
be available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: openldap (Ubuntu
** Description changed:
+ IMPACT:
+ Currently all configured openldap installations being upgraded from Lucid -
Maverick will fail due to underlying database version incompatibility.
+
+ FIX:
+ slapd install/upgrade scripts already have functionality to dump existing
ldap databases and re-load
That's not unavoidable; just bump the minimum version check to the
maverick release version instead of the lucid version. New
installations of maverick will get an excess database dump/restore, but
the upgrade will be clean for everyone.
(This is what was done in the Debian package, fwiw.)
**
For natty, this should be addressed by merging the latest version of the
Debian package.
--
upgrade process does not upgrade underlying BDB format from 4.7 to 4.8 (so
slapd aborts with Program version 4.8 doesn't match environment version 4.7
error message)
On Thu, Oct 14, 2010 at 16:31:20 -, Steve Langasek wrote:
That's not unavoidable; just bump the minimum version check to the
maverick release version instead of the lucid version. New
installations of maverick will get an excess database dump/restore, but
the upgrade will be clean for
On Thu, Oct 14, 2010 at 05:32:03PM -, Nathan Stratton Treadway wrote:
On Thu, Oct 14, 2010 at 16:31:20 -, Steve Langasek wrote:
That's not unavoidable; just bump the minimum version check to the
maverick release version instead of the lucid version. New
installations of maverick
On Thu, 2010-10-14 at 16:31 +, Steve Langasek wrote:
** Also affects: openldap (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: openldap (Ubuntu Natty)
Importance: High
Assignee: James Page (james-page)
Status: In Progress
** Changed in:
Marking the lucid task invalid as this needs to be fixed in maverick.
** Also affects: openldap (Ubuntu Maverick)
Importance: Undecided
Status: New
** Changed in: openldap (Ubuntu Maverick)
Assignee: (unassigned) = James Page (james-page)
** Changed in: openldap (Ubuntu Lucid)
I've uploaded a fix to maverick-update:
--- openldap-2.4.23/debian/slapd.scripts-common
+++ openldap-2.4.23/debian/slapd.scripts-common
@@ -46,7 +46,7 @@
# Return success if yes.
# Usage: if database_format_changed; then
- if dpkg --compare-versions $OLD_VERSION lt-nl 2.4.14; then
+
On Thu, Oct 14, 2010 at 17:47:19 -, Steve Langasek wrote:
Ah, you're probably right then and I'm just
misremembering how this was
handled in Debian.
Looking through the Debian changelog, it appears that
there was a similar problem between 2.4.23-1 and 2.4.23-4.
The switch to libdb4.8 was
On Thu, Oct 14, 2010 at 19:07:47 -, Mathias Gug wrote:
+ if dpkg --compare-versions $OLD_VERSION lt-nl 2.4.23-0ubuntu3.1; then
return 0
else
That will force a database dump for every upgrade to
maverick. This is the same fix as in Debian (modulo the
package
On Thu, Oct 14, 2010 at 19:07:47 -, Mathias Gug wrote:
I've uploaded a fix to maverick-update:
How long before this new version will be available by
default for a user upgrading to Maverick?
Would it make sense to add a Maverick Release Note
mentioning this error and advising users with the
Thanks Nathan and James for the comments on ubuntu3.1.
I've uploaded a new version ubuntu3.2 to maverick-proposed.
I haven't been able to thoroughly test the ubuntu3.2 packages as my
testing environment is currently broken. Please test the ubuntu3.2
packages and report any failure in package new
** Changed in: openldap (Ubuntu)
Status: Triaged = In Progress
** Changed in: openldap (Ubuntu)
Assignee: (unassigned) = James Page (james-page)
--
upgrade process does not upgrade underlying BDB format from 4.7 to 4.8 (so
slapd aborts with Program version 4.8 doesn't match
** Branch linked: lp:~james-page/ubuntu/maverick/openldap/openldap-
fix-658227
--
upgrade process does not upgrade underlying BDB format from 4.7 to 4.8 (so
slapd aborts with Program version 4.8 doesn't match environment version 4.7
error message)
https://bugs.launchpad.net/bugs/658227
You
** Summary changed:
- upgrade process fails to upgrade underlying BDB format from 4.7 to 4.8
+ upgrade process does not upgrade underlying BDB format from 4.7 to 4.8
--
upgrade process does not upgrade underlying BDB format from 4.7 to 4.8
https://bugs.launchpad.net/bugs/658227
You received
Given that this seems to affect any system upgrading slapd from Lucid to
Maverick, I wonder if it's worth trying to get it added to the Maverick
release notes?
** Summary changed:
- upgrade process does not upgrade underlying BDB format from 4.7 to 4.8
+ upgrade process does not upgrade
** Changed in: openldap (Ubuntu)
Importance: Low = High
--
upgrade process does not upgrade underlying BDB format from 4.7 to 4.8 (so
slapd aborts with Program version 4.8 doesn't match environment version 4.7
error message)
https://bugs.launchpad.net/bugs/658227
You received this bug
29 matches
Mail list logo
