Page MenuHomeVyOS Platform

Cloud-init failing with “Unable to render networking” on VyOS 1.3
Needs testing, Requires assessmentPublicBUG

Description

Using a NoCloud provider on latest 1.3 branch is failing with

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

The network-config file used:

version: 2
ethernets:
  eth0:
    dhcp4: true

I also tried with a version 1 of network-config:

version: 1
config:
  - type: physical
    name: eth0
    subnets:
      - type: dhcp
  - type: physical
    name: eth1
    subnets:
      - type: static
        address: 192.168.1.1/24

but I got the same error.

More info follows:

# cat /var/log/cloud-init-output.log

Cloud-init v. 20.4-396-g3b0c82a4-1~bddeb running 'init-local' at Sat, 20 Mar 2021 22:10:48 +0000. Up 5.52 seconds.
2021-03-20 22:10:48,998 - stages.py[ERROR]: Unable to render networking. Network config is likely broken: No available network renderers found. Searched through list: ['netplan', 'eni', 'sysconfig']
Cloud-init v. 20.4-396-g3b0c82a4-1~bddeb running 'init' at Sat, 20 Mar 2021 22:10:49 +0000. Up 6.12 seconds.
ci-info: +++++++++++++++++++++++++++Net device info++++++++++++++++++++++++++++
ci-info: +--------+-------+-----------+-----------+-------+-------------------+
ci-info: | Device |   Up  |  Address  |    Mask   | Scope |     Hw-Address    |
ci-info: +--------+-------+-----------+-----------+-------+-------------------+
ci-info: |  eth0  | False |     .     |     .     |   .   | 00:15:5d:b1:6e:8c |
ci-info: |  eth1  | False |     .     |     .     |   .   | 00:15:5d:b1:6e:8d |
ci-info: |   lo   |  True | 127.0.0.1 | 255.0.0.0 |  host |         .         |
ci-info: |   lo   |  True |  ::1/128  |     .     |  host |         .         |
ci-info: +--------+-------+-----------+-----------+-------+-------------------+
ci-info: +++++++++++++++++++Route IPv6 info+++++++++++++++++++
ci-info: +-------+-------------+---------+-----------+-------+
ci-info: | Route | Destination | Gateway | Interface | Flags |
ci-info: +-------+-------------+---------+-----------+-------+
ci-info: +-------+-------------+---------+-----------+-------+
2021-03-20 22:10:49,559 - cc_resizefs_vyos.py[WARNING]: Device '/dev/overlay' did not exist. cannot resize: dev=overlay mnt_point=/ path=/usr/lib/live/mount/persistence/
Cloud-init v. 20.4-396-g3b0c82a4-1~bddeb running 'modules:config' at Sat, 20 Mar 2021 22:10:50 +0000. Up 7.09 seconds.
2021-03-20 22:10:50,674 - cc_vyos.py[ERROR]: Failed to configure domain-name: 'NoneType' object has no attribute 'group'
Cloud-init v. 20.4-396-g3b0c82a4-1~bddeb running 'modules:final' at Sat, 20 Mar 2021 22:10:51 +0000. Up 8.08 seconds.
No 'final' modules to run under section 'cloud_final_modules'
# cat /etc/os-release

PRETTY_NAME="VyOS 1.3-rolling-202103200258 (equuleus)"
NAME="VyOS"
VERSION_ID="1.3-rolling-202103200258"
VERSION="1.3-rolling-202103200258 (equuleus)"
VERSION_CODENAME=buster
ID=vyos
HOME_URL="https://vyos.io"
SUPPORT_URL="https://support.vyos.io"
BUG_REPORT_URL="https://phabricator.vyos.net"

Discussion:
https://forum.vyos.io/t/cloud-init-failing-with-unable-to-render-networking-on-1-3/6796

Details

Difficulty level
Normal (likely a few hours)
Version
1.3-rolling-202103200258 (equuleus)
Why the issue appeared?
Will be filled on close
Is it a breaking change?
Perfectly compatible

Event Timeline

zsdc changed the task status from Open to Needs testing.Tue, Apr 13, 5:28 PM
zsdc added a subscriber: zsdc.

The issue exists because the ifupdown package that is required for the eni renderer was removed by the https://github.com/vyos/vyatta-cfg-system/commit/3dd837f2d3518b7ddcf8e1ab68d8ab9f3eff0968
To not take back it again for all the platforms, the problem was resolved by the https://github.com/vyos/vyos-vm-images/commit/090e5367dc6df9b49c037e0b60f7adfafdf54a53 , so all the images created with the vyos-vm-images should not contain the problem with the renderer.

zsdc changed Difficulty level from Unknown (require assessment) to Normal (likely a few hours).Tue, Apr 13, 5:29 PM
zsdc changed Is it a breaking change? from Unspecified (possibly destroys the router) to Perfectly compatible.