[LU-11940] init_logging needs to ensure clients are inited at all times Created: 06/Feb/19 Updated: 06/Feb/19 |
|
| Status: | Open |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.13.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Oleg Drokin | Assignee: | WC Triage |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Severity: | 3 |
| Rank (Obsolete): | 9223372036854775807 |
| Description |
|
It looks like when using local config, init_logging inits the client list in CLIENTS variable. It all works fine when tests are called directly, but if you use auster - it calls init_logging before the config file is sourced in - this sets up the YAML_LOG that makes subsequent init_logging calls made from individual test scripts to exit immediately. As such when your current config list does not create any entries in the CLIENTS variable, it would never be set and tests that depend on it will fail. One of the easy ways to see this is if you run something like auster -r replay-single --only 70f that will produce tihs sort of an output with a corresponding failure == replay-single test 70f: OSS O_DIRECT recovery with clients ======================================= 13:39:02 (1549478342) mount clients ... Bad conf mount command: opt= -o user_xattr,flock dev=oleg11-server@tcp:/lustre mnt= I suspect it might not be a bad idea to move init_clients_lists() call to be the very first thing init_logging() does before checking if it needs to exit? |