Description of problem:
Not giving proper error message when trying to create new instance with same instance name/port/ssl port
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create instance with name test
2. Now again try to create new instance with same name but different ports
showing error message
'Failed to create instance!'
Should show error message with reason to fail to create new instance.
Created attachment 1614001 [details]
Screenshot containing the same intace name and port number that is already present
Created attachment 1614003 [details]
The message it is showing is "Failed to create instance!" not specifing the actual error
*** Bug 1751100 has been marked as a duplicate of this bug. ***
I see the following messages when I try to use the same port as another instance:
For non-secure port:
Error: port 389 is already in use, or missing NET_BIND_SERVICE
For secure port:
Error: secure_port 636 is already in use, or missing NET_BIND_SERVICE
Marking as VERIFIED.
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.