Commit a61cc8cf authored by Michał Kępień's avatar Michał Kępień
Browse files

Wait until "rndc dumpdb" completes

"rndc dumpdb" works asynchronously, i.e. the requested dump may not yet
be fully written to disk by the time "rndc" returns.  Prevent false
positives for the "serve-stale" system test by only checking dump
contents after the line indicating that it is complete is written.

(cherry picked from commit 6e3f812a)
parent e677397e
Pipeline #12415 passed with stages
in 12 minutes and 26 seconds
......@@ -97,6 +97,10 @@ grep "data\.example\..*2.*IN.*TXT.*A text record with a 1 second ttl" dig.out.te
# The max-stale-ttl is 3600 seconds, so the comment should say the data is
# stale for somewhere between 3500-3599 seconds.
$RNDCCMD dumpdb > rndc.out.test$n 2>&1 || ret=1
for i in 0 1 2 3 4 5 6 7 8 9; do
grep '^; Dump complete$' ns1/named_dump1.db > /dev/null 2>&1 && break
sleep 1
awk '/; stale/ { x=$0; getline; print x, $0}' ns1/named_dump1.db |
grep "; stale (will be retained for 35.. more seconds) data\.example.*A text record with a 1 second ttl" > /dev/null 2>&1 || ret=1
# Also make sure the not expired data does not have a stale comment.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment