Bifrost CI job is occasionally hitting the job timeout

[Julia Kreger]

The Bifrost CI job is occasionally hitting the default CI job timeout of thirty minutes.

Above and beyond extending the timeout which is a logical first step as performance can vary, we need to look at utilizing pre-caching and potentially look at leveraging a pre-built qcow2 file.

Additionally, the largest amount of time spent during a job is the time cloud-init is spending attempting to retrieve network information. This may be solved in other ways, but should be considered as it is ultimately a core reason the job takes such a long time.

[Julia Kreger (juliaashleykreger)]

https://review.openstack.org/#/c/187067/ has been proposed.

[Julia Kreger (juliaashleykreger)]

The proposed fix, by changing the default guest OS to cirros, reduced the overall testing time by approximately 50% which has largely resolved this issue. We will continue to monitor and potentially re-open this ticket if we begin to encounter this issue again.

[Julia Kreger (juliaashleykreger)]

The remaining step will be to extend the timeout, proposed https://review.openstack.org/191104 to extend the timeout to 60 minutes.