=== vrubiolo1 is now known as vrubiolo
=== jdoss_ is now known as jdoss
=== fyx_ is now known as fyx
[20:50] <blackboxsw> Heya falcojr & lamoura, I see in new integration_tests we can set OS_IMAGE globally, is there a way to set a custom image name for only one test?
[20:53] <blackboxsw> as in, would we be opposed to a decorator that mandates a known other image_id for that cloud?
[20:53] <blackboxsw> as in, would we be opposed to a decorator that mandates a known other image_id for that cloud test?
[20:56] <falcojr> for only a particular test? Why do you want to hard code a specific image to a test?
[21:00] <falcojr> either way, for tests that require a bit more manual setup, you can use the `session_cloud` fixture rather than the `client` fixture
[21:00] <falcojr> test_gh671.py is an example of that
[21:01] <falcojr> when you call `session_cloud.launch`, you can set `image_id` as one of the parameters
[21:01] <falcojr> blackboxsw: ^
[21:02] <blackboxsw> falcojr: thx. the reason being I know a specific public cloud image has a pre-installed older kernel and I want to test upgrade path to recent kernel.
[21:02] <falcojr> ahh, makes sense. Let me know if you need help putting that together
[21:02] <blackboxsw> I could spend time creating that image in the individual test and downgrading the kernel to watch behavior across upgrade path. But I thought started at a base image known to have an error would be a reasonable baseline
[21:03] <blackboxsw> no worries will poke around at it now, just didn't know if we have a convention like that already in int tests
[21:03] <blackboxsw> thx for the ptr
[22:24] <blackboxsw> falcojr: I think I pulled it together https://github.com/canonical/cloud-init/pull/798
[22:26] <falcojr> blackboxsw: did you forget to add the file?
[22:28] <blackboxsw> heh yes
[22:29] <blackboxsw> oh crud
[22:29] <blackboxsw> deleted it with a git reset --hard
[22:29] <blackboxsw> putting humpty back together again
[22:32] <blackboxsw> falcojr: pushed