Thanks for using the TrueNAS Community Edition issue tracker! TrueNAS Enterprise users receive direct support for their reports from our support portal.

Legacy pool modification produces empty encryption key file

Description

I had a pool with two Vdevs (mirrors, 2 drives each) running 11.3. I upgraded to 12.0-RELEASE. I did not upgrade the pool.

I added a hot spare drive to the pool. I got the warning that the passphrase and recovery key will change. When I was done, I downloaded the "dataset_<name>_keys.json" file. I contained two bytes: "{}". I thought that since I had not actually added a Vdev, the key had not changed and so I got an empty object.

Then, I added another mirrored pair to the pool. Again, I clicked on the prompt to download the new key and, again, the file was two bytes: "{}".

I can save the configuration with "pool encryption keys" checked, but shouldn't I get something other than a pair of braces when I download the new key?

Problem/Justification

None

Impact

None

SmartDraw Connector

Katalon Manual Tests (BETA)

Activity

Show:

Bug Clerk February 1, 2021 at 4:26 PM

Bug Clerk January 31, 2021 at 1:34 PM

Frank Wayne January 29, 2021 at 6:12 PM

FWIW, I was able to reproduce the problem today with a fresh install of 11.3U1 (1 Vdev encrypted pool) that I upgraded to 12.0U1. When I add a new Vdev to the pool, I download a key containing only a pair of braces. I have the same options available in my pool settings as I have in production. That's true even if I upgrade the pool. (The pool shows "legacy encryption" even after the pool upgrade, but I assume that's expected.)

Frank Wayne January 29, 2021 at 3:39 PM
Edited

Pool data with redacted key attached.

Waqar Ahmed January 29, 2021 at 3:10 PM

Interesting, can you please share the output of `midclt call pool.query | jq .` ?

Complete
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Impact

Low

Fix versions

Affects versions

Priority

More fields

Katalon Platform

Created January 26, 2021 at 3:46 PM
Updated July 1, 2022 at 5:14 PM
Resolved February 1, 2021 at 5:20 PM