This is in the Load and response scenario.
This is to fix lettuce failures see on mac and debian automated lettuce
runs.
This was just a timing race.
Also I didn't check for BIND10_STARTED_CC as done elsewhere
since that never worked. I opened a ticket for that: #1900.
This fixes lettuce failure:
Scenario: Delegation query for unsigned child zone # features/queries.feature:106
Given I have bind10 running with configuration example.org.inmem.config # features/terrain/bind10_control.py:107
+ And wait for bind10 stderr message AUTH_SERVER_STARTED # features/terrain/steps.py:34
A dnssec query for www.sub.example.org type AAAA should have rcode NOERROR # features/terrain/querying.py:204
Traceback (most recent call last):
File "/usr/pkg/lib/python2.6/site-packages/lettuce/core.py", line 117, in __call__
ret = self.function(self.step, *args, **kw)
File "/home/reed/work/isc/bind10/git/bind10-CLEAN/tests/lettuce/features/terrain/querying.py", line 240, in query
"Expected: " + rcode + ", got " + query_result.rcode
AssertionError: Expected: NOERROR, got NO_ANSWER
This was discussed on jabber. (Maybe the cmdctl check is not needed,
but shouldn't hurt either.)
so that if they have nested default values, which may be set to 'local', and modified later, the original isn't changed. (technically it should be enough to do the copy when setting, but it's safer to copy them entirely for now)
They were originally planned to be enabled with the completion of this branch,
but I forgot to enable them before review. As expected, they just passed
for SQLite3, too.
As suggested in review.
This will make the caller code simpler. It's also safer in that the caller
doesn't have to manipulate the statement separetely (in the previous way
StatementProcessor and the caller could use different statements).
Also made naming more consistent: in the very initial version the class was
called "Executer" and then renamed to Processor. Some variables of this class
were still named "exec", etc, but it's more consistent if they are named
like "proc".
this was intended to be a temporary workaround while developing writability,
and should have been cleaned up in #1746. no one uses this anymore, so
we can safely remove it.
- the test zone DB was updated by hand with an NSEC3 record in the nsec3 table.
- changes to transfer.py was the same one as that in quering.py to support IPv6
transport
defined a new statement for updating the nsec3 table, and used it from
addNSEC3RecordToZone. some validation checks are still missing.
also made simple cleanup of removing unnecessary namespace qualifiers.
defining const values in a shared header file isn't illegal, but it
could cause definition bloat (it's up to the linker implementation
whether to combine them). in practice this probably doesn't matter
much for this limited scope purpose, but it's still cleaner to avoid
the bloat.
