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.
DescriptionMichal Sekletar
2020-04-02 09:50:53 UTC
This bug was initially created as a copy of Bug #1814028
I am copying this bug because: if we introduce tape/by-path links for tape changers in RHEL-7 we should also provide in RHEL-8.
Description of problem:
Veritas (NetBackup) uses SAN connected tape devices with multiple paths. NetBackup is required to manage multiple paths to the SAN tape devices. The only way they can make this persistent through a boot is by using udev symlink's.
Version-Release number of selected component (if applicable): RHEL 6 - RHEL 8
How reproducible: Does not exist so every time.
Steps to Reproduce:
1.
2.
3.
Actual results: Manually need to create the symlink's
Expected results: Script to create symlink's such as from https://access.redhat.com/solutions/285703. This was created by Laurence Oberman and specified by NetBackup Engineering.
Additional info: A from Veritas NetBackup Engineering for this automation.
They will work with us to provide a full test environment.
https://access.redhat.com/solutions/285703
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Low: systemd security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2020:4553