Details
-
Bug
-
Resolution: Fixed
-
Major
-
7.1.0
-
Untriaged
-
1
-
Unknown
Description
It is very important to log 1) a system event item 2) an eventing.log system log message and 3) an Application log message - when an eventing function is auto undeployed due to RBAC authorization change (deletion of either a needed resource, role or a user).
Determining why an Eventing function was undeployed if it is critical is important we want to unambiguously identify a customer error v. a system error.
Of lesser importance is when we receive Application messages like:
2022-04-08T13:35:03.426-07:00 [INFO] {"exception":"{\n \"message\": {\n \"code\": 16,\n \"desc\": \"LCB_ERR_AUTHENTICATION_FAILURE (206): Authentication error\",\n \"name\": \"LCB_ERR_AUTHENTICATION_FAILURE\"\n },\n \"stack\": \"Error\\n at OnUpdate (test26.js:5:22)\"\n}","file":"test26.js","line":4,"srcLine":"dst_col[meta.id] = doc;","stack":"Error\n at OnUpdate (test26.js:5:22)"}
|
|
|
2022-04-08T13:34:57.957-07:00 [INFO] {"count":3,"exception":"{\n \"message\": {\n \"code\": 16,\n \"desc\": \"LCB_ERR_AUTHENTICATION_FAILURE (206): Authentication error\",\n \"name\": \"LCB_ERR_AUTHENTICATION_FAILURE\"\n },\n \"stack\": \"Error\\n at OnUpdate (test26.js:5:22)\"\n}","file":"test26.js","line":4,"since":"2022-04-08T13:34:23","srcLine":"dst_col[meta.id] = doc;","stack":"Error\n at OnUpdate (test26.js:5:22)"}
|
in which we could expedite the 1 minute RBAC check due to seeing LCB_ERR_AUTHENTICATION_FAILURE in the Application log and undeploy the non-authorized function sooner.
Note when we don't have proper RBAC the Evening system almost stalls but does make some slow progress pegging the "failure" counts in the UI.
Attachments
Issue Links
- is a backport of
-
-
- Resolved
-