-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DNS support broken #33
Comments
Thanks for the bug report. Would you mind submitting a pull request of your DNS options handling method? Also, was it the 389 dirsrv config that wasn't removed or related processes/packages? |
The 389 dirsrv processes were still running. I'll make the patch and submit
|
Hmm....when I ran against the master branch as of today, everything seemed to work. Using the 'puppet module install' method didn't work, however. I've got another go at this, so I'll clarify and make sure nothing crazy happened. |
That kinda makes sense... We haven't fully vetted the new changes in master so I haven't released a new version to the forge. Once we're sure the changes in master work in all cases, I'll submit a new forge release. Thanks |
dcode, Thanks |
I'll try to give it a whirl sometime this week. On Tue, Mar 25, 2014 at 8:42 PM, Rob Ruma notifications@github.com wrote:
|
When configuring an IPA master server and configuring DNS, the installation fails (and gets to a pretty annoying state, honestly).
My config:
Running
puppet apply ipa-master.pp
does the normal thing, installing the necessary packages, but when/usr/sbin/ipa-server-install
is run from 'serverinstall.pp', theshellescape
function quotes the following from $dnsopt: "--setup-dns --no-forwarders". Since it is quoted,ipa-server-install
treats this as a single parameter and fails.I temporarily worked around this by replacing the
shellescape
with just ajoin
from stdlib, but it might be better to pass all these "nested" parameters as nested lists and then callflatten
just inside theshellescape
.Once I got the setup script to run correctly, it actually failed because openldap was already running from the failed attempts. I had to remove it (which "cleanup => true" didn't handle, though that is understandable) and kill the slapd processes. Then it worked like a champ.
The text was updated successfully, but these errors were encountered: