Bug 2117550

Summary: [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
Product: Red Hat Enterprise Linux 9 Reporter: xuli <xuli>
Component: wireplumberAssignee: Wim Taymans <wtaymans>
Status: CLOSED CURRENTRELEASE QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 9.0CC: litian, ndegraef, xuli, xxiong, yacao, yuxisun
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-07-11 08:53:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description xuli 2022-08-11 09:50:49 UTC 
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.
Comment 3 Niels De Graef 2023-07-07 08:45:43 UTC 
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