[COMPASS-3475] Compass is still listing deleted databases even though listDatabases does not include them Created: 28/Feb/19  Updated: 15/Dec/23

Status: Waiting (Blocked)
Project: Compass
Component/s: Connectivity, Sidebar, UI / UX
Affects Version/s: 1.16.3, 1.17.0-beta.5, 1.19.12, 1.26.0
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Nic Cottrell Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: TSPR
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Originally Ubuntu, but reproduced on Windows


Attachments: PNG File Screen Shot 2021-04-08 at 12.46.12 PM.png     PNG File pb_compass.png    
Issue Links:
Depends
Related
related to COMPASS-3760 If you drop a database the display of... Closed
related to COMPASS-5750 Investigate marking non-existent data... Waiting (Blocked)
Sprint: Iteration Antelope, Iteration Dingo

 Description   

A customer has an Atlas cluster. Some databases were deleted last year, but still appear in Compass despite clicking the refresh icon, testing 1.17 beta and clearing the ~/.config/MongoDB Compass folder.

When connecting with Mongo Shell and the same user, 

db.adminCommand( { listDatabases: 1 }

  does not show these databases.



 Comments   
Comment by Massimiliano Marcon [ 13/Mar/19 ]

This works as designed from the Compass perspective, needs to be addressed on the server (e.g. make listDatabases always possible no matter the user's permissions).

Comment by Nic Cottrell [ 01/Mar/19 ]

So it appears that Compass is seeing permissions for the authentication user referencing these databases, so it is including them in the list view even though there is no database on this particular deployment. 

Generated at Wed Feb 07 22:33:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.