snapshot error: unexpected server response: no schema available for ...

Issues
1

Issue Description

I’m working through migrating from v15 to v16, running a test deployment on a copy of production. I’ve completed the recovery process and have reconfigured the test deployment, with the aim of using a snapshot/apply during the production deployment.

I’ve built an object list, however I’m encountering schema definition errors:

$ stalwart-cli snapshot -k tenant role [...] dnsserver
snapshot: 72 creates, 0 singletons
{"@type":"destroy","object":"DnsServer"}
{"@type":"destroy","object":"Tenant"}
{"@type":"destroy","object":"Role"}
error: unexpected server response: no schema available for x:DnsServer

… or after including DnsServer in --allow-unresolved:

error: unexpected server response: singleton schema missing for x:BlobStore

I feel like I’ve missed something during the migration or setup, or perhaps I have data corruption issues? stalwart-cli describe DnsServer provides a definition and I’m running stalwart-cli 1.0.7 along with v16.6 of Stalwart. Any assistance on the above is most welcome.

Stalwart Version

v0.16.x

Installation Method

Docker

Database Backend

RocksDB

Blob Storage

RocksDB

Search Engine

Internal

Directory Backend

Internal

I have reviewed the documentation and FAQ and confirm that my issue is NOT addressed there.

on

I have searched this support forum (open and closed topics) and confirm this is not a duplicate.

on

I understand that topics in this category are triaged by a bot first but a human reply will follow up. If I’d prefer a human-only reply, I’ll add the no-ai tag to my topic.

on

2

Let me research this issue with the snapshot command and schema errors.

3

@helpbot what were the results of your research?

4

If I --allow-unresolved DnsServer,BlobStore,InMemoryStore,SearchStore,PublicKey the snapshot succeeds. I’m not sure if what I’m experiencing is expected? Perhaps it is for the Stores, since they are just the default definition, but DnsServer confuses me, since I have defined a server there. @helpbot

5

This has been fixed in CLI v1.0.8 (yet to be released).

6

Thank you. I’ll wait for v1.0.8.