Whamcloud - gitweb
LU-12131 tests: properly handle GSS in server failover 41/35041/6
authorSebastien Buisson <sbuisson@ddn.com>
Mon, 3 Jun 2019 14:30:50 +0000 (23:30 +0900)
committerOleg Drokin <green@whamcloud.com>
Wed, 17 Jul 2019 06:21:33 +0000 (06:21 +0000)
commit1cbfb44fb59945da62acbb672330fde5c75ddc98
treea7dcc364c620039fcd4d8f1ed9cb8f1d258090a1
parent2dc88e46692fd75a53171548db951e7b8c5cef52
LU-12131 tests: properly handle GSS in server failover

In case of server failover, a number of aspects must be handled when
GSS based features (SSK or Kerberos) are activated:
- lsvcgssd daemon must be restarted;
- targets must be mounted with proper skpath option;
- permissions on keys must be adjusted.
When service is initially started, all that is managed in setupall().
fail() and facet_failover() have to be improved to take GSS aspects
into account.

Test-Parameters: envdefinitions=SHARED_KEY=true testlist=sanity,recovery-small,sanity-sec
Signed-off-by: Sebastien Buisson <sbuisson@ddn.com>
Change-Id: I8db686f406629c7eec655496cf83c0539c1bfb33
Reviewed-on: https://review.whamcloud.com/35041
Tested-by: jenkins <devops@whamcloud.com>
Tested-by: Maloo <maloo@whamcloud.com>
Reviewed-by: Andreas Dilger <adilger@whamcloud.com>
Reviewed-by: Wei Liu <sarah@whamcloud.com>
Reviewed-by: Oleg Drokin <green@whamcloud.com>
lustre/tests/test-framework.sh