[Bug 1962095] Re: netplan apply fails on 22.04 with clean yaml
rawad
1962095 at bugs.launchpad.net
Tue Mar 8 12:43:33 UTC 2022
Hello
i have encountered this as well on a physical server, on a vmware vm
issue does not occur, i do not specify network settings in my
autoinstall at all in general, but:
to bypass the crash (as a temporary workaround) i noticed you can make
the network section interactive by adding to your user-data file:
interactive-sections:
- network
this way you just press confirm of network settings in this step manually (without any configuration needed)
and the rest of the install continues automatically without crashing.
hope this helps you out for now.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to subiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1962095
Title:
netplan apply fails on 22.04 with clean yaml
Status in netplan.io package in Ubuntu:
Triaged
Status in subiquity package in Ubuntu:
New
Bug description:
Ubuntu 22.04 clean server iso install with default yaml using dhcp
-------------
# This is the network config written by 'subiquity'
network:
ethernets:
eno1:
dhcp4: true
enp4s0:
dhcp4: true
version: 2
-------------
netplan --debug generate is green. yaml is perfect
--------------
root at cube1:/etc/netplan# netplan --debug generate
DEBUG:command generate: running ['/lib/netplan/generate']
** (generate:65883): DEBUG: 02:01:05.691: starting new processing pass
** (generate:65883): DEBUG: 02:01:05.691: We have some netdefs, pass them through a final round of validation
** (generate:65883): DEBUG: 02:01:05.691: eno1: setting default backend to 1
** (generate:65883): DEBUG: 02:01:05.691: Configuration is valid
** (generate:65883): DEBUG: 02:01:05.691: enp4s0: setting default backend to 1
** (generate:65883): DEBUG: 02:01:05.691: Configuration is valid
** (generate:65883): DEBUG: 02:01:05.691: Generating output files..
** (generate:65883): DEBUG: 02:01:05.691: openvswitch: definition eno1 is not for us (backend 1)
** (generate:65883): DEBUG: 02:01:05.691: NetworkManager: definition eno1 is not for us (backend 1)
** (generate:65883): DEBUG: 02:01:05.691: openvswitch: definition enp4s0 is not for us (backend 1)
** (generate:65883): DEBUG: 02:01:05.691: NetworkManager: definition enp4s0 is not for us (backend 1)
----------------
execute netplan apply/try will fail
----------------
Failed to reload network settings: No such file or directory
Traceback (most recent call last):
File "/usr/sbin/netplan", line 23, in <module>
netplan.main()
File "/usr/share/netplan/netplan/cli/core.py", line 50, in main
self.run_command()
File "/usr/share/netplan/netplan/cli/utils.py", line 244, in run_command
self.func()
File "/usr/share/netplan/netplan/cli/commands/apply.py", line 61, in run
self.run_command()
File "/usr/share/netplan/netplan/cli/utils.py", line 244, in run_command
self.func()
File "/usr/share/netplan/netplan/cli/commands/apply.py", line 255, in command_apply
utils.networkctl_reconfigure(utils.networkd_interfaces())
File "/usr/share/netplan/netplan/cli/utils.py", line 103, in networkctl_reconfigure
subprocess.check_call(['networkctl', 'reload'])
File "/usr/lib/python3.9/subprocess.py", line 373, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['networkctl', 'reload']' returned non-zero exit status 1.
----------------
ubuntu forum thread:
https://ubuntuforums.org/showthread.php?t=2472318
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1962095/+subscriptions
More information about the foundations-bugs
mailing list