** Description changed:

+ [Impact]
+ 
+  * bridge_role property setting is racy on boot
+ 
+  * This results in incorrect bridge mode set on the devices, sometimes,
+ which leads to lack of desired connectivity (e.g. bridging internet to
+ containers)
+ 
+  * The fix for this issue is to set bridge_role, only after the device
+ is online
+ 
+  * Unfortunately the udev rules are not regenerated, therefore affected
+ systemd must manually remove and recreate chzdev rules
+ 
+ [Test Case]
+ 
+  * Remove qeth udev rules from /etc/udev/rules.d/
+  * Enable qeth device using chzdev with a non-default bridge_role setting, 
e.g.:
+    chzdev --no-root-update -pVe c003 bridge_role=primary;
+  * Reboot and check that bridge_role setting is correctly set in the sysfs, 
e.g.:
+    /sys/devices/qeth/0.0.c003/bridge_role
+ 
+ [Regression Potential]
+ 
+  * Minimal, the generated udev rules remain the same; the only
+ difference in the generated udev rules is the ordering in setting the
+ bridge_role attribute
+ 
+ [Other Info]
+  
+  * Original bug report:
+ 
  Attempting to set bridge_role = primary with the following command in
  preseed:
  
  in-target chzdev --no-root-update -pVe c003 bridge_role=primary;
  
  ...works, and generates the following udev rule for this device:
  
  https://pastebin.canonical.com/164271/
  
  However, after reboot:
  
  systemd-udevd[2634]: error opening
  ATTR{/sys/devices/qeth/0.0.c003/bridge_role} for writing: Permission
  denied
  
  More logging:
  
  https://pastebin.canonical.com/164272/
  
  after the system has booted, we are able to write to the file and set
  bridge_role to primary:
  
- root@10-13-3-10:/var/log# cat /sys/devices/qeth/0.0.c003/bridge_role 
+ root@10-13-3-10:/var/log# cat /sys/devices/qeth/0.0.c003/bridge_role
  none
  root@10-13-3-10:/var/log# echo primary > 
/sys/devices/qeth/0.0.c003/bridge_role
- root@10-13-3-10:/var/log# cat /sys/devices/qeth/0.0.c003/bridge_role 
+ root@10-13-3-10:/var/log# cat /sys/devices/qeth/0.0.c003/bridge_role
  primary

** Also affects: s390-tools (Ubuntu Yakkety)
   Importance: Undecided
       Status: New

** Also affects: s390-tools (Ubuntu Zesty)
   Importance: Undecided
     Assignee: Dimitri John Ledkov (xnox)
       Status: Fix Committed

** Also affects: s390-tools (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Changed in: s390-tools (Ubuntu Yakkety)
     Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: s390-tools (Ubuntu Xenial)
     Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: s390-tools (Ubuntu Zesty)
    Milestone: None => ubuntu-17.03

** Changed in: s390-tools (Ubuntu Yakkety)
    Milestone: None => yakkety-updates

** Changed in: s390-tools (Ubuntu Xenial)
    Milestone: None => xenial-updates

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618463

Title:
  udev race condition with qeth device and bridge_role

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1618463/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to