From 855bc232e902d172b25201856388b8f045dbc405 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Fr=C3=A9d=C3=A9ric=20Danis?= <frederic.danis@collabora.com>
Date: Wed, 4 Dec 2019 11:20:05 +0100
Subject: [PATCH] apparmor: Fix apparmor-session-lockdown-no-deny test
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Fix aa_log_extract_tokens.sh path as it is intalled by
apertis-tests-apparmor-report package.

Fixes: APERTIS-6233

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>
---
 test-cases/apparmor-session-lockdown-no-deny.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/test-cases/apparmor-session-lockdown-no-deny.yaml b/test-cases/apparmor-session-lockdown-no-deny.yaml
index 428b99f..828404e 100644
--- a/test-cases/apparmor-session-lockdown-no-deny.yaml
+++ b/test-cases/apparmor-session-lockdown-no-deny.yaml
@@ -43,4 +43,4 @@ run:
     - "Now ensure AppArmor is enabled and working, by running aa-status:"
     - $ sudo aa-status
     - "Then ensure the audit log file has no AppArmor complaints:"
-    - $ sudo journalctl -b -t audit -o cat | ./aa_log_extract_tokens.sh DENIED
+    - $ sudo journalctl -b -t audit -o cat | aa_log_extract_tokens.sh DENIED
-- 
GitLab