[Bug 2077424] [NEW] neutron missing dependency on iptables
Public bug reported: Neutron agents are missing a package dependency on iptables, since iptables is not installed by default: neutron-l3-agent: Aug 20 13:16:34 gateway1a neutron-l3-agent[1498]: Failed to process floating IPs. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/neutron/agent/linux/iptables_manager.py", line 434, in defer_apply yield File "/usr/lib/python3/dist-packages/neutron/agent/l3/router_info.py", line 1040, in process_external self._process_external_gateway(ex_gw_port) File "/usr/lib/python3/dist-packages/neutron/agent/l3/router_info.py", line 938, in _process_external_gateway self._handle_router_snat_rules(gw_port, interface_name) File "/usr/lib/python3/dist-packages/neutron/agent/l3/router_info.py", line 1011, in _handle_router_snat_rules self._add_snat_rules(ex_gw_port, File "/usr/lib/python3/dist-packages/neutron/agent/l3/router_info.py", line 996, in _add_snat_rules rules = self.external_gateway_nat_fip_rules( File "/usr/lib/python3/dist-packages/neutron/agent/l3/router_info.py", line 955, in external_gateway_nat_fip_rules if self.iptables_manager.random_fully: ^^ File "/usr/lib/python3/dist-packages/neutron/agent/linux/iptables_manager.py", line 502, in random_fully version = self._get_version() ^^^ File "/usr/lib/python3/dist-packages/neutron/agent/linux/iptables_manager.py", line 492, in _get_version version = str(linux_utils.execute( File "/usr/lib/python3/dist-packages/neutron/agent/linux/utils.py", line 131, in execute _stdout, _stderr, returncode = priv_utils.execute_process( ^^^ File "/usr/lib/python3/dist-packages/oslo_privsep/priv_context.py", line 271, in _wrap return self.channel.remote_call(name, args, kwargs, File "/usr/lib/python3/dist-packages/oslo_privsep/daemon.py", line 215, in remote_call raise exc_type(*result[2]) FileNotFoundError: [Errno 2] No such file or directory During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/neutron/agent/linux/iptables_manager.py", line 437, in defer_apply self.defer_apply_off() File "/usr/lib/python3/dist-packages/neutron/agent/linux/iptables_manager.py", line 451, in defer_apply_off self._apply() File "/usr/lib/python3/dist-packages/neutron/agent/linux/iptables_manager.py", line 469, in _apply first = self._apply_synchronized() ^^ File "/usr/lib/python3/dist-packages/neutron/agent/linux/iptables_manager.py", line 593, in _apply_synchronized with excutils.save_and_reraise_exception() as ctx: File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 227, in __exit__ self.force_reraise() File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 200, in force_reraise raise self.value File "/usr/lib/python3/dist-packages/neutron/agent/linux/iptables_manager.py", line 586, in _apply_synchronized save_output = linux_utils.execute(args, run_as_root=True, ^^^ File "/usr/lib/python3/dist-packages/neutron/agent/linux/utils.py", line 156, in execute raise exceptions.ProcessExecutionError(msg, neutron_lib.exceptions.ProcessExecutionError: Exit code: 1; Cmd: ['ip', 'netns', 'exec', 'qrouter-47f6ed06-b839-4672-af8e-811d66b33581', 'iptables-save']; Stdin: ; Stdout: ; Stderr: exec of "iptables-save" failed: No such file or dir> During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/neutron/agent/l3/router_info.py", line 1038, in process_external with self.iptables_manager.defer_apply(): File "/usr/lib/python3.12/contextlib.py", line 158, in __exit__ self.gen.throw(value) File "/usr/lib/python3/dist-packages/neutron/agent/linux/iptables_manager.py", line 444, in defer_apply raise l3_exc.IpTablesApplyException(msg) neutron_lib.exceptions.l3.IpTablesApplyException: Failure applying iptables rules neutron-linuxbridge-agent: Aug 20 13:17:42 gateway1a neutron-linuxbridge-agent[11326]: Error starting thread. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/neutron/agent/securitygroups_rpc.py", line 127, in init_firewall self.firewall = firewall_class( ^^^ Type
[Bug 2077423] [NEW] AttributeError: 'MetadataDriver' object has no attribute 'monitors'
Public bug reported: neutron-l3-agent fails to handle notifications on Ubuntu 24.04: Error during notification for neutron.agent.metadata.driver.after_router_updated-7849645393520 router, after_update Traceback (most recent call last): File "/usr/lib/python3/dist-packages/neutron_lib/callbacks/manager.py", line 189, in _notify_loop callback.method(resource, event, trigger, payload=payload) File "/usr/lib/python3/dist-packages/neutron/agent/metadata/driver.py", line 97, in after_router_updated if (not proxy.monitors.get(router.router_id) and ^^ AttributeError: 'MetadataDriver' object has no attribute 'monitors' ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: neutron-l3-agent 2:24.0.0-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-40.40-generic 6.8.12 Uname: Linux 6.8.0-40-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Aug 20 13:22:45 2024 PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: neutron UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: neutron (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077423 Title: AttributeError: 'MetadataDriver' object has no attribute 'monitors' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/2077423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069814] Re: alembic.script.revision.ResolutionError: No such revision or branch 'f399fa0f5f25'
Compared to v23, in v24, all migration files are missing from the package: > diff -r python3-neutron-dynamic-routing_23.0.0-0ubuntu1~cloud0 > python3-neutron-dynamic-routing_24.0.0-0ubuntu1 Only in python3-neutron-dynamic-routing_23.0.0-0ubuntu1~cloud0/usr/lib/python3/dist-packages/neutron_dynamic_routing/db/migration/alembic_migrations: script.py.mako Only in python3-neutron-dynamic-routing_23.0.0-0ubuntu1~cloud0/usr/lib/python3/dist-packages/neutron_dynamic_routing/db/migration/alembic_migrations: versions Only in python3-neutron-dynamic-routing_23.0.0-0ubuntu1~cloud0/usr/lib/python3/dist-packages/neutron_dynamic_routing/db/migration: README ** Attachment added: "Screenshot from 2024-06-19 12-46-09.png" https://bugs.launchpad.net/ubuntu/+source/neutron-dynamic-routing/+bug/2069814/+attachment/5790757/+files/Screenshot%20from%202024-06-19%2012-46-09.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069814 Title: alembic.script.revision.ResolutionError: No such revision or branch 'f399fa0f5f25' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron-dynamic-routing/+bug/2069814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069814] Re: alembic.script.revision.ResolutionError: No such revision or branch 'f399fa0f5f25'
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069814 Title: alembic.script.revision.ResolutionError: No such revision or branch 'f399fa0f5f25' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron-dynamic-routing/+bug/2069814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069814] [NEW] alembic.script.revision.ResolutionError: No such revision or branch 'f399fa0f5f25'
Public bug reported: Migrating the database fails when upgrading to Caracal: $ neutron-db-manage upgrade --expand INFO [alembic.runtime.migration] Context impl MySQLImpl. INFO [alembic.runtime.migration] Will assume non-transactional DDL. Running upgrade (expand) for neutron ... INFO [alembic.runtime.migration] Context impl MySQLImpl. INFO [alembic.runtime.migration] Will assume non-transactional DDL. OK INFO [alembic.runtime.migration] Context impl MySQLImpl. INFO [alembic.runtime.migration] Will assume non-transactional DDL. Traceback (most recent call last): File "/usr/bin/neutron-db-manage", line 10, in sys.exit(main()) File "/usr/lib/python3/dist-packages/neutron/db/migration/cli.py", line 667, in main return_val |= bool(CONF.command.func(config, CONF.command.name)) File "/usr/lib/python3/dist-packages/neutron/db/migration/cli.py", line 188, in do_upgrade run_sanity_checks(config, revision) File "/usr/lib/python3/dist-packages/neutron/db/migration/cli.py", line 650, in run_sanity_checks script_dir.run_env() File "/usr/lib/python3/dist-packages/alembic/script/base.py", line 583, in run_env util.load_python_file(self.dir, "env.py") File "/usr/lib/python3/dist-packages/alembic/util/pyfiles.py", line 95, in load_python_file module = load_module_py(module_id, path) File "/usr/lib/python3/dist-packages/alembic/util/pyfiles.py", line 113, in load_module_py spec.loader.exec_module(module) # type: ignore File "", line 883, in exec_module File "", line 241, in _call_with_frames_removed File "/usr/lib/python3/dist-packages/neutron_dynamic_routing/db/migration/alembic_migrations/env.py", line 88, in run_migrations_online() File "/usr/lib/python3/dist-packages/neutron_dynamic_routing/db/migration/alembic_migrations/env.py", line 79, in run_migrations_online context.run_migrations() File "", line 8, in run_migrations File "/usr/lib/python3/dist-packages/alembic/runtime/environment.py", line 948, in run_migrations self.get_context().run_migrations(**kw) File "/usr/lib/python3/dist-packages/alembic/runtime/migration.py", line 615, in run_migrations for step in self._migrations_fn(heads, self): File "/usr/lib/python3/dist-packages/neutron/db/migration/cli.py", line 640, in check_sanity for script in script_dir.revision_map.iterate_revisions( File "/usr/lib/python3/dist-packages/alembic/script/revision.py", line 813, in iterate_revisions revisions, heads = fn( File "/usr/lib/python3/dist-packages/alembic/script/revision.py", line 1466, in _collect_upgrade_revisions current_revisions = self.get_revisions(lower) File "/usr/lib/python3/dist-packages/alembic/script/revision.py", line 543, in get_revisions return sum([self.get_revisions(id_elem) for id_elem in id_], ()) File "/usr/lib/python3/dist-packages/alembic/script/revision.py", line 543, in return sum([self.get_revisions(id_elem) for id_elem in id_], ()) File "/usr/lib/python3/dist-packages/alembic/script/revision.py", line 566, in get_revisions return tuple( File "/usr/lib/python3/dist-packages/alembic/script/revision.py", line 567, in self._revision_for_ident(rev_id, branch_label) File "/usr/lib/python3/dist-packages/alembic/script/revision.py", line 638, in _revision_for_ident raise ResolutionError( alembic.script.revision.ResolutionError: No such revision or branch 'f399fa0f5f25' Currently, we're running 22.04.4 LTS with Canonical cloud archives for caracal. $ apt-cache policy python3-neutron-dynamic-routing python3-neutron-dynamic-routing: Installed: 2:24.0.0-0ubuntu1 Candidate: 2:24.0.0-0ubuntu1 Version table: *** 2:24.0.0-0ubuntu1 100 100 /var/lib/dpkg/status 2:24.0.0-0ubuntu1~cloud0 500 500 http://... jammy/openstack-caracal amd64 Packages 2:20.0.0-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages ** Affects: neutron-dynamic-routing (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069814 Title: alembic.script.revision.ResolutionError: No such revision or branch 'f399fa0f5f25' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron-dynamic-routing/+bug/2069814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2004179] Re: neutron-linuxbridge-agent flat network incompatibility with systemd-networkd
We're not yet on 24.04 and still have a few OpenStack upgrades to do before we can try 24.04. For now, we're running 22.04 and do specify the bridges that neutron-linuxbridge-agent would create directly in systemd- networkd, which mostly works, like this: # /etc/systemd/network/10-brqe240c66b-da.netdev [NetDev] Name=brqe240c66b-da Kind=bridge MTUBytes=1500 # /etc/systemd/network/10-brqe240c66b-da.network [Match] Name=brqe240c66b-da [Link] MTUBytes=1500 [Network] LinkLocalAddressing=no ConfigureWithoutCarrier=yes This might have some implications on security, since we're not completely sure that we didn't miss any isolation or brtables/iptables rule that neutron-linuxbridge-agent would or wouldn't set up, but in our specific case, we deemed that as acceptable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2004179 Title: neutron-linuxbridge-agent flat network incompatibility with systemd- networkd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2004179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767172] Re: Regression: /etc/modules checked against blacklist or it's really hard to load blacklisted watchdog modules when one really wants one
> I think it's fine. It sounds like there will just be no way to override package-installed blacklists any more. That's unfortunate, but it's a very rare situation. The i6300esb watchdog driver is required for every KVM/qemu virtual machine with an emulated watchdog (https://wiki.openstack.org/wiki/LibvirtWatchdog). Having no easy option to enable that module for virtual machines is a blocker for having them reset when stuck. See the following issues to: * https://bugs.launchpad.net/ubuntu/+source/linux/+bug/642930 * https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948040 * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009350 * https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1432837 ** Bug watch added: Debian Bug tracker #1009350 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009350 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767172 Title: Regression: /etc/modules checked against blacklist or it's really hard to load blacklisted watchdog modules when one really wants one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767172/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948040] Re: modprobe.d is not honored on uc20
Note that relaxing the watchdog module blacklist would solve this issue too: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1767172. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948040 Title: modprobe.d is not honored on uc20 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1948040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959118] Re: LTS upgrade to v21 breaks in LXD containers in OpenStack (nova-compute-lxd)
The fix seems to still not be available in Ubuntu 18.04 and 20.04 as well as their cloud images. The current images still list the LXD data source before the OpenStack data source. Is there any additional step needed to fix the issue in the LTS releases? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959118 Title: LTS upgrade to v21 breaks in LXD containers in OpenStack (nova- compute-lxd) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1959118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959118] Re: LTS upgrade to v21 breaks in LXD containers in OpenStack (nova-compute-lxd)
We use nova-compute-lxd to run OpenStack "VMs" not as libvirt+QEMU virtual machines, but as LXD containers. The nova-compute-lxd connects to the local LXD daemon and creates containers, using a rootfs image from Glance, and attaching it to networks managed by Neutron (VXLANs in our case). As far as I know, LXD basically is used as a dumb "hypervisors". As images, we use the rootfs images "focal-server-cloudimg- amd64-root.tar.xz" from https://cloud-images.ubuntu.com/focal/current/. A daily cron job checks for new images and imports them to Glance. We actually do run "regular" libvirt+QEMU VMs to. They are set up the same way, and use the qcow images. Before the upgrade, the LXD container used "DataSourceOpenStackLocal [net,ver=2]" data source. I am not aware of any special configuration needed to make that happen. The containers used DHCP to get their IP addresses, contacted the metadata server at 169.254.169.254, and processed the results the same way as the QEMU VMs did. > To do so, run "cloud-init collect-logs" and upload the resulting tarball to this bug. I'll see if I can find a still running container. Most instances were recently recreated, which failed. But I was able to find a cloud-init log from a previous instance, that shows the data source as DataSourceOpenStackLocal, even after the cloud-init package was upgraded in the running system and after reboots. ** Attachment added: "cloud-init-output.log" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1959118/+attachment/5557855/+files/cloud-init-output.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959118 Title: LTS upgrade to v21 breaks in LXD containers in OpenStack (nova- compute-lxd) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1959118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959118] [NEW] LTS upgrade to v21 breaks in LXD containers in OpenStack (nova-compute-lxd)
Public bug reported: Some time ago, cloud-init version 21 was pushed to all LTS releases including 20.04, and 18.04. It will be installed by default and present in all LTS cloud images. We are running LXD in OpenStack using nova-compute-lxd and unmodified cloud images. Since cloud-init was upgraded in LTS images, cloud-init will only use the new LXD data source, and will no longer contact the EC2-compatible meta-data server from OpenStack. This means that all LXD instances will not receive any meta-data anymore, as it is only available via the meta-data server. No new LXD instances can be started and configured in OpenStack, not with the current LTS 18.04 nor the LTS 20.04 images. We cannot rebuild instances nor spawn new ones, despite using the LTS releases that formerly worked. Can the upgrade be rolled backed, or the data source be disabled, to restore the original LTS behavior? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cloud-init 21.4-0ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 4.15.0-166.174-generic 4.15.18 Uname: Linux 4.15.0-166-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CloudName: OpenStack Date: Wed Jan 26 15:44:05 2022 Ec2AMI: ami-02c6 Ec2AMIManifest: FIXME Ec2AvailabilityZone: az3 Ec2InstanceType: p2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: SHELL=/bin/bash LANG=C.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably fresh install) user_data.txt: Error: path contained symlinks. ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959118 Title: LTS upgrade to v21 breaks in LXD containers in OpenStack (nova- compute-lxd) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1959118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929560] Re: link mac isn't set if already up
Thanks a lot for your work, Dan! Unfortunately, I wasn't able to pick up the new bug from here, sorry for that. (It appears I did not get any notification on your comments, need to check that) The bridges are managed by OpenStack Neutron from Ubuntu cloud archives and with names derived from the network UUID in the cluster database. It might work for a very limited set of bridges, if they do not set different options. AFAIK, OpenStack Neutron is still working on supporting using external bridges (https://bugs.launchpad.net/neutron/+bug/1105488). As we have bridges on VLANs on bonded interfaces (currently managed with systemd-networkd), I will see if I have to replace that all or if there is an option to just have systemd-networkd not set nomaster... Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929560 Title: link mac isn't set if already up To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1929560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929560] Re: link mac isn't set if already up
This backport to 18.04 LTS broke all our OpenStack compute nodes. We use systemd-network to configure interfaces etc. and neutron-linuxbridge- agent with some flat networks. In this scenario, the neutron agent creates bridges for the flat networks and assigns them to physical interfaces based on a mapping. The backport now sets nomaster on these interfaces, effectively removing the bridges and cutting of connectivity of all VMs using these flat networks. This happened already when the systemd package was upgraded (and systemd-networkd restarted). Example: ``` 10: flat-net1@data: mtu 1500 qdisc noqueue master brq88363244-5f state UP group default qlen 1000 link/ether b0:22:28:1c:f7:12 brd ff:ff:ff:ff:ff:ff ``` The interface (VLAN here) is created and managed by systemd-networkd, the bridge `brq88363244-5f` is managed by neutron. Of course, systemd- networkd doesn't know anything about the bridge, this wasn't a problem until now, but the latest patch update always sets nomaster to `flat- net1`. We were really surprise by this change in 18.04 LTS. Is there any recommend workaround to have systemd-networkd not set nomaster or do we have to not use systemd-network at all? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929560 Title: link mac isn't set if already up To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1929560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
