Disable service_enabled templated test for service_bluetooth_disabled #12211
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
Disable test scenario that tries to start bluetooth service and then expect it to fail.
Rationale:
The service is dependent on loaded
btusb
kernel module. However, this module is not loaded by default and templated test scenario doesn't load it either.We had similar problem in the past #11949 and now it started happening also on RHEL 8.8 and 9.2. I tried it manually on those systems and to properly start the service, I had to
modprobe btusb
(https://wiki.archlinux.org/title/Bluetooth#Installation). It will be better to disable the test scenario completely rather than creating Contest waiver.Review Hints:
Try Automatus for
service_bluetooth_disabled
and see what test scenarios are not run.