Add a catalog zone with an unset 'default-primaries' to the catz test

And unset 'default-primaries' is causing an assertion failure after
two reload/reconfig commands. Add such a catalog zone to check the fix.

(cherry picked from commit 40d040b7d5)
This commit is contained in:
Aram Sargsyan 2025-08-26 14:57:02 +00:00
parent 9f2b474201
commit f1a2dc10eb
4 changed files with 25 additions and 0 deletions

View file

@ -38,6 +38,15 @@ options {
view "default" {
zone "catalog0.example" {
type primary;
file "catalog0.example.db";
allow-transfer { any; };
allow-update { any; };
also-notify { 10.53.0.2; };
notify explicit;
};
zone "catalog1.example" {
type primary;
file "catalog1.example.db";

View file

@ -43,6 +43,9 @@ options {
view "default" {
catalog-zones {
zone "catalog0.example"
/* unset default-primaries, see GL#5494 */
in-memory yes;
zone "catalog1.example"
default-masters { 10.53.0.1; }
min-update-interval 1s
@ -108,6 +111,12 @@ view "default" {
forwarders { };
};
zone "catalog0.example" {
type secondary;
file "catalog0.example.db";
primaries { 10.53.0.1; };
};
zone "catalog1.example" {
type secondary;
file "catalog1.example.db";

View file

@ -55,6 +55,12 @@ view "default" {
forwarders { };
};
zone "catalog0.example" {
type secondary;
file "catalog0.example.db";
primaries { 10.53.0.1; };
};
zone "catalog1.example" {
type secondary;
file "catalog1.example.db";

View file

@ -18,6 +18,7 @@ copy_setports ns2/named1.conf.in ns2/named.conf
copy_setports ns3/named.conf.in ns3/named.conf
copy_setports ns4/named.conf.in ns4/named.conf
cp -f ns1/catalog.example.db.in ns1/catalog0.example.db
cp -f ns1/catalog.example.db.in ns1/catalog1.example.db
cp -f ns3/catalog.example.db.in ns3/catalog2.example.db
cp -f ns1/catalog.example.db.in ns1/catalog3.example.db