| 2022-07-26 15:45:29 |
Chad Smith |
bug |
|
|
added bug |
| 2022-07-26 15:52:58 |
Chad Smith |
description |
In this ephemeral install envivironment, the Ubuntu desktop installer prefers to setup NetworkManager for network configuration due to the file
cat /etc/netplan/01-network-manager-all.yaml:
# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: NetworkManager
But cloud-init package default configuration sets network renders to:
grep -B 1 renderers /etc/cloud/cloud.cfg
network:
renderers: ['netplan', 'eni', 'sysconfig']
You can see cloud-init tring to render netplan files by default in /var/log/cloud-init.log:
egrep 'netplan|network-manager' /var/log/cloud-init.log
...
Selected renderer 'netplan' from priority list: ['netplan', 'eni', 'sysconfig']
...
Since Desktop ephemeral environment prefers NetworkManager to render network, it should change the default network renderers configured for cloud-init with a supplemental cloud config file
cat > /etc/cloud/cloud.cfg.d/99-installer-use-networkmanager.cfg <<EOF
system_info:
network:
renderers: ['network-manager']
EOF |
In this ephemeral install envivironment, the Ubuntu desktop installer prefers to setup NetworkManager for network configuration due to the file
cat /etc/netplan/01-network-manager-all.yaml:
# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: NetworkManager
But cloud-init package default configuration sets network renders to:
grep -B 1 renderers /etc/cloud/cloud.cfg
network:
renderers: ['netplan', 'eni', 'sysconfig']
You can see cloud-init tring to render netplan files by default in /var/log/cloud-init.log:
egrep 'netplan|network-manager' /var/log/cloud-init.log
...
2022-07-26 15:43:12,972 - __init__.py[DEBUG]: Selected renderer 'netplan' from priority list: ['netplan', 'eni', 'sysconfig']
2022-07-26 15:43:12,972 - netplan.py[DEBUG]: V2 to V2 passthrough
2022-07-26 15:43:12,972 - util.py[DEBUG]: Writing to /etc/netplan/50-cloud-init.yaml - wb: [644] 491 bytes
2022-07-26 15:43:12,972 - subp.py[DEBUG]: Running command ['netplan', 'generate'] with allowed return codes [0] (shell=False, capture=True)
2022-07-26 15:43:26,106 - __init__.py[DEBUG]: Selected renderer 'netplan' from priority list: ['netplan', 'eni', 'sysconfig']
2022-07-26 15:43:26,106 - netplan.py[DEBUG]: V2 to V2 passthrough
2022-07-26 15:43:26,107 - util.py[DEBUG]: Writing to /etc/netplan/50-cloud-init.yaml - wb: [644] 491 bytes
2022-07-26 15:43:26,107 - subp.py[DEBUG]: Running command ['netplan', 'generate'] with allowed return codes [0] (shell=False, capture=True)
2022-07-26 15:43:26,166 - activators.py[DEBUG]: Attempting command ['netplan', 'apply'] for device all
2022-07-26 15:43:26,166 - subp.py[DEBUG]: Running command ['netplan', 'apply'] with allowed return codes [0] (shell=False, capture=True)
...
Since Desktop ephemeral environment prefers NetworkManager to render network, it should change the default network renderers configured for cloud-init with a supplemental cloud config file
cat > /etc/cloud/cloud.cfg.d/99-installer-use-networkmanager.cfg <<EOF
system_info:
network:
renderers: ['network-manager']
EOF |
|
| 2022-07-26 15:53:07 |
Chad Smith |
description |
In this ephemeral install envivironment, the Ubuntu desktop installer prefers to setup NetworkManager for network configuration due to the file
cat /etc/netplan/01-network-manager-all.yaml:
# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: NetworkManager
But cloud-init package default configuration sets network renders to:
grep -B 1 renderers /etc/cloud/cloud.cfg
network:
renderers: ['netplan', 'eni', 'sysconfig']
You can see cloud-init tring to render netplan files by default in /var/log/cloud-init.log:
egrep 'netplan|network-manager' /var/log/cloud-init.log
...
2022-07-26 15:43:12,972 - __init__.py[DEBUG]: Selected renderer 'netplan' from priority list: ['netplan', 'eni', 'sysconfig']
2022-07-26 15:43:12,972 - netplan.py[DEBUG]: V2 to V2 passthrough
2022-07-26 15:43:12,972 - util.py[DEBUG]: Writing to /etc/netplan/50-cloud-init.yaml - wb: [644] 491 bytes
2022-07-26 15:43:12,972 - subp.py[DEBUG]: Running command ['netplan', 'generate'] with allowed return codes [0] (shell=False, capture=True)
2022-07-26 15:43:26,106 - __init__.py[DEBUG]: Selected renderer 'netplan' from priority list: ['netplan', 'eni', 'sysconfig']
2022-07-26 15:43:26,106 - netplan.py[DEBUG]: V2 to V2 passthrough
2022-07-26 15:43:26,107 - util.py[DEBUG]: Writing to /etc/netplan/50-cloud-init.yaml - wb: [644] 491 bytes
2022-07-26 15:43:26,107 - subp.py[DEBUG]: Running command ['netplan', 'generate'] with allowed return codes [0] (shell=False, capture=True)
2022-07-26 15:43:26,166 - activators.py[DEBUG]: Attempting command ['netplan', 'apply'] for device all
2022-07-26 15:43:26,166 - subp.py[DEBUG]: Running command ['netplan', 'apply'] with allowed return codes [0] (shell=False, capture=True)
...
Since Desktop ephemeral environment prefers NetworkManager to render network, it should change the default network renderers configured for cloud-init with a supplemental cloud config file
cat > /etc/cloud/cloud.cfg.d/99-installer-use-networkmanager.cfg <<EOF
system_info:
network:
renderers: ['network-manager']
EOF |
In this ephemeral install envivironment, the Ubuntu desktop installer prefers to setup NetworkManager for network configuration due to the file
cat /etc/netplan/01-network-manager-all.yaml:
# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: NetworkManager
But cloud-init package default configuration sets network renders to:
grep -B 1 renderers /etc/cloud/cloud.cfg
network:
renderers: ['netplan', 'eni', 'sysconfig']
You can see cloud-init trying to render netplan files by default in /var/log/cloud-init.log:
egrep 'netplan|network-manager' /var/log/cloud-init.log
...
2022-07-26 15:43:12,972 - __init__.py[DEBUG]: Selected renderer 'netplan' from priority list: ['netplan', 'eni', 'sysconfig']
2022-07-26 15:43:12,972 - netplan.py[DEBUG]: V2 to V2 passthrough
2022-07-26 15:43:12,972 - util.py[DEBUG]: Writing to /etc/netplan/50-cloud-init.yaml - wb: [644] 491 bytes
2022-07-26 15:43:12,972 - subp.py[DEBUG]: Running command ['netplan', 'generate'] with allowed return codes [0] (shell=False, capture=True)
2022-07-26 15:43:26,106 - __init__.py[DEBUG]: Selected renderer 'netplan' from priority list: ['netplan', 'eni', 'sysconfig']
2022-07-26 15:43:26,106 - netplan.py[DEBUG]: V2 to V2 passthrough
2022-07-26 15:43:26,107 - util.py[DEBUG]: Writing to /etc/netplan/50-cloud-init.yaml - wb: [644] 491 bytes
2022-07-26 15:43:26,107 - subp.py[DEBUG]: Running command ['netplan', 'generate'] with allowed return codes [0] (shell=False, capture=True)
2022-07-26 15:43:26,166 - activators.py[DEBUG]: Attempting command ['netplan', 'apply'] for device all
2022-07-26 15:43:26,166 - subp.py[DEBUG]: Running command ['netplan', 'apply'] with allowed return codes [0] (shell=False, capture=True)
...
Since Desktop ephemeral environment prefers NetworkManager to render network, it should change the default network renderers configured for cloud-init with a supplemental cloud config file
cat > /etc/cloud/cloud.cfg.d/99-installer-use-networkmanager.cfg <<EOF
system_info:
network:
renderers: ['network-manager']
EOF |
|
| 2022-07-26 15:54:55 |
Chad Smith |
description |
In this ephemeral install envivironment, the Ubuntu desktop installer prefers to setup NetworkManager for network configuration due to the file
cat /etc/netplan/01-network-manager-all.yaml:
# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: NetworkManager
But cloud-init package default configuration sets network renders to:
grep -B 1 renderers /etc/cloud/cloud.cfg
network:
renderers: ['netplan', 'eni', 'sysconfig']
You can see cloud-init trying to render netplan files by default in /var/log/cloud-init.log:
egrep 'netplan|network-manager' /var/log/cloud-init.log
...
2022-07-26 15:43:12,972 - __init__.py[DEBUG]: Selected renderer 'netplan' from priority list: ['netplan', 'eni', 'sysconfig']
2022-07-26 15:43:12,972 - netplan.py[DEBUG]: V2 to V2 passthrough
2022-07-26 15:43:12,972 - util.py[DEBUG]: Writing to /etc/netplan/50-cloud-init.yaml - wb: [644] 491 bytes
2022-07-26 15:43:12,972 - subp.py[DEBUG]: Running command ['netplan', 'generate'] with allowed return codes [0] (shell=False, capture=True)
2022-07-26 15:43:26,106 - __init__.py[DEBUG]: Selected renderer 'netplan' from priority list: ['netplan', 'eni', 'sysconfig']
2022-07-26 15:43:26,106 - netplan.py[DEBUG]: V2 to V2 passthrough
2022-07-26 15:43:26,107 - util.py[DEBUG]: Writing to /etc/netplan/50-cloud-init.yaml - wb: [644] 491 bytes
2022-07-26 15:43:26,107 - subp.py[DEBUG]: Running command ['netplan', 'generate'] with allowed return codes [0] (shell=False, capture=True)
2022-07-26 15:43:26,166 - activators.py[DEBUG]: Attempting command ['netplan', 'apply'] for device all
2022-07-26 15:43:26,166 - subp.py[DEBUG]: Running command ['netplan', 'apply'] with allowed return codes [0] (shell=False, capture=True)
...
Since Desktop ephemeral environment prefers NetworkManager to render network, it should change the default network renderers configured for cloud-init with a supplemental cloud config file
cat > /etc/cloud/cloud.cfg.d/99-installer-use-networkmanager.cfg <<EOF
system_info:
network:
renderers: ['network-manager']
EOF |
In this ephemeral install environment, the Ubuntu desktop installer prefers to setup NetworkManager for network configuration due to the file
cat /etc/netplan/01-network-manager-all.yaml:
# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: NetworkManager
But cloud-init package default configuration sets network renderers to netplan:
grep -B 1 renderers /etc/cloud/cloud.cfg
network:
renderers: ['netplan', 'eni', 'sysconfig']
This results in cloud-init writing discovered network configuration to files netplan that will not be applied to the ephemeral system during boot which will break some potential custom install paths or cloud-init datasource overrides in the emphemeral desktop install environment.
You can see cloud-init trying to render netplan files by default in /var/log/cloud-init.log:
egrep 'netplan|network-manager' /var/log/cloud-init.log
...
2022-07-26 15:43:12,972 - __init__.py[DEBUG]: Selected renderer 'netplan' from priority list: ['netplan', 'eni', 'sysconfig']
2022-07-26 15:43:12,972 - netplan.py[DEBUG]: V2 to V2 passthrough
2022-07-26 15:43:12,972 - util.py[DEBUG]: Writing to /etc/netplan/50-cloud-init.yaml - wb: [644] 491 bytes
2022-07-26 15:43:12,972 - subp.py[DEBUG]: Running command ['netplan', 'generate'] with allowed return codes [0] (shell=False, capture=True)
2022-07-26 15:43:26,106 - __init__.py[DEBUG]: Selected renderer 'netplan' from priority list: ['netplan', 'eni', 'sysconfig']
2022-07-26 15:43:26,106 - netplan.py[DEBUG]: V2 to V2 passthrough
2022-07-26 15:43:26,107 - util.py[DEBUG]: Writing to /etc/netplan/50-cloud-init.yaml - wb: [644] 491 bytes
2022-07-26 15:43:26,107 - subp.py[DEBUG]: Running command ['netplan', 'generate'] with allowed return codes [0] (shell=False, capture=True)
2022-07-26 15:43:26,166 - activators.py[DEBUG]: Attempting command ['netplan', 'apply'] for device all
2022-07-26 15:43:26,166 - subp.py[DEBUG]: Running command ['netplan', 'apply'] with allowed return codes [0] (shell=False, capture=True)
...
Since Desktop ephemeral environment prefers NetworkManager to render network, it should change the default network renderers configured for cloud-init with a supplemental cloud config file
cat > /etc/cloud/cloud.cfg.d/99-installer-use-networkmanager.cfg <<EOF
system_info:
network:
renderers: ['network-manager']
EOF |
|
| 2022-07-26 15:55:13 |
Chad Smith |
description |
In this ephemeral install environment, the Ubuntu desktop installer prefers to setup NetworkManager for network configuration due to the file
cat /etc/netplan/01-network-manager-all.yaml:
# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: NetworkManager
But cloud-init package default configuration sets network renderers to netplan:
grep -B 1 renderers /etc/cloud/cloud.cfg
network:
renderers: ['netplan', 'eni', 'sysconfig']
This results in cloud-init writing discovered network configuration to files netplan that will not be applied to the ephemeral system during boot which will break some potential custom install paths or cloud-init datasource overrides in the emphemeral desktop install environment.
You can see cloud-init trying to render netplan files by default in /var/log/cloud-init.log:
egrep 'netplan|network-manager' /var/log/cloud-init.log
...
2022-07-26 15:43:12,972 - __init__.py[DEBUG]: Selected renderer 'netplan' from priority list: ['netplan', 'eni', 'sysconfig']
2022-07-26 15:43:12,972 - netplan.py[DEBUG]: V2 to V2 passthrough
2022-07-26 15:43:12,972 - util.py[DEBUG]: Writing to /etc/netplan/50-cloud-init.yaml - wb: [644] 491 bytes
2022-07-26 15:43:12,972 - subp.py[DEBUG]: Running command ['netplan', 'generate'] with allowed return codes [0] (shell=False, capture=True)
2022-07-26 15:43:26,106 - __init__.py[DEBUG]: Selected renderer 'netplan' from priority list: ['netplan', 'eni', 'sysconfig']
2022-07-26 15:43:26,106 - netplan.py[DEBUG]: V2 to V2 passthrough
2022-07-26 15:43:26,107 - util.py[DEBUG]: Writing to /etc/netplan/50-cloud-init.yaml - wb: [644] 491 bytes
2022-07-26 15:43:26,107 - subp.py[DEBUG]: Running command ['netplan', 'generate'] with allowed return codes [0] (shell=False, capture=True)
2022-07-26 15:43:26,166 - activators.py[DEBUG]: Attempting command ['netplan', 'apply'] for device all
2022-07-26 15:43:26,166 - subp.py[DEBUG]: Running command ['netplan', 'apply'] with allowed return codes [0] (shell=False, capture=True)
...
Since Desktop ephemeral environment prefers NetworkManager to render network, it should change the default network renderers configured for cloud-init with a supplemental cloud config file
cat > /etc/cloud/cloud.cfg.d/99-installer-use-networkmanager.cfg <<EOF
system_info:
network:
renderers: ['network-manager']
EOF |
In this ephemeral install environment, the Ubuntu desktop installer prefers to setup NetworkManager for network configuration due to the file
cat /etc/netplan/01-network-manager-all.yaml:
# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: NetworkManager
But cloud-init package default configuration sets network renderers to netplan:
grep -B 1 renderers /etc/cloud/cloud.cfg
network:
renderers: ['netplan', 'eni', 'sysconfig']
This results in cloud-init writing discovered network configuration to netplan files which will not be applied to the ephemeral system during boot which will break some potential custom install paths or cloud-init datasource overrides in the emphemeral desktop install environment.
You can see cloud-init trying to render netplan files by default in /var/log/cloud-init.log:
egrep 'netplan|network-manager' /var/log/cloud-init.log
...
2022-07-26 15:43:12,972 - __init__.py[DEBUG]: Selected renderer 'netplan' from priority list: ['netplan', 'eni', 'sysconfig']
2022-07-26 15:43:12,972 - netplan.py[DEBUG]: V2 to V2 passthrough
2022-07-26 15:43:12,972 - util.py[DEBUG]: Writing to /etc/netplan/50-cloud-init.yaml - wb: [644] 491 bytes
2022-07-26 15:43:12,972 - subp.py[DEBUG]: Running command ['netplan', 'generate'] with allowed return codes [0] (shell=False, capture=True)
2022-07-26 15:43:26,106 - __init__.py[DEBUG]: Selected renderer 'netplan' from priority list: ['netplan', 'eni', 'sysconfig']
2022-07-26 15:43:26,106 - netplan.py[DEBUG]: V2 to V2 passthrough
2022-07-26 15:43:26,107 - util.py[DEBUG]: Writing to /etc/netplan/50-cloud-init.yaml - wb: [644] 491 bytes
2022-07-26 15:43:26,107 - subp.py[DEBUG]: Running command ['netplan', 'generate'] with allowed return codes [0] (shell=False, capture=True)
2022-07-26 15:43:26,166 - activators.py[DEBUG]: Attempting command ['netplan', 'apply'] for device all
2022-07-26 15:43:26,166 - subp.py[DEBUG]: Running command ['netplan', 'apply'] with allowed return codes [0] (shell=False, capture=True)
...
Since Desktop ephemeral environment prefers NetworkManager to render network, it should change the default network renderers configured for cloud-init with a supplemental cloud config file
cat > /etc/cloud/cloud.cfg.d/99-installer-use-networkmanager.cfg <<EOF
system_info:
network:
renderers: ['network-manager']
EOF |
|
| 2022-07-26 15:55:35 |
Chad Smith |
description |
In this ephemeral install environment, the Ubuntu desktop installer prefers to setup NetworkManager for network configuration due to the file
cat /etc/netplan/01-network-manager-all.yaml:
# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: NetworkManager
But cloud-init package default configuration sets network renderers to netplan:
grep -B 1 renderers /etc/cloud/cloud.cfg
network:
renderers: ['netplan', 'eni', 'sysconfig']
This results in cloud-init writing discovered network configuration to netplan files which will not be applied to the ephemeral system during boot which will break some potential custom install paths or cloud-init datasource overrides in the emphemeral desktop install environment.
You can see cloud-init trying to render netplan files by default in /var/log/cloud-init.log:
egrep 'netplan|network-manager' /var/log/cloud-init.log
...
2022-07-26 15:43:12,972 - __init__.py[DEBUG]: Selected renderer 'netplan' from priority list: ['netplan', 'eni', 'sysconfig']
2022-07-26 15:43:12,972 - netplan.py[DEBUG]: V2 to V2 passthrough
2022-07-26 15:43:12,972 - util.py[DEBUG]: Writing to /etc/netplan/50-cloud-init.yaml - wb: [644] 491 bytes
2022-07-26 15:43:12,972 - subp.py[DEBUG]: Running command ['netplan', 'generate'] with allowed return codes [0] (shell=False, capture=True)
2022-07-26 15:43:26,106 - __init__.py[DEBUG]: Selected renderer 'netplan' from priority list: ['netplan', 'eni', 'sysconfig']
2022-07-26 15:43:26,106 - netplan.py[DEBUG]: V2 to V2 passthrough
2022-07-26 15:43:26,107 - util.py[DEBUG]: Writing to /etc/netplan/50-cloud-init.yaml - wb: [644] 491 bytes
2022-07-26 15:43:26,107 - subp.py[DEBUG]: Running command ['netplan', 'generate'] with allowed return codes [0] (shell=False, capture=True)
2022-07-26 15:43:26,166 - activators.py[DEBUG]: Attempting command ['netplan', 'apply'] for device all
2022-07-26 15:43:26,166 - subp.py[DEBUG]: Running command ['netplan', 'apply'] with allowed return codes [0] (shell=False, capture=True)
...
Since Desktop ephemeral environment prefers NetworkManager to render network, it should change the default network renderers configured for cloud-init with a supplemental cloud config file
cat > /etc/cloud/cloud.cfg.d/99-installer-use-networkmanager.cfg <<EOF
system_info:
network:
renderers: ['network-manager']
EOF |
In this ephemeral install environment, the Ubuntu desktop installer prefers to setup NetworkManager for network configuration due to the file
cat /etc/netplan/01-network-manager-all.yaml:
# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: NetworkManager
But cloud-init package default configuration sets network renderers to netplan:
grep -B 1 renderers /etc/cloud/cloud.cfg
network:
renderers: ['netplan', 'eni', 'sysconfig']
This results in cloud-init writing discovered network configuration to netplan files which will not be applied to the ephemeral system during boot via custom kernel commandline parameters which will break some potential custom install paths or cloud-init datasource overrides in the emphemeral desktop install environment.
You can see cloud-init trying to render netplan files by default in /var/log/cloud-init.log:
egrep 'netplan|network-manager' /var/log/cloud-init.log
...
2022-07-26 15:43:12,972 - __init__.py[DEBUG]: Selected renderer 'netplan' from priority list: ['netplan', 'eni', 'sysconfig']
2022-07-26 15:43:12,972 - netplan.py[DEBUG]: V2 to V2 passthrough
2022-07-26 15:43:12,972 - util.py[DEBUG]: Writing to /etc/netplan/50-cloud-init.yaml - wb: [644] 491 bytes
2022-07-26 15:43:12,972 - subp.py[DEBUG]: Running command ['netplan', 'generate'] with allowed return codes [0] (shell=False, capture=True)
2022-07-26 15:43:26,106 - __init__.py[DEBUG]: Selected renderer 'netplan' from priority list: ['netplan', 'eni', 'sysconfig']
2022-07-26 15:43:26,106 - netplan.py[DEBUG]: V2 to V2 passthrough
2022-07-26 15:43:26,107 - util.py[DEBUG]: Writing to /etc/netplan/50-cloud-init.yaml - wb: [644] 491 bytes
2022-07-26 15:43:26,107 - subp.py[DEBUG]: Running command ['netplan', 'generate'] with allowed return codes [0] (shell=False, capture=True)
2022-07-26 15:43:26,166 - activators.py[DEBUG]: Attempting command ['netplan', 'apply'] for device all
2022-07-26 15:43:26,166 - subp.py[DEBUG]: Running command ['netplan', 'apply'] with allowed return codes [0] (shell=False, capture=True)
...
Since Desktop ephemeral environment prefers NetworkManager to render network, it should change the default network renderers configured for cloud-init with a supplemental cloud config file
cat > /etc/cloud/cloud.cfg.d/99-installer-use-networkmanager.cfg <<EOF
system_info:
network:
renderers: ['network-manager']
EOF |
|
| 2022-07-26 15:58:01 |
Chad Smith |
summary |
ubuntu-desktop-installer: cloud-init not configured to use network-manager resulting in unread /etc/netplan /50-cloud-init.yaml |
ubuntu-desktop-installer: cloud-init not configured to use network-manager resulting in unread /etc/netplan/50-cloud-init.yaml |
|
| 2022-07-26 15:58:40 |
Chad Smith |
description |
In this ephemeral install environment, the Ubuntu desktop installer prefers to setup NetworkManager for network configuration due to the file
cat /etc/netplan/01-network-manager-all.yaml:
# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: NetworkManager
But cloud-init package default configuration sets network renderers to netplan:
grep -B 1 renderers /etc/cloud/cloud.cfg
network:
renderers: ['netplan', 'eni', 'sysconfig']
This results in cloud-init writing discovered network configuration to netplan files which will not be applied to the ephemeral system during boot via custom kernel commandline parameters which will break some potential custom install paths or cloud-init datasource overrides in the emphemeral desktop install environment.
You can see cloud-init trying to render netplan files by default in /var/log/cloud-init.log:
egrep 'netplan|network-manager' /var/log/cloud-init.log
...
2022-07-26 15:43:12,972 - __init__.py[DEBUG]: Selected renderer 'netplan' from priority list: ['netplan', 'eni', 'sysconfig']
2022-07-26 15:43:12,972 - netplan.py[DEBUG]: V2 to V2 passthrough
2022-07-26 15:43:12,972 - util.py[DEBUG]: Writing to /etc/netplan/50-cloud-init.yaml - wb: [644] 491 bytes
2022-07-26 15:43:12,972 - subp.py[DEBUG]: Running command ['netplan', 'generate'] with allowed return codes [0] (shell=False, capture=True)
2022-07-26 15:43:26,106 - __init__.py[DEBUG]: Selected renderer 'netplan' from priority list: ['netplan', 'eni', 'sysconfig']
2022-07-26 15:43:26,106 - netplan.py[DEBUG]: V2 to V2 passthrough
2022-07-26 15:43:26,107 - util.py[DEBUG]: Writing to /etc/netplan/50-cloud-init.yaml - wb: [644] 491 bytes
2022-07-26 15:43:26,107 - subp.py[DEBUG]: Running command ['netplan', 'generate'] with allowed return codes [0] (shell=False, capture=True)
2022-07-26 15:43:26,166 - activators.py[DEBUG]: Attempting command ['netplan', 'apply'] for device all
2022-07-26 15:43:26,166 - subp.py[DEBUG]: Running command ['netplan', 'apply'] with allowed return codes [0] (shell=False, capture=True)
...
Since Desktop ephemeral environment prefers NetworkManager to render network, it should change the default network renderers configured for cloud-init with a supplemental cloud config file
cat > /etc/cloud/cloud.cfg.d/99-installer-use-networkmanager.cfg <<EOF
system_info:
network:
renderers: ['network-manager']
EOF |
In this ephemeral install environment, the Ubuntu desktop installer prefers to setup NetworkManager for network configuration due to the file
affects:
ubuntu-deskstop-installer version 0+git.74cbf061 revision 560
cat /etc/netplan/01-network-manager-all.yaml:
# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: NetworkManager
But cloud-init package default configuration sets network renderers to netplan:
grep -B 1 renderers /etc/cloud/cloud.cfg
network:
renderers: ['netplan', 'eni', 'sysconfig']
This results in cloud-init writing discovered network configuration to netplan files which will not be applied to the ephemeral system during boot via custom kernel commandline parameters which will break some potential custom install paths or cloud-init datasource overrides in the emphemeral desktop install environment.
You can see cloud-init trying to render netplan files by default in /var/log/cloud-init.log:
egrep 'netplan|network-manager' /var/log/cloud-init.log
...
2022-07-26 15:43:12,972 - __init__.py[DEBUG]: Selected renderer 'netplan' from priority list: ['netplan', 'eni', 'sysconfig']
2022-07-26 15:43:12,972 - netplan.py[DEBUG]: V2 to V2 passthrough
2022-07-26 15:43:12,972 - util.py[DEBUG]: Writing to /etc/netplan/50-cloud-init.yaml - wb: [644] 491 bytes
2022-07-26 15:43:12,972 - subp.py[DEBUG]: Running command ['netplan', 'generate'] with allowed return codes [0] (shell=False, capture=True)
2022-07-26 15:43:26,106 - __init__.py[DEBUG]: Selected renderer 'netplan' from priority list: ['netplan', 'eni', 'sysconfig']
2022-07-26 15:43:26,106 - netplan.py[DEBUG]: V2 to V2 passthrough
2022-07-26 15:43:26,107 - util.py[DEBUG]: Writing to /etc/netplan/50-cloud-init.yaml - wb: [644] 491 bytes
2022-07-26 15:43:26,107 - subp.py[DEBUG]: Running command ['netplan', 'generate'] with allowed return codes [0] (shell=False, capture=True)
2022-07-26 15:43:26,166 - activators.py[DEBUG]: Attempting command ['netplan', 'apply'] for device all
2022-07-26 15:43:26,166 - subp.py[DEBUG]: Running command ['netplan', 'apply'] with allowed return codes [0] (shell=False, capture=True)
...
Since Desktop ephemeral environment prefers NetworkManager to render network, it should change the default network renderers configured for cloud-init with a supplemental cloud config file
cat > /etc/cloud/cloud.cfg.d/99-installer-use-networkmanager.cfg <<EOF
system_info:
network:
renderers: ['network-manager']
EOF |
|
| 2022-07-26 16:01:30 |
Dan Bungert |
affects |
subiquity |
livecd-rootfs |
|
| 2022-07-26 16:11:41 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~dbungert/livecd-rootfs/+git/livecd-rootfs/+merge/427445 |
|
| 2023-04-07 22:32:59 |
Dan Bungert |
bug task added |
|
livecd-rootfs (Ubuntu) |
|
| 2023-04-07 22:33:14 |
Dan Bungert |
livecd-rootfs (Ubuntu): status |
New |
Fix Released |
|
