diff options
Diffstat (limited to 'tests')
| -rwxr-xr-x | tests/features/ssl-authz.t | 11 |
1 files changed, 9 insertions, 2 deletions
diff --git a/tests/features/ssl-authz.t b/tests/features/ssl-authz.t index 37cbbd789c0..f5cd1122332 100755 --- a/tests/features/ssl-authz.t +++ b/tests/features/ssl-authz.t @@ -52,6 +52,7 @@ TEST $CLI volume set $V0 client.ssl on #EST $CLI volume set $V0 ssl.cipher-list $(valid_ciphers) TEST $CLI volume set $V0 auth.ssl-allow Anyone TEST $CLI volume start $V0 +EXPECT_WITHIN $CHILD_UP_TIMEOUT "1" online_brick_count # This mount should WORK. TEST glusterfs --volfile-server=$H0 --volfile-id=$V0 $M0 @@ -63,6 +64,7 @@ EXPECT_WITHIN $UMOUNT_TIMEOUT "Y" force_umount $M0 TEST $CLI volume stop $V0 TEST $CLI volume set $V0 auth.ssl-allow NotYou TEST $CLI volume start $V0 +EXPECT_WITHIN $CHILD_UP_TIMEOUT "1" online_brick_count # This mount should FAIL because the identity given by our certificate does not # match the allowed user. In other words, authentication works (they know who @@ -70,7 +72,12 @@ TEST $CLI volume start $V0 TEST glusterfs --volfile-server=$H0 --volfile-id=$V0 $M0 # Looks like /*/bin/glusterfs isn't returning error status correctly (again). -# Actually try doing something to get a real error. -TEST ! ping_file $M0/after +# We may get an unusable mount where ping will fail, or no mount at all, +# where ping will write to the mount point instead of the mounted filesystem. +# In order to avoid spurious failures, create a file by ping and check it +# is absent from the brick. +ping_file $M0/after +TEST test -f $B0/1/before +TEST ! test -f $B0/1/after cleanup; |