Thx for the re-test and update - with that I'm closing this ticket now.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: ubuntu-z-systems
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Kernel
[Expired for iproute2 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: iproute2 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching
** Tags added: fr-585
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/1838258
Title:
Unable to configure VLAN on an additional OSA interface
Status
It is unclear how to reproduce the issue.
So far, I always have multiple VLANs configured and accessible. The only
time I see errors similar to the ones from the reporter, is when the
same vlan with the same name is configured multiple times in a row
(which is an input/configuration error)
This
Something is odd executing the command twice in a row does produce the
same error message
$ sudo ip link add link encc003 name encc003.2653 type vlan id 2653
(exits zero, creates vlan interface)
$ sudo ip link add link encc003 name encc003.2653 type vlan id 2653
RTNETLINK answers: File exists
Unfortunately the logs are not that helpful, since VLAN additions are
not printed in the dmesg/syslog/journal. I.e. one needs to bump udev
logging to be more verbose.
Locally I can activate multiple NICs and like same vlan on both of them:
$ ip link | grep '^[0-9]'
1: lo: mtu 65536 qdisc
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin18043
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/1838258
Title:
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Canonical Foundations Team
(canonical-foundations)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
** Tags added: id-5d3f1092c9ff2f192b03a448
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/1838258
Title:
Unable to configure VLAN on an additional
Hi Michael,
looks like we added our comments and files in parallel.
I guess it's okay for now ...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/1838258
Here are more details from my setup...
@Bug reporter, please share your details and logs as well!
** Attachment added: "recreate.txt"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1838258/+attachment/5279822/+files/recreate.txt
--
You received this bug notification because you
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1838258/+attachment/5279825/+files/syslog
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
** Attachment added: "journalctl.txt"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1838258/+attachment/5279824/+files/journalctl.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1838258/+attachment/5279823/+files/dmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
Looks I can re-create this issue.
Just as a workaround, one may edit /etc/netplan/01-netcfg.yaml
do the configuration in a persistent way there and do a netplan apply:
$ sudo netplan apply --dryrun
$ sudo netplan apply
Please notice that you should have your system always on the latest level -
What's the output of: $ ip a ?
Also matching dmesg / syslog / journal?
--
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/1838258
Title:
Unable to configure VLAN on an additional OSA
16 matches
Mail list logo
