Red Hat Bugzilla – Bug 1024578
ipa-client-install occasionally updates ldap.conf with improper formatting
Last modified: 2014-08-05 07:18:52 EDT
Description of problem:
In one of our client tests, I occasionally see ipa-client install update ldap.conf with the line "URI ldap://ipaqa64vmc.testrelm.com". the problem is that the line is occasionally added to ldap.conf without a CR or a LF in front of the line.
I am having difficulty reproducing this problem. I only had it happen once manually when I ran "ipa-client-install --domain=testrelm.com --principal=admin --server=ipaqa64vmc.testrelm.com --password=<pw> --unattended --realm=TESTRELM.COM --fixed-primary --force --force-ntpd --hostname=ipaqavmg.testrelm.com --mkhomedir --no-dns-sshfp --noac"
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. ipa-client-install --domain=testrelm.com --principal=admin --server=ipaqa64vmc.testrelm.com --password=<pw> --unattended --realm=TESTRELM.COM --fixed-primary --force --force-ntpd --hostname=ipaqavmg.testrelm.com --mkhomedir --no-dns-sshfp --noac
:: [ 20:14:03 ] :: contents of /etc/openldap/ldap.conf
# LDAP Defaults
# See ldap.conf(5) for details
# This file should be world readable but not world writable.
#URI ldap://ldap.example.com ldap://ldap-master.example.com:666
# Turning this off breaks GSSAPI used with krb5 when rdns = false
SASL_NOCANON onURI ldap://ipaqa64vmc.testrelm.com
Expected results: I am expecting the "URI ldap://<etc>" line to be on it's own line.
I did look in the code and run the installation few times, but I was never able to reproduce. Jan, any idea what could cause this?
I am doing my best to find a way to reproduce this reliably today.
I have been trying for two hours, but I am unable to reproduce this in ipa-server-3.3.2-5.el7.x86_64
I suppose I will close this bug as "worksforme". I have tagged the QA test that was hitting this in the past. If this seems to come back, we can reopen this bug.
Michael, thanks for all the work when reproducing it. Let's resurrect this Bugzilla if we manage to find the reproducer, eventually.
I was not able to reproduce this either. I suspected that the bug would be triggered by removing trailing newline from ldap.conf, but it was not.