On 23.9.2016 09:01, Standa Laznicka wrote:
On 09/23/2016 08:50 AM, Jan Cholasta wrote:
On 25.8.2016 15:31, Martin Basti wrote:
On 10.08.2016 07:53, Stanislav Laznicka wrote:
On 08/10/2016 07:31 AM, Jan Cholasta wrote:
On 9.8.2016 18:52, Petr Vobornik wrote:
On 08/09/2016 04:18 PM, Martin Basti wrote:
On 09.08.2016 16:07, Stanislav Laznicka wrote:
Didn't we agreed that --force-join should be always used (without
IMO the default behavior should be the same as in domain level 0 when
trying to install replica on an already enrolled host.
That was my impression as well.
OK then, I don't like to add mostly useless option, but client install
is broken by design so whatever.
Bump, what is the status of this?
FTR this is what happens on domain level 0 if the host is already
# ipa-replica-install replica-info-test.example.com.gpg
WARNING: conflicting time&date synchronization service 'chronyd' will
be disabled in favor of ntpd
Directory Manager (existing master) password:
The host test.example.com already exists on the master server.
You should remove it before proceeding:
% ipa host-del test.example.com
ipa.ipapython.install.cli.install_tool(Replica): ERROR The
ipa-replica-install command failed. See
/var/log/ipareplica-install.log for more information
There's been no status change.
I think the problem here is more about client-install advertising the
--force-join option which does not exist for ipa-replica-install. I do
not think we can detect that exactly this error occurred during
client-install being run from replica-install (can we?) but we can add
this option and pass it to client-install if required.
We could detect it before running ipa-client-install, but adding the
option to ipa-replica-install is easier, so IMO that's what we should do.
Manage your subscription for the Freeipa-devel mailing list:
Contribute to FreeIPA: http://www.freeipa.org/page/Contribute/Code