Tracked in Github Issues as https://github.com/canonical/cloud- init/issues/3999
** Bug watch added: github.com/canonical/cloud-init/issues #3999 https://github.com/canonical/cloud-init/issues/3999 ** Changed in: cloud-init Status: Confirmed => Expired -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1981912 Title: Gentoo no longer applying network config Status in cloud-init: Expired Bug description: It seems that cloud-init has evolved past the previous work in getting gentoo functioning on first boot. It is missing the proper renderer to configure the network on the booted machine, in this case would be "openrc". I am not good with python enough to help, but the original gentoo script in cloudinit/distros/gentoo.py looks like has mostly what is needed to get the network configured, and needs to be adapted to a network renderer. Putting this bug here to hopefully get some traction on this. stages.py[ERROR]: Unable to render networking. Network config is likely broken: No available network renderers found. Searched through list: ['eni', 'sysconfig', 'netplan', 'network-manager', 'freebsd', 'netbsd', 'openbsd', 'networkd'] To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1981912/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
