[freeipa PR#2446][opened] Fix misleading errors during client install rollback
by rcritten
URL: https://github.com/freeipa/freeipa/pull/2446
Author: rcritten
Title: #2446: Fix misleading errors during client install rollback
Action: opened
PR body:
"""
Some incorrect errors are possible if a client installation
fails and a configuration rollback is required.
These include:
1. Unconfigured automount client failed: CalledProcessError(Command
['/usr/sbin/ipa-client-automount', '--uninstall', '--debug']
returned non-zero exit status 1: '')
Caused by check_client_configuration() not returning the correct
return value (2).
2. WARNING: Unable to revert to the pre-installation state ('authconfig'
tool has been deprecated in favor of 'authselect'). The default sssd
profile will be used instead.
The authconfig arguments would have been: authconfig --disableldap
--disablekrb5 --disablesssdauth --disablemkhomedir
If installation fails before SSSD is configured there is no state
to roll back to. Detect this condition.
3. An error occurred while removing SSSD's cache.Please remove the
cache manually by executing sssctl cache-remove -o.
Again, if SSSD is not configured yet then there is no cache to
remove. Also correct the missing space after the period.
https://pagure.io/freeipa/issue/7729
"""
To pull the PR as Git branch:
git remote add ghfreeipa https://github.com/freeipa/freeipa
git fetch ghfreeipa pull/2446/head:pr2446
git checkout pr2446
5 years, 6 months
DNS in the WebUI
by Adam Young
I wanted to float the idea of bumping DNS to a top level Menu Item in IdM.
Here is how it looks right now:
https://admiyo.fedorapeople.org/ipa/IPA-Netsvc-screenshot.png
Note that I had to know to click "Network services" in order to find DNS.
DNS is a much more important Use case than Automount, and those two use
cases do not really have anything to do with each other.
I see DNS management as one of the primary uses of IdM. The integration of
naming and certificates is a powerful story. Having DNS as anything less
than a top level menu item buries it. It makes DNS seem like an
afterthought when it should be a major driving factor.
Automount and DNS have nothing to do with each other.
Automount is an end user type workflow. It seems almost like it should be
near the user/host side of things. It really is not a network service, so
much as an autoprovisioning tool.
We can easily move DNS up one level, and leave Automount in "network
services" or, even better, rename it to "Automount" without confusing
users. Yeah, Automount does not deserve its own top level menu item, but
it is kindof a homeless waif right now. Its not like we are running out of
space on the menu.
5 years, 6 months