fix(docker): fix set kernel perf event paranoid set

[soyacz]

When using docker and setting print_kernel_callstack param we need to set kernel.perf_event_paranoid=0 - which didn't work due missing params and proper privileges for docker.

refs: #10633

Testing

• - tested locally with docker backend

PR pre-checks (self review)

• I added the relevant backport labels
• I didn't leave commented-out/debugging code

Reminders

• Add New configuration option and document them (in sdcm/sct_config.py)
• Add unit tests to cover my changes (under unit-test/ folder)
• Update the Readme/doc folder relevant to this change (if needed)

[Copilot]

Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.

Files not reviewed (1)

• docker/scylla-sct/centos/Dockerfile: Language not supported

Comments suppressed due to low confidence (1)

sdcm/cluster_docker.py:59

• Using bool() directly on the print_kernel_callstack parameter may lead to unexpected behavior if the parameter is provided as a non-boolean value (e.g., the string 'false'). Consider converting or validating the parameter to explicitly obtain a boolean value.

privileged = bool(self.parent_cluster.params.get('print_kernel_callstack'))

[yaronkaikov]

Thanks @soyacz

[yaronkaikov]

@lsfreitas FYI

[soyacz]

@lsfreitas FYI

this is not solving the original issue, just helps with mentioned error when setting this system setting.

[vponomaryov]

@soyacz I don't think we should update the kernel.perf_event_paranoid host config option on docker backend.
With this change everyone running a docker SCT test will get this option changed on his/her machine.

I think we should update the related SCT config option instead:

print_kernel_callstack: false

[soyacz]

@soyacz I don't think we should update the kernel.perf_event_paranoid host config option on docker backend. With this change everyone running a docker SCT test will get this option changed on his/her machine.

hmm, yes, that seems to be true. Better not change host settings.

I think we should update the related SCT config option instead:

print_kernel_callstack: false

so, I'd propose to disable it at code by adding and not self.is_docker() level in condition, as anyway it is not working and won't generate unrelevant errors. We could consider adding a warning that we skip it.:

if self.node_type == "db" and not self.is_kubernetes() \
                and self.parent_cluster.params.get("print_kernel_callstack"):

[soyacz]

wrong approach. closing