Error log: Collection entities does not exist. Currently in strict mode.

[AlvaroVega]

perseo.log-20200123.gz:time=2020-01-22T12:17:42.724Z | lvl=ERROR | corr=n/a | trans=n/a | op=initialRefresh | comp=perseo-fe | srv=n/a | subsrv=n/a | msg= Collection entities does not exist. Currently in strict mode.

p-fe 1.9.0 y p-core 1.4.0

[AlvaroVega]

It happens at https://github.com/telefonicaid/perseo-fe/blob/master/lib/models/entitiesStore.js#L65
which is invoked by checkNoSignal

config.orionDb = {
    url: 'mongodb://localhost:27017/orion',
    collection: 'entities',
    prefix: 'orion',
    batchSize: 500
};

Orion db.entities collection is not created by perseo-fe and may not exists when a service is deleted (but still not theirs rules).

A possible workaround could be disable strict mode since find can work with and empty collection,
but desirable a log which op, service/subservice and rule are involved.

[fgalan]

Fixed in PR #447 ? Should be closed or is there something else pending?

[AlvaroVega]

PR #447 do not solve this issue, only improve error log

[AlvaroVega]

IMHO this issue is not a bug, it is just a operational error: there are nosignal rules which were not deleted with their service.

[fgalan]

IMHO this issue is not a bug, it is just a operational error: there are nosignal rules which were not deleted with their service.

Maybe in that case the error should clearly specify the cause? I mean, instead of:

Collection entities does not exist. Currently in strict mode.

tell something like:

The following rule: {ruleName} is a no signal rule on service {service} that seems not existing in the DB

or something similar

[AlvaroVega]

Agree on #422 (comment), that's the reason for keep improving logs:
#448

[fgalan]

Is this issue closeable after PR #448 (maybe with an extra fix to the CNR to be more precise in the current line about this)?

[fgalan]

Confirmed by skype with @AlvaroVega that there are pending aspects on this issue, so it needs to be opened.