** Tags added: ssc
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1794478
Title:
Automatic ipv4 not assigned to bond interface is manual ipv6 is
assigned to it
Status in Ub
This bug was fixed in the package network-manager - 1.10.6-2ubuntu1.4
---
network-manager (1.10.6-2ubuntu1.4) bionic; urgency=medium
* d/p/start-ip-conf-when-master-carrier-goes-up.patch: device: start IP
configuration when master carrier goes up (LP: #1794478)
network-manager
Thx 'abhir...@in.ibm.com' for verification - the tags are set to done.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1794478
Title:
Automatic ipv4 not assigned to bond interf
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1794478
Title:
Automatic ipv4 not assigned to bond interfa
Hello
I've verified this -proposed pkg on my local.
#2 on description working fine.
xtrusia@ubuntu:~$ dpkg -l | grep network-manager
ii network-manager1.10.6-2ubuntu1.4
amd64network management framework (daemon and userspace
to
Hello bugproxy, or anyone else affected,
Accepted network-manager into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.10.6-2ubuntu1.4 in a few hours, and then in the -proposed
repository.
Please help us by testing this new p
Sponsored by dgadomski. Unsubscribing sts-sponsor team.
Thanks for your contribution Seyeong.
Thanks for the sponsoring Dariusz.
- Eric
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.ne
** Changed in: network-manager (Ubuntu Bionic)
Status: Confirmed => In Progress
** Tags added: sts-sponsor-dgadomski
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/179447
@xtrusia,
Is this ready for sponsorship ?
I'll have a look when ready.
- Eric
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1794478
Title:
Automatic ipv4 not assigned to b
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1794478
Title:
Automatic ipv4 not assigned to bond inte
why bugproxy keep attaching old debdiff I've changed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1794478
Title:
Automatic ipv4 not assigned to bond interface is manual ipv6
** Description changed:
[Impact]
+
+ In case creating bond interface, IPv4 address is not automatically
+ assigned when IPv6 has manual setting.
+
[Test Case]
+
+ 1. create 18.04.4 instance, network-manager version is 1.10.6-2ubuntu.1.2 as
original description.
+ 2. ipv6 manual, ipv4 auto
** Patch removed: "lp1794478_bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1794478/+attachment/5329464/+files/lp1794478_bionic.debdiff
** Patch added: "lp1794478_bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1794478/+attachm
I uploaded patch for bionic sru. but I didn't subscribe sru-sponsors yet
because I'm still confirming reproducer.
I'll update description after reproducing this issue in my local.
Thanks.
** Tags added: sts
** Changed in: network-manager (Ubuntu Bionic)
Assignee: (unassigned) => Seyeong Ki
** Description changed:
+
+ [Impact]
+ [Test Case]
+ [Potential Regression]
+
+ [Other informations]
+
+ * Upstream bug[0] and fix[1]:
+
+ https://bugzilla.redhat.com/show_bug.cgi?id=1575944
+ https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35
+
+ * Only affectinb Bio
Thanks for reporting the outcome of your test.
We will start the SRU process in order to update network-manager package
next week.
Regards,
Eric
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.la
This look like a similar issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1575944
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35
A test package (including the above fix) is available on my PPA:
sudo add-apt-repository ppa:slashd/lp1794478
sudo apt-get update
Please
** Changed in: network-manager (Ubuntu Bionic)
Assignee: Till Kamppeter (till-kamppeter) => (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1794478
Title:
Aut
** Changed in: network-manager (Ubuntu Bionic)
Importance: Undecided => High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1794478
Title:
Automatic ipv4 not assigned to bo
** Changed in: network-manager (Ubuntu Bionic)
Assignee: Olivier Tilloy (osomon) => Till Kamppeter (till-kamppeter)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1794478
T
Setting 'bionic' from "Fix Released" to "Confirmed" since 2 different
persons stated the problem still exist (supported with reproducer
testing)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launc
** Changed in: network-manager (Ubuntu Bionic)
Status: Fix Released => Confirmed
** Changed in: network-manager (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
Changed the status to New, since I was still able to reproduce the issue
on Bionic, using the "patched" network-manager version.
** Changed in: network-manager (Ubuntu)
Status: Fix Released => New
--
You received this bug notification because you are a member of Desktop
Packages, which is
Hi, all. I'm afraid I'll need to reopen this bug.
I was able to reproduce the issue on Bionic, using network-manager
1.10.6-2ubuntu1.2. However, when testing this on Eoan, using network-
manager 1.20.4-2ubuntu2, I didn't reproduce the behaviour.
The steps one takes to reproduce the issue, eithe
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1794478
Title:
Automatic ipv4 not assigned to bond
** Changed in: network-manager (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1794478
Title:
Automatic ipv4 not as
Adjusting tags according to comments #9 and #10.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in
> The new stable version indicate the fix mentioned by seb128 is there but no
> indication has been made in
> the debian/changelog to automatically change the status, which breaks the SRU
> machinery for this
> particular bug.
@Eric, I didn't handle it ine SRU because I don't understand the issu
** Changed in: ubuntu-z-systems
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1794478
Title:
Automatic ipv4 not assigned to bond in
The new stable version indicate the fix mentioned by seb128 is there but
no indication has been made in the debian/changelog to automatically
change the status, which breaks the SRU machinery for this particular
bug.
--- network-manager-1.10.6/src/nm-manager.c 2018-03-12 08:59:48.0
-0
The issue looks like it could be what is fixed by
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/34ca1680
(the change is included in 1.10.8 which is currently not yet in bionic
but being SRUed)
--
You received this bug notification because you are a member of Desktop
Packages
Indeed, sorry about that, I overlooked that this was on a bond and
tested with a bridge instead.
Here are the results with a bond:
$ cat /etc/netplan/50-cloud-init.yaml
network:
version: 2
ethernets:
eth0:
dhcp4: false
bonds:
bond0:
interfaces:
** Changed in: ubuntu-z-systems
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1794478
Title:
Automatic ipv4 not assigned to bond interface is
This is not reproducible with netplan in an Ubuntu 18.04 container (on
an Ubuntu cosmic host). With the following netplan config:
$ cat /etc/netplan/50-cloud-init.yaml
network:
version: 2
ethernets:
eth0:
dhcp4: false
bridges:
br0:
interfaces: [eth0
34 matches
Mail list logo