/srv/irclogs.ubuntu.com/2021/02/01/#cloud-init.txt

=== vrubiolo1 is now known as vrubiolo
=== jdoss_ is now known as jdoss
=== fyx_ is now known as fyx
blackboxswHeya 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:50
blackboxswas in, would we be opposed to a decorator that mandates a known other image_id for that cloud?20:53
blackboxswas in, would we be opposed to a decorator that mandates a known other image_id for that cloud test?20:53
falcojrfor only a particular test? Why do you want to hard code a specific image to a test?20:56
falcojreither way, for tests that require a bit more manual setup, you can use the `session_cloud` fixture rather than the `client` fixture21:00
falcojrtest_gh671.py is an example of that21:00
falcojrwhen you call `session_cloud.launch`, you can set `image_id` as one of the parameters21:01
falcojrblackboxsw: ^21:01
blackboxswfalcojr: 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
falcojrahh, makes sense. Let me know if you need help putting that together21:02
blackboxswI 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 baseline21:02
blackboxswno worries will poke around at it now, just didn't know if we have a convention like that already in int tests21:03
blackboxswthx for the ptr21:03
blackboxswfalcojr: I think I pulled it together https://github.com/canonical/cloud-init/pull/79822:24
falcojrblackboxsw: did you forget to add the file?22:26
blackboxswheh yes22:28
blackboxswoh crud22:29
blackboxswdeleted it with a git reset --hard22:29
blackboxswputting humpty back together again22:29
blackboxswfalcojr: pushed22:32

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!