449242ebda
The openstack boot test often ruins our days with: Waiting for instance 63ac19be-2e19-44e2-8bef-9770d68a190c to become Active failed: A timeout occurred I decided to investigate. It turns out the first boot of an image can take up to 18 minutes. The subsequent ones are usually much faster (but don't rely on this fact, I saw 15 minutes there). This commit bumps the timeout to 30 minutes. This should be plenty of time for the instance to spin up and get into the ACTIVE state. Honestly, I'm not very happy with the solution but it should help with the failing Schutzbot. As a follow up, I will reach to the PSI OpenStack team and ask them if we could somehow speed up the process (maybe by using another flavor, ci.m1.medium.ephemeral just might be slow for some reason, I don't know). Anyway, this should help us in the short term because I strongly believe that a slow test is still better than a failing one. Signed-off-by: Ondřej Budai <ondrej@budai.cz> |
||
|---|---|---|
| .. | ||
| azuretest | ||
| openstacktest | ||
| vmwaretest | ||
| aws.go | ||
| context-managers.go | ||
| helpers.go | ||
| netns.go | ||