@Marcos: same bug on my side.
I was also asked to switch from DHCP to a static IP, to make the configuration
as simple as possible and remove any doubt about DHCP server issues.
Once I did it I've had the same issue (no IP at boot).
Could you please try the same thing on your side and confirm tha
@Marcos,#80: ubuntu-18.04-server-amd64.iso is exactly the ISO I'm using
for my installations.
@Mathieu,#82: you've removed the verification-failed-bionic tag but
0.40.1~18.04.2 is still not working on my side, both on VirtualBox VM and on
Proxmox VM (KDE).
Interface renaming works but IP address
Still not working on my side (plain vanilla Ubuntu Server 18.04, fully
updated, no cloud).
The renaming regression of 0.40.1~18.04.1 has been fixed, but it's still
not applying IP address just after boot.
A manual "netplan apply" correctly configures the network interface.
--
IMHO if a "match" option is present (especially with a MAC condition),
it should always override the ID.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770082
Title:
systemd-networkd not renaming de
Sorry, still not working here. Same behavior as my previous post.
Maybe it's due to VirtualBox? Haven't tried on my production KDE (Proxmox)
yet...
---
# dpkg -s netplan.io | grep Version
Version: 0.40~18.04.1
---
** Tags removed: verification-needed-bionic
** Tags added
Wrong cut&paste:
---
# dpkg -s netplan.io | grep Version
Version: 0.40.1~18.04.1
---
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770082
Title:
systemd-networkd not renami
Sorry for being such a buzzkill, but it's still not working on my side
:(
=
Reinstalled 18.04.1 server x64 from scratch in a clean VirtualBox VM.
=
# lsb_release
I've tried some workarounds:
- kernel parameter "net.ifnames=0" on kernel commandline: NOT WORKING
- ebtables: NOT WORKING
- add "@reboot /usr/sbin/netplan apply" to root cron: NOT WORKING
The following works on my side:
* create a new unit file: /etc/systemd/system/netplan-workaround.service
---
@Marcos: ebtables is ininfluent on my side.
It is installed with server version and the bug persists both with and without
it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770082
Title:
systemd-n
*** This bug is a duplicate of bug 1770082 ***
https://bugs.launchpad.net/bugs/1770082
** This bug has been marked a duplicate of bug 1770082
systemd-networkd not renaming devices on boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Just tried with a fresh installed Ubuntu SERVER 18.04.1.
The interface now got renamed but IP address is not applied, both static and
DHCP.
If I run "netplan apply" just after reboot+login, network interface is
configured correctly (again, both with static/DHCP address).
Do you mean that removing ebtables (if possible) let rename work
properly?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770082
Title:
systemd-networkd not renaming devices on boot
To manage notif
After a few investigation I found that my previous fix does not fix the
bug at boot, at least on my Ubuntu 18.04 server.
There's no need to manually create the /run/dhcp-server folder since
dhcpd automatically creates the needed PID file parent folders by
itself.
It only happens at boot so the bu
Ubuntu 18.04 here, no apparmor.
Directory /run is on tempfs, so it is empty at start.
I suppose PID file /run/dhcp-server/dhcpd.pid can't be created because
directory /run/dhcp-server is missing at startup and I haven't found where it
will be created.
I've fixed systemd unit "/lib/systemd/syste
The behavior is not reproducible, maybe a race condition?
I'm actually not getting IP addres for static interface too :-(
I agree, let's continue there:
https://bugs.launchpad.net/netplan/+bug/1768827
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Sorry for the confusion.
Current version (0.36.2):
- both devices not renamed after boot (have original enp.. names)
- static and dynamic IPs correctly assigned
Proposed version (0.36.3):
- both devices correctly renamed after boot:
:91 gets renamed eth_static
:f5 gets renamed to eth_dhcp
- o
@Daniel: no, it's a regression to me because set-name never worked and
now DHCP stopped working too.
But I'm not testing the same environment as you, I'm on VirtualBox and this is
my original bug report (linked to this one):
https://bugs.launchpad.net/netplan/+bug/1768827
--
You received this b
Partially working here on fully updated Ubuntu 18.04 Server on
VirtualBox :(
I've enabled -proposed repo and updated both nplan/bionic-proposed and
netplan.ion/bionic-proposed packages.
Now interfaces got renamed, but IPs are not assigned at boot (both DHCP and
static ones).
Calling "netplan gen
Thanks for the update.
Referring to this duplicate bug
(https://bugs.launchpad.net/netplan/+bug/1768827), is it going to be backported
to 18.04?
Or is there a way to install 0.38 on Ubuntu Server 18.04?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Maybe a backport of php-5.3.3 could help.
Can someone provide it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/654470
Title:
egroupware provoke segfaults
--
ubuntu-bugs mailing list
ubuntu-bugs@l
+1 for having access to DVD creator scripts/procedures
--
No DVD images available for 8.04.2 release
https://bugs.launchpad.net/bugs/379601
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ub
This seems to give some hope, even on de-bricking hardware...
http://lkml.org/lkml/2008/10/1/368
Is it?
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You received this bug notification because you are a member of Ubunt
Public bug reported:
Binary package hint: fail2ban
The package fail2ban-0.8.1-1 should have whois as a dependence.
Whois is needed to include IP address details into warning emails.
** Affects: fail2ban (Ubuntu)
Importance: Undecided
Assignee: Yaroslav Halchenko (yarikoptic)
S
23 matches
Mail list logo
