Closed booxter closed 5 years ago
@fabiand I believe CI fails here b/c traviskube
is locked to 0.14.0. Please consider https://github.com/fabiand/traviskube/pull/37
/assign @fabiand
CI failures should be fixed by https://github.com/fabiand/traviskube/pull/37 that bumps kubevirt version.
ci test please
CI should be fixed by enabling software emulation: https://github.com/fabiand/traviskube/pull/39
Please rebase
This is comical now. Now it fails (in one job only) with:
Error from server (InternalError): error when creating "manifests/vm.yaml": Internal error occurred: failed calling webhook "virtualmachine-validator.kubevirt.io": Post https://virt-api.kubevirt.svc:443/virtualmachines-validate?timeout=30s: dial tcp 10.110.29.209:443: connect: connection refused
I guess we don't wait for virt-api to start and post manifest immediately? I see virt-api is ContainerCreating.
Ah. We need to wait for the operator to become functional.
Oh, we already do.
The old api for volumes results in the following error when applied:
error: unable to recognize "vm.yaml": no matches for kind "VirtualMachine" in version "kubevirt.io/v1alpha2"