OperationFailure: not authorized on logs to execute command { createIndexes: "conversations", indexes: [ { key: { s...

[sentry-io]

Sentry Issue: RASA-OPEN-SOURCE-786

OperationFailure: not authorized on logs to execute command { createIndexes: "conversations", indexes: [ { key: { sender_id: 1 }, name: "sender_id_1" } ], lsid: { id: UUID("13ff5029-6135-4385-8e55-fe5b616c34c9") }, $db: "logs", $readPreference: { mode: "primary" } }
(16 additional frame(s) were not displayed)
...
  File "rasa/core/run.py", line 255, in load_agent_on_start
    _tracker_store = TrackerStore.create(endpoints.tracker_store, event_broker=_broker)
  File "rasa/core/tracker_store.py", line 123, in create
    return _create_from_endpoint_config(obj, domain, event_broker)
  File "rasa/core/tracker_store.py", line 1235, in _create_from_endpoint_config
    tracker_store = MongoTrackerStore(
  File "rasa/core/tracker_store.py", line 577, in __init__
    self._ensure_indices()
  File "rasa/core/tracker_store.py", line 586, in _ensure_indices
    self.conversations.create_index("sender_id")

Definition of Done

• Catch OperationalError during tracker store creation and convert to RasaException

[wochinge]

This issue is causing a lot of sentry events and should hence be prioritized

[ancalita]

@wochinge quick q: if this OperationFailure exception is caught during tracker-store creation, the exception that gets raised is a subclass of RasaException, i.e. ConnectionException - is that ok?

Otherwise since it's a PyMongo exception, it can also be caught here and re-raised as RasaException. Please let me know which approach is better.

[wochinge]

I think for the sake of a more detailed error message I'd slightly prefer option 2). Also ensure_indices is very particular for the MongoTrackerStore (unlike errors during connecting). Hence it makes probably sense dealing with it within MongoTrackerStore to avoid leaking that into other parts of the codebase.