9d9042d835
1. Don't require an ssh-config In the case of redhat-ci, the VMs are already fully configured for the system (injected in the hosts file, host key accepted, etc...). So there's no need to have an ssh-config there. In general, it should be acceptable to run the vmcheck suite against a resolvable host without having to create an ssh-config for it. 2. Make the host name configurable Rather than hardcoding "vmcheck" as the hostname, allow overridding it by specifying a VM env var directly. We also prepare the various scripts to make use of the $VM variable whenever host-specific dirs/files are created so that parallel runs won't step on each other. Closes: #675 Approved by: cgwalters
14 lines
269 B
Bash
Executable File
14 lines
269 B
Bash
Executable File
#!/bin/bash
|
|
set -euo pipefail
|
|
|
|
. ${commondir}/libvm.sh
|
|
|
|
vm_setup
|
|
|
|
if ! vm_ssh_wait 30; then
|
|
echo "WARNING: Failed to wait for VM to fetch journal" > ${JOURNAL_LOG}
|
|
else
|
|
echo "Saving ${JOURNAL_LOG}"
|
|
vm_cmd 'journalctl --no-pager || true' > ${JOURNAL_LOG}
|
|
fi
|