[LU-9100] lctl network down shouldn't error with "LNET unconfigure error 19" Created: 09/Feb/17 Updated: 18/Mar/17 Resolved: 23/Feb/17 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.10.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Giuseppe Di Natale (Inactive) | Assignee: | Sonia Sharma (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | patch | ||
| Severity: | 3 |
| Rank (Obsolete): | 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. |
| Comments |
| Comment by Gerrit Updater [ 09/Feb/17 ] |
|
Giuseppe Di Natale (dinatale2@llnl.gov) uploaded a new patch: https://review.whamcloud.com/25359 |
| Comment by Peter Jones [ 10/Feb/17 ] |
|
Sonia Could you please review this proposed change? Thanks Peter |
| Comment by Gerrit Updater [ 23/Feb/17 ] |
|
Oleg Drokin (oleg.drokin@intel.com) merged in patch https://review.whamcloud.com/25359/ |
| Comment by Peter Jones [ 23/Feb/17 ] |
|
Landed for 2.10 |