Details
-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
3
-
9223372036854775807
Description
When lnet modules haven't been loaded, lctl network down returns with "LNET unconfigure error 19" and a non-zero return code. In this case, lctl should simply return an error code of 0 and a message stating lnet is not loaded.
Logically speaking, the network is already down because lnet isn't even loaded. There are also other places in init scripts where there is an active effort to ignore the error above. Seems to me lctl should just succeed in this case.