diskimage-builder/elements/yum/post-install.d/99-reset-yum-conf

#!/bin/bash

if [ ${DIB_DEBUG_TRACE:-1} -gt 0 ]; then
    set -x
fi
set -eu
set -o pipefail

sed -i 's/keepcache=1/keepcache=0/' /etc/yum.conf
sed -i 's/cachedir=\/tmp\/yum/cachedir=\/var\/cache\/yum/' /etc/yum.conf
Reset yum configuration in post-install.d When using the yum element, we should reset the changes we've made to /etc/yum.conf during post-install.d. Otherwise, this build time configuration is propagated into booted instances. Change-Id: I1eea586ca0fefe9bc0cf91fedefcbd141a536fa2 2014-09-12 00:59:50 +00:00			`#!/bin/bash`

Standarise tracing for scripts There is a wide variety of tracing options through the various shell scripts. Some use "set -eux", others explicity set xtrace and others do nothing. There is a "-x" option to bin/disk-image-create but it doesn't flow down to the many scripts it calls. This adds a global integer variable set by disk-image-create DIB_DEBUG_TRACE. All scripts have a stanza added to detect this and turn on tracing. Any other tracing methods are rolled into this. So the standard header is --- if [ "${DIB_DEBUG_TRACE:-0}" -gt 0 ]; then set -x fi set -eu set -o pipefail --- Multiple -x options can be specified to dib-create-image, which increases the value of DIB_DEBUG_TRACE. If script authors feel their script should only trace at higher levels, they should modify the "-gt" value. If they feel it should trace by default, they can modify the default value also. Changes to pachset 16 : scripts which currently trace themselves by default have retained this behaviour with DIB_DEBUG_TRACE defaulting to "1". This was done by running [1] on patch set 15. See the thread beginning at [2] dib-lint is also updated to look for the variable being matched. [1] https://gist.github.com/ianw/71bbda9e6acc74ccd0fd [2] http://lists.openstack.org/pipermail/openstack-dev/2014-November/051575.html Change-Id: I6c5a962260741dcf6f89da9a33b96372a719b7b0 2014-09-04 04:56:29 +00:00			`if [ ${DIB_DEBUG_TRACE:-1} -gt 0 ]; then`
			`set -x`
			`fi`
			`set -eu`
Reset yum configuration in post-install.d When using the yum element, we should reset the changes we've made to /etc/yum.conf during post-install.d. Otherwise, this build time configuration is propagated into booted instances. Change-Id: I1eea586ca0fefe9bc0cf91fedefcbd141a536fa2 2014-09-12 00:59:50 +00:00			`set -o pipefail`

Remove use of sudo from yum pre and post elements sudo is not needed, since in-chroot elements are run in the context of the root user. Furthermore, sudo in pre-install is problematic as sudo may not have been installed yet (imagine a debootstrap build) Change-Id: Ib5c7e176a90fe3b8fa9c3cd702d3d815df54f472 2014-11-23 17:53:38 +00:00			`sed -i 's/keepcache=1/keepcache=0/' /etc/yum.conf`
			`sed -i 's/cachedir=\/tmp\/yum/cachedir=\/var\/cache\/yum/' /etc/yum.conf`