Bug 2213749
| Summary: | Symlink on some devices disappear after running the 'insights-client --register' command on the host. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Nikhil Gupta <ngupta> |
| Component: | insights-client | Assignee: | CSI Client Tools Bugs <csi-client-tools-bugs> |
| Status: | NEW --- | QA Contact: | Red Hat subscription-manager QE Team <rhsm-qe> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 8.7 | CC: | ahitacat, cmarinea, fjansen, pakotvan, stomsa |
| Target Milestone: | rc | Flags: | ngupta:
needinfo?
(ahitacat) |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 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 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.