freeipa.git/install/tools/ipactl, branch platform-master

Convert installation tools to platform-independent access to system services

2011-09-13T09:15:50+00:00

http://fedorahosted.org/freeipa/ticket/1605

Add common is_installed() fn, better uninstall logging, check for errors.

2011-08-29T20:50:43+00:00

The installer and ipactl used two different methods to determine
whether IPA was configured, unify them.

When uninstalling report any thing that looks suspicious and warn
that a re-install may fail. This includes any remaining 389-ds instances
and any state or files that remains after all the module uninstallers
are complete.

Add wrappers for removing files and directories to log failures.

https://fedorahosted.org/freeipa/ticket/1715

Suppress 389-ds debug output when starting services

2011-08-24T11:54:08+00:00

If the user wants the output they can pass the --debug flag to ipactl.

https://fedorahosted.org/freeipa/ticket/1402

Improve error message in ipactl

2011-08-04T06:18:18+00:00

If a hostname configured in /etc/ipa/default.conf is changed and
is different from the one stored in LDAP in cn=ipa,cn=etc,$SUFFIX
ipactl gives an unintelligible error.

This patch improves the error message and also offers a list of
configured master so that the hostname setting in IPA configuration
can be easily fixed.

https://fedorahosted.org/freeipa/ticket/1558

Verify that the hostname is fully-qualified before accessing the service information in ipactl.

2011-06-24T05:23:14+00:00

Fail gracefully if the supplied hostname isn't fully-qualified in
ipa-server-install.

ticket 1035

Let the framework be able to override the hostname.

2011-06-23T06:11:34+00:00

The hostname is passed in during the server installation. We should use
this hostname for the resulting server as well. It was being discarded
and we always used the system hostname value.

Important changes:
- configure ipa_hostname in sssd on masters
- set PKI_HOSTNAME so the hostname is passed to dogtag installer
- set the hostname when doing ldapi binds

This also reorders some things in the dogtag installer to eliminate an
unnecessary restart. We were restarting the service twice in a row with
very little time in between and this could result in a slew of reported
errors, though the server installed ok.

ticket 1052

Improve error handling and return status codes in ipactl

2011-03-07T23:16:48+00:00

There are cases when ipactl returns success even when it fails. Plus,
when the error really is detected the status codes are not LSB
compliant. This may result in consequent issues.

This patch improves error handling in ipactl and adds LSB compliant
status codes. Namely:

0   program is running or service is OK
3   program is not running
4   program or service status is unknown

for "status" action. Status code 4 is issued when IPA is not
configured to distinguish this state from not running IPA.

For other actions, the following non-zero status codes are
implemented:

1   generic or unspecified error
2   invalid or excess argument(s)
4   user had insufficient privilege
6   program is not configured

https://fedorahosted.org/freeipa/ticket/1055

Require ipactl be run as root to avoid a lot of misleading error msgs.

2011-02-15T19:21:08+00:00

Trying to run ipactl as non-root results in a slew of bogus
error messages, some of which come because dirsrv can't read certain
files as the wrong user, some based on our handling of that fact.

ticket 936

Fix return codes for ipactl

2011-02-10T18:59:03+00:00

This patch fixes ipactl to return non-zero value when something
goes wrong.

https://fedorahosted.org/freeipa/ticket/894

Make sure all DS instances are managed by ipactl

2011-01-27T22:49:30+00:00

Fixes: https://fedorahosted.org/freeipa/ticket/860