Details
-
Improvement
-
Resolution: Fixed
-
Minor
-
Lustre 2.9.0
-
None
-
9223372036854775807
Description
The documentation of the -d flag on lgss_sk only identifies is as setting the "Key random data source" but it also causes the shared key to be regenerated, regardless of the other flags.
When converting a server shared key to a client one, it's necessary to use the -m modification flag to change the type attribute of the key. If one uses the -d flag as well, it will rewrite the shared key portion of the keyfile as well, and this behavior is not documented anywhere. This causes errors like:
Handling sk request Decoded netstring of 653 bytes Creating credentials for target: test-MDT0000-mdc-ffff88003c228800 with nodemap: default Searching for key with description: lustre:test:default HMAC verification error: 0x60000 from peer 192.168.122.2@tcp sending reply writing message:...
It would be nice if this behavior was documented somewhere, though I personally feel like rewriting the shared key should be the sole domain of the -w flag. In any case, I thought I'd report this issue in case it trips up anyone else.