== sanity-sec test 300: test user_principal mount option parsing ========================================================== 23:31:39 (1788924699)
Mount with user_principal=mock_iam_test
Stopping clients: oleg231-client.virtnet /mnt/lustre (opts:)
Stopping client oleg231-client.virtnet /mnt/lustre opts:
Starting client oleg231-client.virtnet:  -o user_xattr,flock,user_principal=mock_iam_test 192.168.202.131@tcp:/lustre /mnt/lustre
Mount client oleg231-client.virtnet: mount -t lustre -o user_xattr,flock,user_principal=mock_iam_test 192.168.202.131@tcp:/lustre /mnt/lustre
Started clients oleg231-client.virtnet: 
192.168.202.131@tcp:/lustre on /mnt/lustre type lustre (rw,flock,checksum,encrypt,lazystatfs,lruresize,nolock,statfs_project,nosync_on_close,nouser_fid2path,user_principal=mock_iam_test,user_xattr,verbose)
Stopping clients: oleg231-client.virtnet /mnt/lustre (opts:)
Stopping client oleg231-client.virtnet /mnt/lustre opts:
Mount with only user_principal (should fail)
Starting client oleg231-client.virtnet:  -o user_xattr,flock,user_principal 192.168.202.131@tcp:/lustre /mnt/lustre
mount.lustre: mount 192.168.202.131@tcp:/lustre at /mnt/lustre failed: Invalid argument
This may have multiple causes.
Is 'lustre' the correct filesystem name?
Are the mount options correct?
Check the syslog for more info.
Mount client oleg231-client.virtnet: mount -t lustre -o user_xattr,flock,user_principal 192.168.202.131@tcp:/lustre /mnt/lustre
Mount failed as expected with only -o user_principal