canonical / canonical/cloud-init
Gentoo no longer applying network config
- Dominant language
- Python
- Stars
- 3.8k
- Forks
- 1.1k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 18
Description
This bug was originally filed in Launchpad as [LP: #1981912](https://bugs.launchpad.net/cloud-init/+bug/1981912)
Launchpad details
affected_projects = []
assignee = None
assignee_name = None
date_closed = None
date_created = 2022-07-17T02:08:52.262346+00:00
date_fix_committed = None
date_fix_released = None
id = 1981912
importance = undecided
is_complete = False
lp_url = https://bugs.launchpad.net/cloud-init/+bug/1981912
milestone = None
owner = robtongue
owner_name = Rob Tongue
private = False
status = confirmed
submitter = robtongue
submitter_name = Rob Tongue
tags = []
duplicates = []
_Launchpad user **Rob Tongue(robtongue)** wrote on 2022-07-17T02:08:52.262346+00:00_
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']
Contributor guide
Assessment
This issue has not been assessed yet.