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.
[Hyper-V][RHEL9] “wireplumber: stack traceback: in function 'string.find' for 'isBluez5AudioSink' ” exists in journalctl log after done leapp update from RHEL 8.7 to RHEL 9.0
Description of problem:
After do leapp upgrade from RHEL 8.7 to RHEL 9.0, check the journalctl log, there is “stack traceback: in function 'string.find' for 'isBluez5AudioSink' ".
Host:
Hyper-V 2019 host
RHEL Version:
RHEL-8.7.0-20220802.0
Kernel Version:
RHEL 8.7 kernel : 4.18.0-413.el8.x86_64
RHEL 9.0 kernel: 5.14.0-70.13.1.el9_0.x86_64
Wirelumber version:
wireplumber-libs-0.4.8-1.el9.x86_64
wireplumber-0.4.8-1.el9.x86_64
Leapp package:
leapp-0.14.0-100.20220727105923461008.master.23.g85d7548.noarch
leapp-upgrade-el8toel9-0.16.0-100.20220801115100511502.master.71.g40af46c.el8.noarch
leapp-repository-deps-el9-5.0.9-100.202208011150Z.40af46c.master.el9.noarch
How reproducible:
100%
Steps to Reproduce:
1. Start a VM of RHEL-8.6.0-20220802.0
2. Do leapp upgrade by following the guide with “no RHSM” method.
3. Check journalctl logs by # journalctl -a | grep -i 'traceback'
Actual results:
“stack traceback: in function 'string.find' for 'isBluez5AudioSink' " exists in the journalctl log
Expected results:
No traceback log in journalctl.
Additional info:
This should be a general issue, but cannot reproduce it if directly booting up RHEL 9.0 or RHEL 9.1 build.
Maybe it is similar with https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/193, which has been fixed by wireplumber to version 0.4.9 @ https://gitlab.freedesktop.org/pipewire/wireplumber/-/releases. Currently RHEL 9.0/9.1 downstream only rebases wireplumber to version 0.4.8.
Detailed logs:
10 16:39:44 LISAv2-OneVM-2022-GQ22-637957404235-role-0 systemd[4348]: Stopping PipeWire PulseAudio...
Subject: A stop job for unit UNIT has begun execution
Defined-By: systemd
Support: https://access.redhat.com/support
A stop job for unit UNIT has begun execution.
The job identifier is 48.
Aug 10 16:39:44 LISAv2-OneVM-2022-GQ22-637957404235-role-0 wireplumber[4821]: [string "policy-bluetooth.lua"]:121: bad argument #1 to 'find' (string expected, got nil)
stack traceback:
[C]: in function 'string.find'
[string "policy-bluetooth.lua"]:121: in upvalue 'isBluez5AudioSink'
[string "policy-bluetooth.lua"]:389: in function <[string "policy-bluetooth.lua"]:387>
Aug 10 16:39:44 LISAv2-OneVM-2022-GQ22-637957404235-role-0 systemd[4348]: Stopped PipeWire PulseAudio.
It looks like this was also found and fixed upstream: https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/193
xuli, would you mind testing with the latest RHEL 9 nightlies or CentOS Stream? We did a wireplumber rebase there, which should fix this issue