From 66da715c84fadba2120a59f02b68ba92ae6807b8 Mon Sep 17 00:00:00 2001
From: Oleh Huzei <oleh.huzei@ormuco.com>
Date: Wed, 16 Oct 2019 11:32:28 -0400
Subject: [PATCH] Add release note for fix error of cron trigger run

It relates to the change I793fbfec03032d9ff7137c11becb6d1c18ec54bc,
commit 51b7dd0c6d.

Change-Id: I2571246947ab5ae06731fc7d35de7a5954325a82
(cherry picked from commit 948ceb150b66b86ba56b11821e1bb9cb8a7209cc)
---
 ...alidate_token_when_run_cron_trigger-7beffc06b75294fb.yaml | 5 +++++
 1 file changed, 5 insertions(+)
 create mode 100644 releasenotes/notes/fix_error_validate_token_when_run_cron_trigger-7beffc06b75294fb.yaml

diff --git a/releasenotes/notes/fix_error_validate_token_when_run_cron_trigger-7beffc06b75294fb.yaml b/releasenotes/notes/fix_error_validate_token_when_run_cron_trigger-7beffc06b75294fb.yaml
new file mode 100644
index 000000000..f27613128
--- /dev/null
+++ b/releasenotes/notes/fix_error_validate_token_when_run_cron_trigger-7beffc06b75294fb.yaml
@@ -0,0 +1,5 @@
+---
+fixes:
+  - |
+    Fix error validate token when run cron trigger. The problem is that a trust
+    client can't do validate token when run cron trigger.