Browse Source

Work around log file upload EPERM issue

The log files created during the Tempest run
get scp-d to their final location via Ansible.
Some root-owned log files are not readable
for the Ansible process and that results in
getting an EPERM and thus the gateway job
is qualified as UNSTABLE.

We don't have a hook in between the gluster
invocations creating those log files and the
call to the Ansible upload job, so we are not
able to chmod the logs as needed.

Instead we apply the following hack: we create
and mount a VFAT file system onto the log directory
where the trouble strikes; and VFAT does not implement
POSIX file permissions therefore all files within it
qualify as world readable.

Change-Id: I9a85888166b5b9c28a049e7c17335e2082a61f92
changes/77/302477/7
Csaba Henk 3 years ago
parent
commit
5d698eda71
1 changed files with 15 additions and 0 deletions
  1. 15
    0
      manila/post_test_hook.sh

+ 15
- 0
manila/post_test_hook.sh View File

@@ -124,3 +124,18 @@ iniset $TEMPEST_CONFIG validation network_for_ssh ${PRIVATE_NETWORK_NAME:-"priva
124 124
 
125 125
 echo "Running tempest manila test suites"
126 126
 sudo -H -u jenkins tox -eall-plugin $MANILA_TESTS -- --concurrency=$MANILA_TEMPEST_CONCURRENCY
127
+
128
+_retval=$?
129
+
130
+# This is a hack to work around EPERM issue upon
131
+# uploading log files: we ensure that the logs
132
+# shall land in a VFAT mount, whereby POSIX file
133
+# permissions are not implemented (everything is
134
+# world readable).
135
+install_package dosfstools
136
+truncate -s 3g /tmp/fat.img
137
+mkdosfs /tmp/fat.img
138
+sudo mkdir "$WORKSPACE/logs/glusterfs"
139
+sudo mount /tmp/fat.img "$WORKSPACE/logs/glusterfs"
140
+
141
+(exit $_retval)

Loading…
Cancel
Save