-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Minor
-
None
-
Affects Version/s: 4.14.1
-
Component/s: provisioning
-
None
Sometimes Google logs membership errors as DNE and sometimes as ERR. This makes the job error out, because you can set it to ignore DNE but not ERR status. The entities are always DNE. The membership ERR message is "Entity does not exist in target or cannot be found, and not creating entities" just like the DNE message, but it doesn't consider it a DNE.
Setting it to log target commands always doesn't show anything because the output is truncated. Setting it to log target commands on error doesn't show any commands in the log.