Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
udev events are not available inside of an SPC (super privileged container), but some components (like vdsm from RHEV) require those events to work correctly.
We need a way to retrieve the udev events inside the container.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. run any SPC
2. On the host run udevadm monitor --udev --env
3. In the container run udevadm monitor --udev --env
4. On the host run udevadm trigger --action=change --subsystem-match=block
Actual results:
udevadm on the host shows the udev events
udevadm in the container does not show the udev events
Expected results:
udevadm in the container shows the udev events
Additional info:
Time has passed.
A nice way to get custom udev rules onto the host might be, to use LABELs to name the udev rules which should be copied frmo the container onto the host.
I.e.
LABEL org.storaged.udev.rules /etc/…/foo.rule
This rule would be copied to the host each time a new image is deployed.
This drops the burden from the image/container to move the rule to the right place.
There is just a component needed on the host side to perform this acton.
This idea actually comes from cadvisor who is using labels to expose config files inside a container.
In addition: By dropping most namespaces and bindmounting /runevents should get inside of a container.