EDIT: So after about three hours of trying to get 'netplan try' to work, I tried 'netplan apply' and the setting worked. Yet, 'netplan try' still throws the same error. I am assuming that this is a bug?

I just upgraded to 21.10. However, I am having troubles with NetPlan. Trying to apply the following new setup, NetPlan is coming back with the error "'netplanapply' object has no attribute 'state'" and reverts back to the last setup

network: version: 2 renderer: networkd ethernets: enp1s0: link-local: [] optional: true dhcp4: no addresses: - 192.168.189.6/24 routes: - to: default via: 192.168.189.2 nameservers: addresses: [192.168.189.2] search: [young.youngind.ca]

Even when I copy back the default netplan config file and run netplan try, I get the same error.

network: ethernets: enp1s0: dhcp4: true version: 2

Any ideas as to what is going on? I get the same error with the freshly installed netplan config!!

7

3 Answers

There is a bug report about this issue with 'netplan try'

As a workaround you can execute the "netplan try" command as:

netplan try --state /etc/netplan

This will mitigate the problem for the time being.

2

I used netplan apply instead and it worked for my situation.

I managed to make it work with this configuration below:

network: version: 2 renderer: networkd ethernets: eth0: link-local: [] optional: true dhcp4: no addresses: - 192.168.189.6/24 routes: - to: default via: 192.168.189.2 match: macaddress: 08:00:27:7d:21:fd set-name: eth0 nameservers: addresses: [8.8.8.8] search: []

2

Your Answer

Sign up or log in

Sign up using Google Sign up using Facebook Sign up using Email and Password Submit

Post as a guest

Post Your Answer Discard

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy