ubuntu-389-directory-server team mailing list archive

[Nic Bernstein <nic@xxxxxxxxxxx>]

Public bug reported:

Using a brand new Bionic 18.04LTS LXC container on a Bionic host, I am
unable to complete running setup-ds-admin.  When performing the exact
same sequence on the physical host it completes as expected.

When run as "setup-ds-admin -k -d" on the container, the run ends with this:
-------------------
Your new DS instance 'ds3891' was successfully created.
Creating the configuration directory server . . .
+Processing /usr/share/dirsrv/data/01nsroot.ldif.tmpl ...
+Processing /usr/share/dirsrv/data/02globalpreferences.ldif.tmpl ...
+Processing /usr/share/dirsrv/data/12dsconfig.mod.tmpl ...
+Processing /usr/share/dirsrv/data/13dsschema.mod.tmpl ...
+Processing /usr/share/dirsrv/data/14dsmonitor.mod.tmpl ...
+Processing /usr/share/dirsrv/data/16dssuffixadmin.mod.tmpl ...
Could not authenticate as user 'uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot' to server 'ldap://ds3891.example.com:389/o=NetscapeRoot'.  Error: Invalid credentials

Could not register the directory server with the configuration directory server.
Exiting . . .
-------------------
and the UserPassword entry for that user is a bogus string, unrelated to the password entered.  By that I mean that I can run the same sequence four times with different passwords (cleaning up the /etc/dirsrv/slapd-* directories in between), and the same exact string will end up stored in the UserPassword entry for that user.  The password for "cn=Directory Manager" is fine, however.

The value of admin's UserPassword will always end up being this:
userPassword:: e1NTSEE1MTJ9Y21SMUR1MER0Tk9FNWNZc1VlSTVXRHA1TlBSK2NQeGY1MlJPVTN
 GZzFLQW1zTnlQZDRQOXdNNm1YTFJSZ1V0THp0d1ZnQWFyeFc1a2s2UVRMU2s0TDZTcm1xTXkrTmEz

As noted, the same exact sequence run on the bare host (not in an LXC
container) yields expected results.

** Affects: 389-admin (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: bionic lxc

** Description changed:

  Using a brand new Bionic 18.04LTS LXC container on a Bionic host, I am
  unable to complete running setup-ds-admin.  When performing the exact
  same sequence on the physical host it completes as expected.
  
  When run as "setup-ds-admin -k -d" on the container, the run ends with this:
  -------------------
  Your new DS instance 'ds3891' was successfully created.
  Creating the configuration directory server . . .
  +Processing /usr/share/dirsrv/data/01nsroot.ldif.tmpl ...
  +Processing /usr/share/dirsrv/data/02globalpreferences.ldif.tmpl ...
  +Processing /usr/share/dirsrv/data/12dsconfig.mod.tmpl ...
  +Processing /usr/share/dirsrv/data/13dsschema.mod.tmpl ...
  +Processing /usr/share/dirsrv/data/14dsmonitor.mod.tmpl ...
  +Processing /usr/share/dirsrv/data/16dssuffixadmin.mod.tmpl ...
- Could not authenticate as user 'uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot' to server 'ldap://ds3891.occinc.com:389/o=NetscapeRoot'.  Error: Invalid credentials
+ Could not authenticate as user 'uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot' to server 'ldap://ds3891.example.com:389/o=NetscapeRoot'.  Error: Invalid credentials
  
  Could not register the directory server with the configuration directory server.
  Exiting . . .
  -------------------
  and the UserPassword entry for that user is a bogus string, unrelated to the password entered.  By that I mean that I can run the same sequence four times with different passwords (cleaning up the /etc/dirsrv/slapd-* directories in between), and the same exact string will end up stored in the UserPassword entry for that user.  The password for "cn=Directory Manager" is fine, however.
  
  The value of admin's UserPassword will always end up being this:
  userPassword:: e1NTSEE1MTJ9Y21SMUR1MER0Tk9FNWNZc1VlSTVXRHA1TlBSK2NQeGY1MlJPVTN
-  GZzFLQW1zTnlQZDRQOXdNNm1YTFJSZ1V0THp0d1ZnQWFyeFc1a2s2UVRMU2s0TDZTcm1xTXkrTmEz
+  GZzFLQW1zTnlQZDRQOXdNNm1YTFJSZ1V0THp0d1ZnQWFyeFc1a2s2UVRMU2s0TDZTcm1xTXkrTmEz
  
  As noted, the same exact sequence run on the bare host (not in an LXC
  container) yields expected results.

-- 
You received this bug notification because you are a member of Ubuntu
389 Directory Server, which is subscribed to 389-admin in Ubuntu.
https://bugs.launchpad.net/bugs/1769266

Title:
  Unable to complete setup-ds-admin when running in Bionic LXC container

Status in 389-admin package in Ubuntu:
  New

Bug description:
  Using a brand new Bionic 18.04LTS LXC container on a Bionic host, I am
  unable to complete running setup-ds-admin.  When performing the exact
  same sequence on the physical host it completes as expected.

  When run as "setup-ds-admin -k -d" on the container, the run ends with this:
  -------------------
  Your new DS instance 'ds3891' was successfully created.
  Creating the configuration directory server . . .
  +Processing /usr/share/dirsrv/data/01nsroot.ldif.tmpl ...
  +Processing /usr/share/dirsrv/data/02globalpreferences.ldif.tmpl ...
  +Processing /usr/share/dirsrv/data/12dsconfig.mod.tmpl ...
  +Processing /usr/share/dirsrv/data/13dsschema.mod.tmpl ...
  +Processing /usr/share/dirsrv/data/14dsmonitor.mod.tmpl ...
  +Processing /usr/share/dirsrv/data/16dssuffixadmin.mod.tmpl ...
  Could not authenticate as user 'uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot' to server 'ldap://ds3891.example.com:389/o=NetscapeRoot'.  Error: Invalid credentials

  Could not register the directory server with the configuration directory server.
  Exiting . . .
  -------------------
  and the UserPassword entry for that user is a bogus string, unrelated to the password entered.  By that I mean that I can run the same sequence four times with different passwords (cleaning up the /etc/dirsrv/slapd-* directories in between), and the same exact string will end up stored in the UserPassword entry for that user.  The password for "cn=Directory Manager" is fine, however.

  The value of admin's UserPassword will always end up being this:
  userPassword:: e1NTSEE1MTJ9Y21SMUR1MER0Tk9FNWNZc1VlSTVXRHA1TlBSK2NQeGY1MlJPVTN
   GZzFLQW1zTnlQZDRQOXdNNm1YTFJSZ1V0THp0d1ZnQWFyeFc1a2s2UVRMU2s0TDZTcm1xTXkrTmEz

  As noted, the same exact sequence run on the bare host (not in an LXC
  container) yields expected results.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/389-admin/+bug/1769266/+subscriptions