1/ When the uninstaller is called but there is no GC, a scary message
is printed. Modify the message so that it reflects the status with no
need to raise any alarm.
2/ If the uninstaller is called on a node where the main 389ds instance
has already been uninstalled, trap the exception so that GC uninstaller
proceeds anyway.
abbra
commented
4 years ago
1/ When the uninstaller is called but there is no GC, a scary message is printed. Modify the message so that it reflects the status with no need to raise any alarm.
2/ If the uninstaller is called on a node where the main 389ds instance has already been uninstalled, trap the exception so that GC uninstaller proceeds anyway.