ipactl start command does rollback in case of error, i.e. the command stops all services if some error occured in start up sequence.
ipactl start
E.g.:
$ ipactl start Starting Directory Service Starting KDC Service Starting KPASSWD Service Starting DNS Service Job failed. See system journal and 'systemctl status' for details. Failed to start DNS Service Shutting down Aborting ipactl
<- At this point all service were stopped.
It would be nice to have --no-rollback option which would prevent service shutdown in case of an error.
--no-rollback
Without --no-rollback option, it is necessary to use service or systemctl commands with cryptic service names to manually start all services before you can proceed with debugging.
service
systemctl
Or maybe --force since we use that elsewhere in IPA?
May be, but --force will need one line with explanation what it does.
--force
As Ana is moving out of the team, I am moving her unresolved tickets to free-to-take pool.
Found this old patch lying on my HDD... I see that it still applies cleanly, but I haven't tested it recently Add-force-option-to-ipactl.patch
Adam can check the patch as he is looking into ipactl anyway in ticket #4050.
patch is ok, sending it to freeipa-devel after the review has been done for #4050 to avoid conflicts
master:
Metadata Update from @pspacek: - Issue assigned to amisnyov - Issue set to the milestone: FreeIPA 4.0 Backlog
Login to comment on this ticket.