[UC20][NETPLAN] "renderer" option is not working in netplan configuration of gadget.yamal

Bug #2026220 reported by ChunAnWu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OEM Priority Project
New
High
ChunAnWu
snapd
New
Undecided
Unassigned

Bug Description

We add a simple netplan configuration to gadget.yaml and everything work fine until we add "renderer"
option.

Tags: oem-priority
ChunAnWu (kiya956)
Changed in oem-priority:
assignee: nobody → ChunAnWu (kiya956)
importance: Undecided → High
Revision history for this message
Michael Vogt (mvo) wrote :

Could you please attach the failing gadget.yaml?

Revision history for this message
Michael Vogt (mvo) wrote :

Could you please paste also the exact error message here.

Revision history for this message
ChunAnWu (kiya956) wrote :

Hi Michael
    I have uploaded the gadget.yaml

BR
    An

Revision history for this message
ChunAnWu (kiya956) wrote :

Hi Michael
the log I saw
'''
Jul 13 06:52:31 ubuntu systemd[1]: Starting Snap Daemon...
Jul 13 06:52:33 ubuntu snapd[1681]: overlord.go:272: Acquiring state lock file
Jul 13 06:52:33 ubuntu snapd[1681]: overlord.go:277: Acquired state lock file
Jul 13 06:52:34 ubuntu snapd[1681]: patch.go:64: Patching system state level 6 to sublevel 1...
Jul 13 06:52:34 ubuntu snapd[1681]: patch.go:64: Patching system state level 6 to sublevel 2...
Jul 13 06:52:34 ubuntu snapd[1681]: patch.go:64: Patching system state level 6 to sublevel 3...
Jul 13 06:52:34 ubuntu snapd[1681]: daemon.go:247: started snapd/2.59.5 (series 16) ubuntu-core/20 (arm64) linux/5.4.0-1039-shiner.
Jul 13 06:52:34 ubuntu snapd[1681]: daemon.go:340: adjusting startup timeout by 35s (pessimistic estimate of 30s plus 5s per snap)
Jul 13 06:52:34 ubuntu snapd[1681]: backends.go:58: AppArmor status: apparmor is enabled and all features are available
Jul 13 06:52:34 ubuntu snapd[1681]: devicemgr.go:338: save already mounted under /var/lib/snapd/save
Jul 13 06:52:34 ubuntu systemd[1]: Started Snap Daemon.
Jul 13 06:54:00 ubuntu snapd[1681]: context.go:318: ERROR task 1 (Run configure hook of "core" snap if present): ignoring failure in hook "configure": cannot try netplan config: no specific reason returned from netplan and cannot cancel netplan config: Unknown object '/io/netplan/Netplan/config/UX6V71'.
Jul 13 06:55:47 ubuntu snapd[1681]: stateengine.go:149: state ensure error: persistent network error: Get https://api.snapcraft.io/api/v1/snaps/sections: dial tcp: lookup api.snapcraft.io: Temporary failure in name resolution
Jul 13 06:56:07 ubuntu snapd[1681]: devicemgr.go:1190: System initialized, cloud-init reported to be done, disabled permanently
Jul 13 07:32:42 ubuntu snapd[1681]: storehelpers.go:769: cannot refresh: snap has no updates available: "core20", "hbt-imx-kernel", "hon-pdk-x8med-gadget", "modem-manager", "network-manager", "snapd"
'''

Revision history for this message
Alfonso Sanchez-Beato (alfonsosanchezbeato) wrote :

The problem is probably https://bugs.launchpad.net/netplan/+bug/2027583 - the netplan try that snapd does is returning an error when NM is installed.

Revision history for this message
Alfonso Sanchez-Beato (alfonsosanchezbeato) wrote :

I have reproduced this and actually it looks more like https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1959570 - I saw the nmcli related crash in the journal along with the snapd error. To reproduce, I ran:

$ sudo snap set system system.network.netplan='{"network":{"version":2,"renderer":"NetworkManager"}}'

The problem is fixed in 0.106. but it has not been backported to jammy yet.

Rex Tsai (chihchun)
tags: added: oem-priority
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.