openstack-qa-team team mailing list archive
-
openstack-qa-team team
-
Mailing list archive
-
Message #00168
Re: Issues with soft reboot
Hi David,
>From a time perspective I see what you're saying. However, there's an important bit of functionality that is getting tested here: the fact that the soft reboot works regardless of hyper visor. I've always aimed to make Tempest hyper visor agnostic, and I would be hesitant to skip a valid test case. I think it's at least worth noting down as something we can revisit later, but I think there are other areas we can improve performance in first.
Daryl
Sent from my iPad
On Jun 19, 2012, at 8:01 AM, "David Kranz" <david.kranz@xxxxxxxxxx> wrote:
> To help with the effort of making the Tempest suite run faster, we should avoid or skip the use of soft reboot in any tests, at least for now. The problem is that, according to Vish, soft reboot requires guest support. If the booted image doesn't have it, compute will wait (two minutes by default), and do a hard reboot. So right now almost all tests that do a soft reboot will take at least 150 seconds or so and will not actually be testing anything useful. There should be a soft reboot test that uses an image with guest support.
>
> -David
>
> References:
> https://bugs.launchpad.net/nova/+bug/1013747
> https://bugs.launchpad.net/tempest/+bug/1014647
>
> --
> Mailing list: https://launchpad.net/~openstack-qa-team
> Post to : openstack-qa-team@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack-qa-team
> More help : https://help.launchpad.net/ListHelp
Follow ups
References