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:
The program behaves unexpectedly, ie. against manpage/help when script internal variables are exported by the user.
Version-Release number of selected component (if applicable):
mdevctl-0.78-1.el8.noarch
How reproducible:
100%
Steps to Reproduce:
1. User's environment exports some variable values for whatever reason
export uuid=35e06c5e-a1d4-41cf-9c1b-0483f9e603fb
export type=mdev_bus
2. They define a new device (expecting uuid to be generated and returned as by manpage)
mdevctl define -t vfio_ccw-io -p 0.0.26aa
3. They think they did something wrong because the uuid is not returned, but luckily mdevctl list -d lists the uuid
4. They start the device
mdevctl start -u 35e06c5e-a1d4-41cf-9c1b-0483f9e603fb
Actual results:
a. uuid not printed after 2.
b. help text is shown after 4.
Expected results:
a. uuid printed after 2.
b. device is started
Additional info:
This seems to happen to come from global variable usage in the mdevctl script. IMO, any local variable should be isolated and not interfere with the user exported variables OR declare they're usage, if intended, in the manual/help.
Setting TestOnly expecting this to be solved by the linked rebase.
Expected scope: manual confirmation test, no system level regression test as it's covered by design (Rust).
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 (mdevctl 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-2022:1922