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.
It is possible to have an initiator name that contains non-unicode characters. Because UDisks DBus API provides only function to get initiator name as a string, UDisks will for a non-unicode initiator name return string "Invalid UTF-8".
We need to provide a function that returns bytearray so users of the API can work with such initiator names.
This functionality is already available in upstream -- https://github.com/storaged-project/udisks/pull/645
Comment 1guazhang@redhat.com
2019-05-29 09:32:52 UTC
Hello
QE need reproducer here so that we will add it to automation ?
thanks
Guazhang
This adds a new API function, it can be tested using busctl
```
$ busctl call org.freedesktop.UDisks2 /org/freedesktop/UDisks2/Manager org.freedesktop.UDisks2.Manager EnableModules "b" 1
$ busctl call org.freedesktop.UDisks2 /org/freedesktop/UDisks2/Manager org.freedesktop.UDisks2.Manager.ISCSI.Initiator GetInitiatorNameRaw
ay 36 105 113 110 46 49 57 57 52 45 48 53 46 99 111 109 46 114 101 100 104 97 116 58 50 53 54 53 54 99 102 52 57 52 98 49 0
```
Part of the upstream PR is also a new test case, so it will be run in the gating CI together with other tests from the upstream test suite.
Comment 4guazhang@redhat.com
2019-06-18 11:04:36 UTC
Hello
Get the test info, the GetInitiatorNameRaw was str, so move to verified.
'busctl call org.freedesktop.UDisks2 /org/freedesktop/UDisks2/Manager org.freedesktop.UDisks2.Manager EnableModules 'b' 1'...
INFO: [2019-06-18 07:01:28] Running: 'busctl call org.freedesktop.UDisks2 /org/freedesktop/UDisks2/Manager org.freedesktop.UDisks2.Manager.ISCSI.Initiator GetInitiatorNameRaw '...
ay 36 105 113 110 46 49 57 57 52 45 48 53 46 99 111 109 46 114 101 100 104 97 116 58 102 55 54 48 99 100 56 52 49 52 53 100 0
INFO: get the GetInitiatorNameRaw ay 36 105 113 110 46 49 57 57 52 45 48 53 46 99 111 109 46 114 101 100 104 97 116 58 102 55 54 48 99 100 56 52 49 52 53 100 0 and the type was <class 'str'>
thanks
Guazhang
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, 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/RHBA-2019:3459