RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 866584 - udev properties are only shown after re-triggering
Summary: udev properties are only shown after re-triggering
Keywords:
Status: CLOSED DUPLICATE of bug 866585
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Fabian Deutsch
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-15 16:39 UTC by Fabian Deutsch
Modified: 2016-04-26 13:32 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-19 13:40:41 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Fabian Deutsch 2012-10-15 16:39:27 UTC 
Description of problem:
Udev properties are used to e.g. determin the model or vendor of a NIC. After boot, not all udev properties are determined properly.

Version-Release number of selected component (if applicable):
Current

How reproducible:
Always

Steps to Reproduce:
1. Clean install
2. No nic configuration
3. Dro to shell and run:
4. udevadm info --query=all --path/sys/class/net/eth0
  
Actual results:
Some properties are shown, but nothing like e.g. VENDOR_INFO_FROM_DATABASE (or what it is called)

Expected results:
More properties are shown, including e.g. VENDOR_INFO_FROM_DATABASE (or what it is called)

Additional info:
Comment 5 Fabian Deutsch 2012-10-17 06:33:18 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.
Comment 9 Kay Sievers 2012-10-17 12:23:15 UTC 
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.
Comment 10 Fabian Deutsch 2012-10-18 05:08:18 UTC 
(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.
Comment 11 Mike Burns 2012-10-19 13:40:41 UTC 
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 ***
Note You need to log in before you can comment on or make changes to this bug.