linux 4.17.0-3.4 ADT test failure with linux 4.17.0-3.4

[Seth Forshee]

Testing failed on:
    amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-bootstrap/cosmic/amd64/l/linux/20180629_050011_b6306@/log.gz
    arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-bootstrap/cosmic/arm64/l/linux/20180629_071913_b6306@/log.gz
    i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-bootstrap/cosmic/i386/l/linux/20180629_061018_b6306@/log.gz
    ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-bootstrap/cosmic/ppc64el/l/linux/20180629_053838_b6306@/log.gz
    s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-bootstrap/cosmic/s390x/l/linux/20180629_045904_b6306@/log.gz

[Seth Forshee (sforshee)]

First failure:

  ======================================================================
  FAIL: test_075_config_stack_protector (__main__.KernelSecurityTest)
  CONFIG_CC_STACKPROTECTOR set
  ----------------------------------------------------------------------
  Traceback (most recent call last):
    File "./test-kernel-security.py", line 921, in test_075_config_stack_protector
      self.assertEqual(self._get_config('CC_STACKPROTECTOR'), expected)
  AssertionError: None != 'y'

  ----------------------------------------------------------------------

Test needs to be updated for changes in kernel config options.

[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 1779314

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.

[Seth Forshee (sforshee)]

Second failure:

  ======================================================================
  FAIL: test_7 (__main__.AaTest_get_interpreter_and_abstraction)
  test '#!/usr/bin/python'
  ----------------------------------------------------------------------
  Traceback (most recent call last):
    File "/tmp/testlibpNQhZk/source/cosmic/apparmor-2.12/utils/test/common_test.py", line 88, in stub_test
      self._run_test(test_data, expected)
    File "test-aa.py", line 187, in _run_test
      self.assertEqual(interpreter_path, exp_interpreter_path)
  AssertionError: '/usr/bin/python2.7' != '/usr/bin/python2'
  - /usr/bin/python2.7
  ? --
  + /usr/bin/python2

Which seems to be an issue with the test itself.

[Steve Beattie (sbeattie)]

The CONFIG_CC_STACKPROTECTOR issue was addressed in bug 1776242, leaving the apparmor test failure to resolve.

[Steve Beattie (sbeattie)]

For the apparmor failure, this is caused by /usr/bin/python being a symlink to python2, which is in turn a symlink to python2.7, which caught the tests unprepared to handle nested symlinks like that. A fix has been proposed at https://gitlab.com/apparmor/apparmor/merge_requests/147 and committed to the qa-regression-testing tree in https://git.launchpad.net/qa-regression-testing/commit/?id=30c513e222cadc8abe24463cefadce53bf0e277a .

Thanks.