test_520_config_random_trust_cpu in ubuntu_qrt_kernel_security fail with B-OEM-OSP1

[Po-Hsu Lin]

== SRU Justification ==
The ubuntu_qrt_kernel_security test from Security Team require that the RANDOM_TRUST_CPU config must be enabled for kernel >= 5.0.0

== Test ==
Tested with a kernel built with this config enabled, it will pass the config check in test test_520_config_random_trust_cpu.

== Regression Potential ==
Low.
As stated in bug 1823754, no user-visible regressions are expected.
The config is already enabled in the Disco generic/master.

FAIL: test_520_config_random_trust_cpu (__main__.KernelSecurityConfigTest)
 Ensure RANDOM_TRUST_CPU is enabled (LP: #1823754)
 ----------------------------------------------------------------------
 Traceback (most recent call last):
 File "./test-kernel-security.py", line 2840, in test_520_config_random_trust_cpu
 self.assertKernelConfig('RANDOM_TRUST_CPU', expected)
 File "./test-kernel-security.py", line 208, in assertKernelConfig
 self.assertKernelConfigSet(name)
 File "./test-kernel-security.py", line 195, in assertKernelConfigSet
 '%s option was expected to be set in the kernel config' % name)
 AssertionError: RANDOM_TRUST_CPU option was expected to be set in the kernel config

[Tyler Hicks (tyhicks)]

Timo, could you enable CONFIG_RANDOM_TRUST_CPU in linux-oem-osp1? It isn't an SRU cycle blocker but it would be good if the config option was enabled for the next cycle. Thanks!

[Po-Hsu Lin (cypressyew)]

https://lists.ubuntu.com/archives/kernel-team/2019-May/100752.html

[Timo Aaltonen (tjaalton)]

I'm not sure why the config change didn't make it to debian.oem-osp1..

[Timo Aaltonen (tjaalton)]

is fixed in the kernel now