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.
Bug 2158914 - "stratis debug uevent" command fails with "unexpected keyword argument 'strict'"
Summary: "stratis debug uevent" command fails with "unexpected keyword argument 'strict'"
Keywords:
Status: CLOSED ERRATA
Alias: None
Deadline: 2023-01-30
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: stratis-cli
Version: 9.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Bryan Gurney
QA Contact: Filip Suba
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-01-06 21:59 UTC by Bryan Gurney
Modified: 2023-05-09 08:49 UTC (History)
4 users (show)

Fixed In Version: stratis-cli-3.4.1-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-09 07:41:26 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-144217 0 None None None 2023-01-06 22:23:17 UTC
Red Hat Product Errata RHBA-2023:2273 0 None None None 2023-05-09 07:41:28 UTC

Description Bryan Gurney 2023-01-06 21:59:12 UTC
Description of problem:
The stratis-cli command has a sub-command, "stratis debug uevent", which generates a synthetic uevent for a device.  (This is helpful for cases where the size of the device has increased, and the administrator wants stratisd to detect the new size of the device.)

The command currently fails with the following error:
Execution failed:
stratis reported an error in generating a synethetic udev event: Failed to send synth event: realpath() got an unexpected keyword argument 'strict' 


Version-Release number of selected component (if applicable):
stratis-cli-3.4.0-1.el9.noarch

How reproducible:
100%


Steps to Reproduce:
1. Run the "stratis debug uevent" command on a block device:
# stratis debug uevent /dev/nvme0n1p2

Actual results:
The command fails with the following error:
Execution failed:
stratis reported an error in generating a synethetic udev event: Failed to send synth event: realpath() got an unexpected keyword argument 'strict' 


Expected results:
The command succeeds, and a synthetic uevent is generated.

Additional info:

Comment 6 Filip Suba 2023-01-23 14:24:48 UTC
Verified with stratis-cli-3.4.1-1.el9.

Comment 8 errata-xmlrpc 2023-05-09 07:41:26 UTC
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 (stratis-cli 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/RHBA-2023:2273


Note You need to log in before you can comment on or make changes to this bug.