Export with "jail-whitelist" does not jail the specified validators

[njmurarka]

Summary of Bug

Relating to feature #3454, I have been trying to "upgrade" a network, by means to a JSON file and using that JSON. Indirectly related to this particular issue are #7505 and #7506.

But for starters, I need to be able to export and pre-jail all validators I will not be immediately starting up in the upgraded network.

Unfortunately, whether I provide the "jail-whitelist" command or not, the resulting JSON is the same (ignoring the creation date and time of the JSON based on when I ran the export command).

Version

Cosmos-sdk: v0.39.1
Tendermint: 0.33.7

Steps to Reproduce

I ran the following command on my chain (you can assume the valopers listed are valid ones):

blzd export --for-zero-height --jail-whitelist bluzellevaloper10ymgqrvrxq2ux5hs22v09ucut8yet05n62unyj,bluzellevaloper1p6duj9wkhtm42xx0esdq9xg7852p6tfm0rlu64

I also ran the following:

blzd export --for-zero-height

The output is the same for both.

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned

[njmurarka]

In talking to @alessio, it is established this command is a bit misleading -- this command does not jail a given list of validators.

Rather, it's job is to specify a list of validators that are ALREADY jailed (when exporting) that you wish to unjail, as part of the export. The result is that any validators in this list will be UNJAILED.

So, this command only affects validators that are already jailed, and it ensures they get unjailed. Any validators that are jailed and not in this list, remain jailed. Any validators that are not jailed, are unaffected, regardless of being in this list or not.