rpm-ostree/tests/vmcheck/sync.sh
Jonathan Lebon 95bc93205e vmcheck/test-basic.sh: adjust for new polkit policy
Now that we require clients to have an active session to RegisterClient,
we can't use runuser to check for non-root functionality. Add a new
vm_cmd_as() function to allow connecting as a different user. While
we're there, do some minor cleanups to consistently use `local` when
possible.

Closes: #894
Approved by: cgwalters
2017-07-27 17:10:41 +00:00

62 lines
2.0 KiB
Bash
Executable File

#!/bin/bash
set -euo pipefail
if test -z "${INSIDE_VM:-}"; then
# do this in the host
. ${commondir}/libvm.sh
vm_setup
if ! vm_ssh_wait 30; then
echo "ERROR: A running VM is required for 'make vmcheck'."
exit 1
fi
set -x
cd ${topsrcdir}
export VMCHECK_INSTTREE=${VMCHECK_INSTTREE:-$(pwd)/insttree}
# Always pull ostree from the build container; we assume development and
# testing is against git master. See also overlay.sh and build.sh.
ostree --version
for pkg in ostree{,-libs,-grub2}; do
rpm -q $pkg
# We do not have perms to read /etc/grub2 as non-root
rpm -ql $pkg | grep -v '^/etc/' | sed "s/^/+ /" > list.txt
echo "- *" >> list.txt
# In the prebuilt container case, manpages are missing. Ignore that.
# Also chown everything to writable, due to https://bugzilla.redhat.com/show_bug.cgi?id=517575
chmod -R u+w ${VMCHECK_INSTTREE}/
# The --ignore-missing-args option was added in rsync 3.1.0,
# but CentOS7 only has rsync 3.0.9. Can simulate the behavior
# with --include-from and the way we constructed list.txt.
rsync -l --include-from=list.txt / ${VMCHECK_INSTTREE}/
rm -f list.txt
done
make install DESTDIR=${VMCHECK_INSTTREE}
vm_rsync
vm_cmd env INSIDE_VM=1 /var/roothome/sync/tests/vmcheck/sync.sh
exit 0
else
# then do this in the VM
set -x
ostree admin unlock || :
# only copy /usr and /etc
rsync -rlv /var/roothome/sync/insttree/usr/ /usr/
rsync -rlv /var/roothome/sync/insttree/etc/ /etc/
restorecon -v /usr/bin/rpm-ostree
restorecon -v /usr/libexec/rpm-ostreed
mkdir -p /etc/systemd/system/rpm-ostreed.service.d
# For our test suite at least, to catch things like https://github.com/projectatomic/rpm-ostree/issues/826
cat > /etc/systemd/system/rpm-ostreed.service.d/fatal-warnings.conf << EOF
[Service]
Environment=G_DEBUG=fatal-warnings
EOF
systemctl daemon-reload
systemctl restart rpm-ostreed
fi