ost-pools test_1j and test_1k fail with 'test_1j returned 1' and 'test_1k returned 1', respectively, for Ubuntu 18.04 only and fails 100% of the time for Ubuntu 18.04 clients.
Both of these ost-pools tests try to create a pool using a bad format for the pool name. The creation of the pool is expected to fail and non-Ubuntu clients clean up their environment and run the next test. For Ubuntu clients, we see an error at the end of the test. Looking at the suite_log for a recent failure, with logs at https://testing.whamcloud.com/test_sets/423475d4-6661-11e9-aeec-52540065bddc , we see the following error for both tests
This error is from destroy_pool() calling ‘destroy_pool_int $fsname.$poolname’. destroy_pool() is called because we have a stack_trap in create_pool() and create_pool() is called by both tests.
There are several examples of this failure, but here are just a couple of additional links to logs