udevd: failed to rename network device
Bug #1523117 reported by
Ivan Suzdal
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Ivan Suzdal |
Bug Description
We have race condition between setup-bootdev and udevd. In setup-bootdev we are run udevadm trigger which go to race condition with systemd-udevd service in some cases.
summary: |
- Race condition between setup-bootdev and systemd-udev service. + udevd: failed to rename network device |
information type: | Public → Private |
description: | updated |
information type: | Private → Proprietary |
information type: | Proprietary → Private |
Changed in mos: | |
status: | New → Fix Released |
Changed in mos: | |
status: | Fix Released → In Progress |
description: | updated |
description: | updated |
information type: | Private → Public |
Changed in mos: | |
status: | In Progress → Fix Committed |
Changed in fuel: | |
status: | New → Fix Committed |
importance: | Undecided → High |
assignee: | nobody → Ivan Suzdal (isuzdal) |
milestone: | none → 8.0 |
no longer affects: | mos |
tags: | added: area-python |
To post a comment you must log in.
During start services, systemd require sd_notify support for guarantee what service will started _only_ after another service was successfully started, we can to handle this in our setup-bootdev without adding support sd_notify.