test_520_config_random_trust_cpu in ubuntu_qrt_kernel_security failed with 5.0 kernel

[Po-Hsu Lin]

Failure found on B-hwe-edge kernel on P8 / i386 (difficulties with deployment for ARM64 / AMD64).

In disco, this option was enabled:
$ grep RANDOM_TRUST_CPU ~/ubuntu-disco/debian.master/config/config.common.ubuntu
CONFIG_RANDOM_TRUST_CPU=y

$ grep RANDOM_TRUST_CPU ~/ubuntu-disco/debian.master/config/annotations
CONFIG_RANDOM_TRUST_CPU policy<{'amd64': 'y', 'i386': 'y', 'ppc64el': 'y', 's390x': 'y'}>

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 2835, 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

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1825280

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Tyler Hicks (tyhicks)]

This shouldn't be a blocker to release the B-hwe-edge kernel but it is something that we'll want to fix in that kernel's config soon.

[Tyler Hicks (tyhicks)]

Bionic linux-hwe-edge 5.0.0-13.14~18.04.1 has this config option set. Rerunning this test against that kernel will result in a passing test.

[Steve Beattie (sbeattie)]

Confirmed that this has been fixed in the linux-hwe-edge kernel config. Closing.

Thanks!