Bug 866584
Summary: | udev properties are only shown after re-triggering | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Fabian Deutsch <fdeutsch> |
Component: | ovirt-node | Assignee: | Fabian Deutsch <fdeutsch> |
Status: | CLOSED DUPLICATE | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.4 | CC: | acathrow, bsarathy, dyasny, jboggs, mburns, mgoldboi, ovirt-bugs, ovirt-maint |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-10-19 13:40:41 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Fabian Deutsch
2012-10-15 16:39:27 UTC
An initial udevadm info after a boot without configured nics: [root@hp-xw4550-02 admin]# udevadm --debug info --query=all --path=/sys/class/net/eth3 run_command: calling: info udev_device_new_from_syspath: device 0x7f6f4fc5a6d0 has devpath '/devices/pci0000:00/0000:00:14.4/0000:07:04.0/net/eth3' P: /devices/pci0000:00/0000:00:14.4/0000:07:04.0/net/eth3 E: UDEV_LOG=6 E: DEVPATH=/devices/pci0000:00/0000:00:14.4/0000:07:04.0/net/eth3 E: INTERFACE=eth3 E: IFINDEX=5 E: SUBSYSTEM=net [root@hp-xw4550-02 admin]# Thus properties are not loaded. udev can be forced to load the properties by running: # udevadm test /sys/class/net/eth3 The properties will now be available. As mentioned on IRC, this setup renames the device while it runs, and it seemed to be done several times in one and the same event. Also the rules change during bootup by over-mounting them. Something along all these rather "exotic" setup steps causes some hickup. Sorry, I have no idea what goes wrong here. It seems, the simplest workaround would be to 'trigger' all network interfaces again after bootup, and 'settle' again before anything tries to access any udev device data that is in the process of being mangled that way. (In reply to comment #9) > As mentioned on IRC, this setup renames the device while it runs, and it > seemed > to be done several times in one and the same event. Also the rules change > during bootup by over-mounting them. Something along all these rather > "exotic" setup steps causes some hickup. Sorry, I have no idea what goes > wrong here. Just a note here: I could also reproduce this on a default RHEL6 machine (see comment above) which hasn't got this exotic setup. The base issue in udev can't/won't be solved in RHEL 6. We handle this issue with the fix in bug 866585 *** This bug has been marked as a duplicate of bug 866585 *** |