Another update: I noticed a new update available for cloud-init (cloud-init-19.1-lp151.2.6.1.x86_64.rpm) and created a new image with this rpm. The failing renderer message still occurs and the instance's network ist not configured. Zitat von Eugen Block :

Update:

I have tested several versions now, and while cloud-init version 18.4 works on a SLES15-SP1 (from Packages iso) it does not on Leap 15.1. Although the desired ip address is configured correctly the default gateway is not. I've read through several bugzilla reports with regards to cloud-init and they state that version 19.1 has also fixes for config drive issues, but I can't confirm that.

My workaround is now to use version 18.2 (from Leap 15.0) on Leap 15.1 and lock the package so we don't mess up the installation process.

We have been dealing with these issues for several years now, almost every version had some flaws so we had to stick with an older version to be able to process both metadata and config drive datasources. I could offer some testing before new versions are released, at least for those two datasources we're using, if it would help.

Regards, Eugen

Zitat von Eugen Block :

...

Hi all,

I hope this list is not dead yet ;-)

Once again I'm struggling with cloud-init, it seems like a neverending story to me. It may be related to our outdated Ocata environment.

We have two different scenarios we need to cover in our environment, instances are launched either in provider networks (with config drive) or in self-service networks where they receive their metadata from neutron metadata service.

With Leap 15 images (cloud-init version 18.2) this still worked fine for us. With a fresh Leap 15.1 (cloud-init 19.1) image it doesn't work anymore, I get this error when I launch an instance with config drive:

...

Unable to render networking. Network config is likely broken: No available network renderers found. Searched through list: ['eni', 'sysconfig', 'netplan']

We did not change anything in our cloud environment and I can't figure out what cloud-init would need in order to process the network settings via config drive.

Can anyone shed some light, please?

Thanks and best regards, Eugen

-- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org