When IPA replica or server is configured it does not check for
possibly installed client. This will cause the installation to
fail in the very end.
This patch adds a check for already configured client and suggests
removing it before server/replica installation.
Jan Zeleny jzel...@redhat.com wrote:
Jan Zelený jzel...@redhat.com wrote:
Jan Zelený jzel...@redhat.com wrote:
Rob Crittenden rcrit...@redhat.com wrote:
Jan Zelený wrote:
Rob Crittendenrcrit...@redhat.com wrote:
Jan Zelený wrote:
Loading of the schema is now performed in
On Thu, 24 Feb 2011 10:38:50 +0100
Pavel Zuna pz...@redhat.com wrote:
On 02/23/2011 11:53 PM, Simo Sorce wrote:
On Wed, 23 Feb 2011 23:41:33 +0100
Pavel Zůnapz...@redhat.com wrote:
On 2011-02-15 16:36, JR Aquino wrote:
On 2/15/11 6:52 AM, Simo Sorcesso...@redhat.com wrote:
On
We should have been doing this all along but with 389-ds-base-1.2.8.a3
we need to supply the SuitespotGroup directive in the installation
template. The 389-ds instance installation will fail otherwise, being
unable to write to /var/run/dirsrv.
ticket 1010
rob
On 02/24/2011 02:56 PM, Rob Crittenden wrote:
We should have been doing this all along but with 389-ds-base-1.2.8.a3
we need to supply the SuitespotGroup directive in the installation
template. The 389-ds instance installation will fail otherwise, being
unable to write to /var/run/dirsrv.
I updated the reolve.conf of the client machine to point to the server
and ran:
[root@vm-060 ~]# ipa-client-install --domain idm.lab.bos.redhat.com -p
admin -w freeipa4all
Discovery was successful!
Realm: IDM.LAB.BOS.REDHAT.COM
DNS Domain: idm.lab.bos.redhat.com
IPA Server:
On Thu, 24 Feb 2011 20:55:32 -0500
Adam Young ayo...@redhat.com wrote:
I updated the reolve.conf of the client machine to point to the
server and ran:
[root@vm-060 ~]# ipa-client-install --domain idm.lab.bos.redhat.com
-p admin -w freeipa4all
Discovery was successful!
Realm:
