[COMPASS-3104] Connection to cluster via mongos fails: An error occurred while loading navigation: Can't use 'local' database through mongos Created: 02/Sep/18 Updated: 10/Jan/24 Resolved: 02/Nov/18 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | Connectivity |
| Affects Version/s: | 1.15.1, 1.15.4 |
| Fix Version/s: | 1.16.0 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Brian Blevins | Assignee: | Durran Jordan |
| Resolution: | Fixed | Votes: | 7 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||
| Issue Links: |
|
||||
| Sprint: | Iteration Mango Miso, Iteration Naan, Iteration Qbert | ||||
| Description |
|
After upgrading from Compass 1.15.0 to 1.15.1 on MacOSX, I am no longer able to successfully access a MongoDB version 3.6.7 sharded cluster via the mongos router. Compass gives the following error message with the arrows beside "DBS" spinning. The same connection settings and credentials worked in version 1.15.0. > An error occurred while loading navigation: Can't use 'local' database through mongos Cluster has Username/Password authentication enabled. |
| Comments |
| Comment by Githook User [ 05/Nov/18 ] |
|
Author: {'name': 'Durran Jordan', 'email': 'durran@gmail.com', 'username': 'durran'}Message: |
| Comment by Durran Jordan [ 02/Nov/18 ] |
|
This is fixed in master and also backported to the 1.16-releases branch. 1.16.0 stable will be out Monday or Tuesday. |
| Comment by Githook User [ 02/Nov/18 ] |
|
Author: {'name': 'Durran Jordan', 'email': 'durran@gmail.com', 'username': 'durran'}Message: |
| Comment by Githook User [ 02/Nov/18 ] |
|
Author: {'name': 'Durran Jordan', 'email': 'durran@gmail.com', 'username': 'durran'}Message: |
| Comment by Githook User [ 02/Nov/18 ] |
|
Author: {'name': 'Durran Jordan', 'email': 'durran@gmail.com', 'username': 'durran'}Message: |
| Comment by Thiago T. Maia [ 22/Oct/18 ] |
|
Same issue on 1.15.4 (Community) connecting to mongos 3.2.12 |
| Comment by Marco Lanzotti [ 22/Oct/18 ] |
|
Same issue on 1.15.4 connecting to mongos 4.0.3
|
| Comment by Githook User [ 01/Oct/18 ] |
|
Author: {'name': 'Lucas Hrabovsky', 'email': 'hrabovsky.lucas@gmail.com', 'username': 'imlucas'}Message:
Rollback 4063342b1ae108c994a22a164430094e65ddb4d0 Puts mocha@3.x and tests now pass as expected.
Was only being updated before when SDAM topologyChanged fired. So initially, would always both be false until an SDAM change.
|
| Comment by Lucas Hrabovsky (Inactive) [ 28/Sep/18 ] |
|
Confirmed this has been fixed in 1.15.4. Please re-open if the problem persists. |
| Comment by Githook User [ 26/Sep/18 ] |
|
Author: {'name': 'Lucas Hrabovsky', 'email': 'hrabovsky.lucas@gmail.com', 'username': 'imlucas'}Message: Rollback 4063342b1ae108c994a22a164430094e65ddb4d0 Puts mocha@3.x and tests now pass as expected. |
| Comment by Githook User [ 20/Sep/18 ] |
|
Author: {'name': 'Lucas Hrabovsky', 'email': 'hrabovsky.lucas@gmail.com', 'username': 'imlucas'}Message: |