While testing https://github.com/teemtee/tmt/pull/1040 I ran into a couple of issues testing the qcow image produced from the centos automotive build. This happens with regular and ostree builds.
One was the prompting for a password at each step, it was unable to properly communicate using sshkeys.
tmt run -a provision --how virtual --image /root/cs9-qemu-qa-ostree.aarch64.qcow2 --arch aarch64
/var/tmp/tmt/run-004

/plan
discover
how: fmf
directory: /root/kernel-tests
path: kunit
tests: /kunit
summary: 1 test selected
provision
how: virtual
image: /root/cs9-qemu-qa-ostree.aarch64.qcow2
user: root
memory: 2048 MB
disk: 10 GB
arch: aarch64
progress: booting...
root@127.0.0.1's password:
root@127.0.0.1's password:
root@127.0.0.1's password:
root@127.0.0.1's password:
distro: CentOS Stream 9
root@127.0.0.1's password:
summary: 1 guest provisioned
prepare
root@127.0.0.1's password:
how: shell
name: Enable Centos Repos
overview: 1 script found
root@127.0.0.1's password:

And two, communication from image to outside repos was not working properly so getting curl (60) errors.

Warning: Permanently added '[127.0.0.1]:10023' (ED25519) to the list of known hosts.
error: Updating rpm-md repo 'extras-common': cannot update repo 'extras-common': Cannot prepare internal mirrorlist: Curl error (60): SSL peer certificate or SSH remote key was not OK for https://mirrors.centos.org/metalink?repo=centos-extras-sig-extras-common-9-stream&arch=aarch64&protocol=https,http [SSL certificate problem: certificate is not yet valid]; Last error: Curl error (60): SSL peer certificate or SSH remote key was not OK for https://mirrors.centos.org/metalink?repo=centos-extras-sig-extras-common-9-stream&arch=aarch64&protocol=https,http [SSL certificate problem: certificate is not yet valid]

After working with a colleague, he was able to point to what he thinks is the issue:

https://pagure.io/testcloud/blob/79c96f0544babe4e47eb7c445963d5f2aff5f47a/f/testcloud/cli.py#_45

Instructions to build image here https://sigs.centos.org/automotive/building/