| *** Guest6972 is now known as starkis | 09:17 | |
| hemanth1 | Hi some of the sunbeam-charms project CI functional tests are failing as the test setup launches VMs using LXD | 11:54 |
|---|---|---|
| hemanth1 | Error message: Failed creating instance record: Instance type "virtual-machine" is not supported on this server: KVM support is missing (no /dev/kvm) | 11:54 |
| hemanth1 | this is no kvm support on the machines allocated for the function test | 11:54 |
| hemanth1 | this used to be fine earlier https://zuul.opendev.org/t/openstack/builds?job_name=func-test-machine | 11:54 |
| hemanth1 | is something changed recently? Do i need to apply any specific nodeset on top of ubuntu-jammy? | 11:55 |
| frickler | hemanth1: I'm not aware of any recent change. in general using kvm in our CI is considered unstable and it would be best if you could make your jobs work without it | 12:01 |
| frickler | we do have some special nodesets where using KVM is possible, but their availability is limited and using them for gating jobs should be avoided | 12:02 |
| hemanth1 | frickler: ack | 12:02 |
| fungi | hemanth1: some of our providers are xen-based (notably, rackspace). are you trying to use nested virtualization or something? | 12:46 |
| hemanth1 | fungi: yes | 12:46 |
| fungi | yeah, you won't be able to do accelerated nesting of kvm-on-xen (nor xen-on-kvm for that matter) | 12:47 |
| hemanth1 | is it possible to set some filters on nodesets to get ubuntu-jammy and non xen-based? | 12:47 |
| fungi | also, in our experience, nested kvm-on-kvm acceleration is unreliable unless you control all three kernel versions, and we have no control over what kernels are deployed on the hypervisor hosts of public cloud providers, so have observed lots of crashing virtual machines with no way to debug without engaging the donor cloud's operators | 12:49 |
| hemanth1 | ack | 12:50 |
| fungi | we do have a nested-virt node label limiting to clouds where we think it may work okay, but make no guarantees that it will be stable and it also limits the number of available providers such that your jobs my sometimes not be able to get nodes successfully assigned, especially if one of those providers is experiencing a service outage | 12:52 |
| hemanth1 | I will check that and see how it goes | 12:52 |
| fungi | we can't really assist in debugging vm crashes on those providers, but may be able to put developers in touch with operators of those clouds who can | 12:52 |
| hemanth1 | Ok | 12:53 |
| opendevreview | Merged openstack/project-config master: Add magnum-capi-helm repo to Magnum project https://review.opendev.org/c/openstack/project-config/+/910239 | 12:55 |
| fungi | hemanth1: judging from https://opendev.org/openstack/project-config/src/branch/master/nodepool/nl02.opendev.org.yaml#L53 the label is nested-virt-ubuntu-jammy | 12:57 |
| hemanth1 | Ok I will see which jobs are using that label and how the builds against those jibs in general before using it.. | 12:58 |
| fungi | there are no predefined nodesets for that, but you can see examples of defining custom nodesets in a project, for example here's a nova job using that label: https://opendev.org/openstack/nova/src/branch/master/.zuul.yaml#L418 | 12:58 |
| fungi | codesearch.opendev.org will turn up more examples | 12:58 |
| hemanth1 | Cool thanks for all the info, helpful! | 12:59 |
| fungi | yw | 12:59 |
| fungi | hemanth1: we also have a (much more brief) disclaimer about nested virt documented in https://docs.opendev.org/opendev/infra-manual/latest/testing.html#known-differences-to-watch-out-for | 13:01 |
| opendevreview | Merged openstack/project-config master: Add op to #openstack-outreachy https://review.opendev.org/c/openstack/project-config/+/911954 | 18:42 |
| opendevreview | Jeremy Stanley proposed openstack/project-config master: Drop gating for x/networking-opencontrail https://review.opendev.org/c/openstack/project-config/+/912678 | 22:58 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!