Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/2858
** Bug watch added: github.com/canonical/cloud-init/issues #2858
https://github.com/canonical/cloud-init/issues/2858
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
This bug is believed to be fixed in cloud-init in 17.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ker
This bug was fixed in the package linux - 4.4.0-83.106
---
linux (4.4.0-83.106) xenial; urgency=low
* linux: 4.4.0-83.106 -proposed tracker (LP: #1700541)
* CVE-2017-1000364
- Revert "UBUNTU: SAUCE: mm: Only expand stack if guard area is hit"
- Revert "mm: do not collapse
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1682871
Title:
attempts to rename vlans / vlans have addr_
** Changed in: cloud-init
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1682871
Title:
attempts to rename vlans / vlans have addr_assign_type o
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~17.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~17.04.1) zesty; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream snapshot.
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.10.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.10.1) yakkety; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream snapshot.
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
** Changed in: linux (Ubuntu Xenial)
Assignee: Canonical Kernel (canonical-kernel) => Kleber Sacilotto de Souza
(kleber-souza)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1682871
Verified yakkety and zesty
for release in yakkety zesty; do ./get-proposed-cloudimg $release; done
--2017-05-12 13:04:0
MODE=vlan ./btest.sh yakkety-server-cloudimg-amd64-proposed.img chad.smith
...
# login
ubuntu@ubuntu:~$ python3 -c 'from cloudinit.net import get_interfaces_by_mac;
print(get_
** Changed in: linux (Ubuntu Yakkety)
Status: New => Fix Released
** Changed in: linux (Ubuntu Zesty)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
Thank you for confirming the fix. The patch was sent to the Canonical
Kernel Team mailing list for review of inclusion on Xenial kernel SRU.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1
** Changed in: linux (Ubuntu Xenial)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1682871
Title:
attempts to rename vlans / vlans have addr_assign
Hello Scott, or anyone else affected,
Accepted cloud-init into zesty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/0.7.9-113-g513e99e0-0ubuntu1~17.04.1 in a few hours, and then in
the -proposed repository.
Please help us by testing this
Hello Scott, or anyone else affected,
Accepted cloud-init into yakkety-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/cloud-
init/0.7.9-113-g513e99e0-0ubuntu1~16.10.1 in a few hours, and then in
the -proposed repository.
Please help us by testing thi
Verified cloud-init xenial
$ ./get-proposed-cloudimg xenial
--2017-05-11 14:11:13--
http://cloud-images.ubuntu.com/daily/server/xenial/current/xenial-server-cloudimg-amd64-disk1.img
...
xenial-server-cloud 100%[===>] 273.75M 9.87MB/sin 2m 29s
2017-05-11 14:13:42 (1.83 MB/s)
Hello Scott, or anyone else affected,
Accepted cloud-init into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/0.7.9-113-g513e99e0-0ubuntu1~16.04.1 in a few hours, and then in
the -proposed repository.
Please help us by testing this
** Changed in: cloud-init (Ubuntu Yakkety)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu Zesty)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu Yakkety)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu Zesty)
Importance: Undecided => M
** Also affects: linux (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Zesty
Hi Scott,
Did you have a chance to test the patched Xenial kernel to check whether
is fixes the issue on the kernel side?
Thank you.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1682871
** Description changed:
[Impact]
* When vlan interfaces are created, their mac address is copied from
the underlying interface, but it is not marked by kernel as stolen.
* When underlying interface MAC address is changed, it does not
propagate to the vlan interfaces.
[Test C
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1) artful; urgency=medium
* New upstream snapshot.
- nova-lxd: read product_name from environment, not platform.
(LP: #1685810)
- Fix yum repo config
Hi,
Could you please try the following patched kernel and check if it fixes
the issue?
PPA: https://launchpad.net/~kleber-souza/+archive/ubuntu/ppa
Package: linux=4.4.0-74.95+lp1682871v1
Thank you in advance.
--
You received this bug notification because you are a member of Kernel
Packages, wh
I am building a xenial test kernel with the patch attached on comment
#2. I will post the link here once it's ready.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1682871
Title:
attempt
** Merge proposal linked:
https://code.launchpad.net/~xnox/cloud-init/+git/cloud-init/+merge/322828
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1682871
Title:
attempts to rename vl
Hm, I don't think you will win much here. vlans made from a bond have
addr_assign_type 3.
root@xnox-iad-16:/sys/class/net# uname -r
4.8.0-46-generic
root@xnox-iad-16:/sys/class/net# grep -e 0 -e 1 -e 2 -e 3 */addr_assign_type
bond0.101/addr_assign_type:3
bond0.401/addr_assign_type:3
bond0/addr_as
The cloud init patch needs work...
>>> interface_has_own_mac('bonding_masters')
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/cloudinit/net/__init__.py", line 226, in
interface_has_own_mac
uevent = read_sys_net_safe(ifname, 'uevent').splitlin
** Patch added: "vlans-steal-mac-addresses.patch"
https://bugs.launchpad.net/cloud-init/+bug/1682871/+attachment/4864966/+files/vlans-steal-mac-addresses.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
Adding a cloud-init workaround patch for kernels before 4.7 too.
** Description changed:
[Impact]
- * When vlan interfaces are created, their mac address is copied from
+ * When vlan interfaces are created, their mac address is copied from
the underlying interface, but it is not marked b
** Tags added: patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1682871
Title:
attempts to rename vlans / vlans have addr_assign_type of 0 on kernel
4.4
Status in cloud-init:
Co
** Description changed:
+ [Impact]
+
+ * When vlan interfaces are created, their mac address is copied from
+ the underlying interface, but it is not marked by kernel as stolen.
+
+ * When underlying interface MAC address is changed, it does not
+ propagate to the vlan interfaces.
+
+ [Test C
I wonder if this really should go to linux-stable too.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1682871
Title:
attempts to rename vlans / vlans have addr_assign_type of 0 on kernel
32 matches
Mail list logo
