"Fix for duplicate Ignition message problem"

fixed the problem by limiting the journal output to the most recent boot - jira coreos#1033
aaradhak · Dec 15, 2021 · 2223f69 · 2223f69
1 parent 86e2bde
commit 2223f69
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/overlay.d/15fcos/usr/libexec/coreos-check-ssh-keys b/overlay.d/15fcos/usr/libexec/coreos-check-ssh-keys
@@ -11,15 +11,15 @@ main() {
     # source. It will track the authorized-ssh-keys entries in journald 
     # provided via Ignition.
     ignitionusers=$(
-            journalctl -o json-pretty MESSAGE_ID=225067b87bbd4a0cb6ab151f82fa364b | \
+            journalctl -b 0 -o json-pretty MESSAGE_ID=225067b87bbd4a0cb6ab151f82fa364b | \
             jq -r '.MESSAGE' | \
             xargs -I{} echo "Ignition: {}")
 
     # See https://github.com/coreos/afterburn/pull/397 for the MESSAGE_ID 
     # source. It will track the authorized-ssh-keys entries in journald  
     # provided via Afterburn.
     afterburnusers=$(
-            journalctl -o json-pretty MESSAGE_ID=0f7d7a502f2d433caa1323440a6b4190 | \
+            journalctl -b 0 -o json-pretty MESSAGE_ID=0f7d7a502f2d433caa1323440a6b4190 | \
             jq -r '.MESSAGE' | \
             xargs -I{} echo "Afterburn: {}")