Paul Gonin
Paul Gonin
I'm facing the same issue. It seems related to the image If I use the openSUSE Tumbleweed JeOS image, the following works fine ``` terraform { required_providers { libvirt =...
and I just checked http://download.opensuse.org/distribution/leap/15.4/appliances/openSUSE-Leap-15.4-JeOS.x86_64-15.4-OpenStack-Cloud-Build6.195.qcow2 and I got a 404 Refreshed the page with image links and a new image was actually available There is actually a 'Current' link to...
Rancher Desktop gets official SUSE signature Would that be required for unblocking in that case ?
If you build for arm64, could you also add s390 ?
You could also directly used qcow2 and cloud-init on OVH bare metal https://blog.ovhcloud.com/how-do-we-deploy-cloud-ready-images-on-bare-metal-servers/
The same working fine with Rancher v2.7.9 ?
the bug is present in v2.7.9, which does NOT actually support k8s 1.27
Interestingly, Kaniko is also candidate https://github.com/cncf/sandbox/issues/88
it would be nice if it worked with GL-AR300M https://www.gl-inet.com/products/gl-ar300m/#specs
Could you check with v2.8.6 as well? We're starting to have an understanding of what lead to this issue, and the change should be shared with v2.8.6