v0.6.410: offline commands refuse without -config when they find no state, and name where they read and write #1182
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fx15-s3dry"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Found by the post-release dogfood dry run.
cairnd migrate --to nats --dry-runran without-configon the S3 dogfood. It read the built-in defaults (/data/.cairn), found 0 documents and still printed "Result: every item can be copied."holds-confirm-emptyandrestoredhad the same blind spot: on an S3 instance they wrote to the local/data/.cairninstead of the bucket and reported success.holds-confirm-empty,restored): they refuse without-configunless the defaults' state directory already holds state.Single-instance state: <where>, andaudit-verifynames the missing-config.migrate, the member start path, and running instances all read the bucket correctly, and there is no data loss.-configin every offline example, and a troubleshooting row. CHANGELOG v0.6.410, chart appVersion v0.6.410.Severity: Medium (misleading output, and a local write on S3 instances; no data touched in the bucket).
The blind spot of fx15 in the offline commands that write single-instance state. Run without -config on an S3 instance, holds-confirm-empty wrote {} to the local /data/.cairn (the built-in defaults) instead of the bucket and reported success; restored declared into the same directory. Both now print 'Single-instance state: <where>' and, without -config, refuse with exit 2 when no state document is where the defaults point ("(no -config: the built-in defaults were read)", as the migrate dry run). A configuration-less POSIX instance whose state is at the defaults is not refused. audit-verify without -config names the missing -config instead of the posix month files.