Created attachment 1177526 [details]
Backtrace file created in abrt folder.
Description of problem: traceback message seen in ipaserver-uninstall.log.
Version-Release number of selected component (if applicable):
How reproducible: Always
Steps to Reproduce:
1. Install ipa-server on RHEL7.3 | Ensure installation is successfull.
2. echo Secret123|kinit admin
3. Now uninstall ipa-server
4. tail -f /var/log/ipaserver-uninstall.log
1. ipaserver-uninstall.log files displays traceback message.
2. Also see backtrace in /var/spool/abrt/ folder.
[root@server abrt]# ls -l
-rw-------. 1 root root 26 Jul 8 11:37 last-via-server
drwxr-x---. 2 root abrt 4096 Jul 8 11:37 Python-2016-07-05-14:26:34-27547
Traceback message should be fixed.
Attached ipaserver-uninstall.log file and backtrace file information and sosreport
Created attachment 1177527 [details]
Created attachment 1177528 [details]
ipa server uninstall log
This was added there on purpose, because there are many hidden places where sys.exit() in modules is incorrectly used from past. Without this we couldn't be able easily debug issues in installer code. It logs only as DEBUG level.
To avoid this we need refactor client and installers, but it hasn't been prioritized.
I propose wontfix for this part of BZ.
traceback reported by abrt should be fixed.
ABRT reported traceback fixed
Verified using ipa-server-4.4.0-5.el7.x86_64 on RHEL7.3
abrt report is not generated now which is the fix.
Although we can see the traceback in the ipaserver-uninstall.log file which is wontfix for this part of BZ as per comment #5.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.