#47483 Windows Console UI: Managing multiple instances
Closed: wontfix None Opened 10 years ago by nkinder.

In windows console there are problems managing multiple DS instances.
When trying to show basic information about the non-default instance, it takes
a lot of time to show the view and it shows wrong state of the machine.
The instance is showed to be Stopped even when it is running and is
inaccessible.

Steps to Reproduce:
1. In windows console second or further instance
2. Click on the instance in the list
3. Check the status of the instance, try to open the directory console

Actual results:
The operation takes a lot of time. Server is displayed as stopped, not
accessible.

Expected results:
The instance status is displayed correctly. Console opens Directory console
window.


Cannot reproduce the problem.

On Windows.
Started Console pointing to an admin server and Config DS running on Fedora.
Successfully created a new DS instance.
Could open the DS console for the newly created DS instance.
Did add/modify/delete user on the DS console.
They are successfully operated on the DS server on Fedora.

Metadata Update from @nhosoi:
- Issue set to the milestone: 389-admin,console 1.1.36

7 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/820

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Invalid)

3 years ago

Login to comment on this ticket.

Metadata