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:
Symlink on some devices disappears after running the 'insights-client --register' command.
Version-Release number of selected component (if applicable):
RHEL 8.7
How reproducible:
Always
Steps to Reproduce:
1. Check the devices
~~~
# ls -rtl /dev | grep sd
brw-rw----. 1 root disk 8, 0 Jun 9 02:45 sda
brw-rw----. 1 root disk 8, 1 Jun 9 02:45 sda1
~~~
2. Here ENV{ID_SERIAL_SHORT} is taken from the output of the following command
~~~
# udevadm info --query=all --name=/dev/sda1 | grep ID_SERIAL_SHORT
~~~
3. Create a symlink by creating the udev rule in '/etc/udev/rules.d/61-persistent-disk.rules' file:
~~~
ACTION=="add", ENV{ID_SERIAL_SHORT}=="2a3b8c45-487c-42cf-b87a-hr712b1mn12o", SYMLINK+="wlopt"
~~~
4. To load the udev rule(s) without rebooting the system, run the following command:
~~~
# /sbin/udevadm control --reload-rules
# /sbin/udevadm trigger --type=devices --action=add
~~~
5. Check the symlink:
~~~
# ls -rtl /dev | grep sd
brw-rw----. 1 root disk 8, 0 Jun 9 02:45 sda
brw-rw----. 1 root disk 8, 1 Jun 9 02:45 sda1
lrwxrwxrwx. 1 root root 4 Jun 9 02:45 wlopt -> sda1 <<<<==== New
~~~
6. Run the 'insights-client --register' command to register the host with Insights.
Actual results:
The new symlink disappears:
~~~
# ls -rtl /dev | grep sd
brw-rw----. 1 root disk 8, 0 Jun 9 02:47 sda
brw-rw----. 1 root disk 8, 1 Jun 9 02:47 sda1
~~~
Expected results:
The symlink should not disappear from the host.
The problem seems to be in the parted command that uses insights-core.
I will close this bug because is not an insights-client issue and there are other bugs to handle the root problem.
Description of problem: Symlink on some devices disappears after running the 'insights-client --register' command. Version-Release number of selected component (if applicable): RHEL 8.7 How reproducible: Always Steps to Reproduce: 1. Check the devices ~~~ # ls -rtl /dev | grep sd brw-rw----. 1 root disk 8, 0 Jun 9 02:45 sda brw-rw----. 1 root disk 8, 1 Jun 9 02:45 sda1 ~~~ 2. Here ENV{ID_SERIAL_SHORT} is taken from the output of the following command ~~~ # udevadm info --query=all --name=/dev/sda1 | grep ID_SERIAL_SHORT ~~~ 3. Create a symlink by creating the udev rule in '/etc/udev/rules.d/61-persistent-disk.rules' file: ~~~ ACTION=="add", ENV{ID_SERIAL_SHORT}=="2a3b8c45-487c-42cf-b87a-hr712b1mn12o", SYMLINK+="wlopt" ~~~ 4. To load the udev rule(s) without rebooting the system, run the following command: ~~~ # /sbin/udevadm control --reload-rules # /sbin/udevadm trigger --type=devices --action=add ~~~ 5. Check the symlink: ~~~ # ls -rtl /dev | grep sd brw-rw----. 1 root disk 8, 0 Jun 9 02:45 sda brw-rw----. 1 root disk 8, 1 Jun 9 02:45 sda1 lrwxrwxrwx. 1 root root 4 Jun 9 02:45 wlopt -> sda1 <<<<==== New ~~~ 6. Run the 'insights-client --register' command to register the host with Insights. Actual results: The new symlink disappears: ~~~ # ls -rtl /dev | grep sd brw-rw----. 1 root disk 8, 0 Jun 9 02:47 sda brw-rw----. 1 root disk 8, 1 Jun 9 02:47 sda1 ~~~ Expected results: The symlink should not disappear from the host.