`pdnsutil catalog set` does not warn on non-existent catalog

[jpmens]

• This is not a support question, I have read about opensource and will send support questions to the IRC channel, GitHub Discussions or the mailing list.

• I have read and understood the 'out in the open' support policy

• I have read and understood the PowerDNS AI policy

• Program: Authoritative

• Issue type: Bug report

Short description

pdnsutil catalog set doesn't warn of a non-existent catalog.

Environment

• Operating system: macOS
• Software version: 5.0.2_1
• Software source: homebrew

Steps to reproduce

Configuration file:

default-soa-content=nsa.example. noc.@ 0 10800 3600 604800 3600
default-ttl=3607
launch=gsqlite3
gsqlite3-dnssec=true
gsqlite3-database=/usr/local/etc/powerdns/pdns.sqlite3
local-address=127.0.0.2
local-port=53
log-dns-details=yes
log-dns-queries=yes
primary=yes
socket-dir=/usr/local/etc/powerdns/sockdir

$ pdnsutil catalog set b03.aa nosuchcatz
$ echo $?
0

$ pdnsutil catalog list-members nosuchcatz
Zone 'nosuchcatz' not found
$ echo $?
1

The zone I wish to add exists; if I use a nonexistent zone I see

$ pdnsutil catalog set powerdns.example nosuchcatz
No such zone powerdns.example in the database
$ echo $?
1

Expected behaviour

I expected an error diagnostic as shown with catalog list-members above.

Actual behaviour

No error and no exit code, as demonstrated above.

Possibly somewhat related to #12728