udevd: failed to rename network device

Bug #1523117 reported by Ivan Suzdal
6
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.

Tags: area-python
Ivan Suzdal (isuzdal)
summary: - Race condition between setup-bootdev and systemd-udev service.
+ udevd: failed to rename network device
Ivan Suzdal (isuzdal)
information type: Public → Private
description: updated
information type: Private → Proprietary
information type: Proprietary → Private
Ivan Suzdal (isuzdal)
Changed in mos:
status: New → Fix Released
Ivan Suzdal (isuzdal)
Changed in mos:
status: Fix Released → In Progress
Revision history for this message
Ivan Suzdal (isuzdal) wrote :

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.

Changed in mos:
importance: Critical → High
Revision history for this message
Dmitry Teselkin (teselkin-d) wrote :

Attaching part of /var/log/messages from the node where this error occurred. There are two files, both from the same node, failed one was found in a snapshot, and successful log was taken from the same node after a reboot (no other changes made).

Revision history for this message
Dmitry Teselkin (teselkin-d) wrote :

Just in case, content of /var/log from the same node

Ivan Suzdal (isuzdal)
description: updated
description: updated
Ivan Suzdal (isuzdal)
information type: Private → Public
Revision history for this message
Ivan Suzdal (isuzdal) wrote :

There is request which should fix this issue
https://review.openstack.org/#/c/253843/

Ivan Suzdal (isuzdal)
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
Revision history for this message
Timur Nurlygayanov (tnurlygayanov) wrote :

It looks like the issue was successfully fixed in MOS 8.0, moved to Fix Released.

Please update the status and provide the additional information if this issue will be reproduced again.

Changed in fuel:
status: Fix Committed → Fix Released
Revision history for this message
Alexander Gordeev (a-gordeev) wrote :

probably fixed by this change https://review.openstack.org/#/c/270008/

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.