Browse code

chown -R to ensure that stack user owns data_dir

The fix for bug #1129748 tightens some permissions on image
directories. This breaks the devstack gate jobs, which were
relying on wide-open permissions. chowning recursively should
ensure that all the directories are owned by the stack user,
so the gate tests work with tighter permissions.

Change-Id: I09be54bff6d8f9c3f7f599d6e5ada6431beb7c31

David Ripton authored on 2013/03/02 01:48:27
Showing 1 changed files
... ...
@@ -197,9 +197,7 @@ fi
197 197
 
198 198
 # Create the destination directory and ensure it is writable by the user
199 199
 sudo mkdir -p $DEST
200
-if [ ! -w $DEST ]; then
201
-    sudo chown $STACK_USER $DEST
202
-fi
200
+sudo chown -R $STACK_USER $DEST
203 201
 
204 202
 # Set ``OFFLINE`` to ``True`` to configure ``stack.sh`` to run cleanly without
205 203
 # Internet access. ``stack.sh`` must have been previously run with Internet
... ...
@@ -214,7 +212,7 @@ ERROR_ON_CLONE=`trueorfalse False $ERROR_ON_CLONE`
214 214
 # Destination path for service data
215 215
 DATA_DIR=${DATA_DIR:-${DEST}/data}
216 216
 sudo mkdir -p $DATA_DIR
217
-sudo chown $STACK_USER $DATA_DIR
217
+sudo chown -R $STACK_USER $DATA_DIR
218 218
 
219 219
 
220 220
 # Common Configuration