[LU-17439] Handle invalid configurations more gracefully Created: 17/Jan/24 Updated: 17/Jan/24 |
|
| Status: | Open |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Colin Faber | Assignee: | WC Triage |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Severity: | 3 |
| Rank (Obsolete): | 9223372036854775807 |
| Description |
|
As it stands today there is little or no feedback on invalid configurations which are set with setparam. We should check for invalid configuration entries when they're applied. This will likely be difficult with the current design so we'll need to look into how to address this. A recent example and common mistake is when identity_upcall set to 'none' instead of 'NONE'. This results in MDS upcall forking out to 'none' executable which obviously doesn't exist and isn't desired behavior. |