Not sure if that applies here, but "fe80::a8bb:ccff:fedd:eeff" is not a valid ipv6 address on this machine.
instead try "fe80::a8bb:ccff:fedd:eeff%ens3"
The problem might be with "systemd-resolved" which happily serves "fe80::a8bb:ccff:fedd:eeff" as an ipv6 address of this machine.
I stumbled over this ticket based on symptoms I saw (unrelated to netplan), and searching for some keywords...
Not sure if that applies here, but "fe80:: a8bb:ccff: fedd:eeff" is not a valid ipv6 address on this machine.
instead try "fe80:: a8bb:ccff: fedd:eeff% ens3"
The problem might be with "systemd-resolved" which happily serves "fe80:: a8bb:ccff: fedd:eeff" as an ipv6 address of this machine.
I stumbled over this ticket based on symptoms I saw (unrelated to netplan), and searching for some keywords...