Hi Petr,
On Tue, Apr 06, 2021 at 05:05:03PM +0200, Petr Šplíchal wrote:
On Tue, 6 Apr 2021 at 11:28, Coiby Xu <coxu(a)redhat.com> wrote:
> Hi Tomas,
[...]
Hi!
As for now, reboot during the test execution itself is not supported in
tmt. Here's the issue where we discuss the feature:
-
https://github.com/psss/tmt/issues/281
Reboot is possible using an ansible playbook during the prepare step:
-
https://tmt.readthedocs.io/en/latest/spec/plans.html#ansible
Sorry for not having been clear before. For now, the kdump tests will
automatically reboot the VM after finishing vmcore dumping in the
dump-capture kernel. So reboot during the test execution is not needed
currently.
What's required is if there is a way to get the console output because
the tests rely on the console output to know if the tests are successful.
However, I'm not sure this approach would be sufficient for the use case
you've described (e.g. several vm instances). I guess Miro will provide
some more details from the TFT point of view.
Yes, this is another must-have feature. Without this feature, only the
test of dumping vmcore locally can be done. Because the rest of the tests
need a second VM to act as a SSH or NFS server.