Public bug reported:

[Impact]

 * Two regression tests fail due to a behavior change in recent Xenial
and Yakkety kernels

 * Adjusting the regression tests appropriately allows the kernel and
security teams to use QRT's test-apparmor.py to test kernel and
userspace AppArmor changes with confidence

[Test Case]

$ apt-get source apparmor
$ cd tests/regression/apparmor
$ make USE_SYSTEM=1
$ sudo bash stackonexec.sh
Error: transition failed. Test 'STACKONEXEC (stacked with unconfined - okcon)' 
was expected to 'pass'. Reason for failure 'FAIL - current mode "enforce" != 
expected_mode "mixed"'
Error: transition passed. Test 'STACKONEXEC (stacked with unconfined - bad 
mode)' was expected to 'fail'
$ sudo bash stackprofile.sh
Error: transition failed. Test 'STACKPROFILE (stacked with unconfined - okcon)' 
was expected to 'pass'. Reason for failure 'FAIL - current mode "enforce" != 
expected_mode "mixed"'

The two previous commands should result in no output and return value of 0 once
the regression test is properly updated.

[Regression Potential]

 * This is an extremely low risk change since it only touches regression
testing code that is not user-facing.

[Other Info]

 * This bug has already been fixed upstream:

   https://bazaar.launchpad.net/~apparmor-
dev/apparmor/master/revision/3505

** Affects: apparmor (Ubuntu)
     Importance: Low
     Assignee: Tyler Hicks (tyhicks)
         Status: In Progress

** Affects: apparmor (Ubuntu Trusty)
     Importance: Low
     Assignee: Tyler Hicks (tyhicks)
         Status: New

** Affects: apparmor (Ubuntu Xenial)
     Importance: Low
     Assignee: Tyler Hicks (tyhicks)
         Status: New

** Affects: apparmor (Ubuntu Yakkety)
     Importance: Low
     Assignee: Tyler Hicks (tyhicks)
         Status: In Progress

** Also affects: apparmor (Ubuntu Trusty)
   Importance: Undecided
       Status: New

** Also affects: apparmor (Ubuntu Yakkety)
   Importance: Low
     Assignee: Tyler Hicks (tyhicks)
       Status: In Progress

** Also affects: apparmor (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Changed in: apparmor (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: apparmor (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: apparmor (Ubuntu Xenial)
     Assignee: (unassigned) => Tyler Hicks (tyhicks)

** Changed in: apparmor (Ubuntu Trusty)
     Assignee: (unassigned) => Tyler Hicks (tyhicks)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1628295

Title:
  Change in kernel stacking behavior causes regression tests to fail

Status in apparmor package in Ubuntu:
  In Progress
Status in apparmor source package in Trusty:
  New
Status in apparmor source package in Xenial:
  New
Status in apparmor source package in Yakkety:
  In Progress

Bug description:
  [Impact]

   * Two regression tests fail due to a behavior change in recent Xenial
  and Yakkety kernels

   * Adjusting the regression tests appropriately allows the kernel and
  security teams to use QRT's test-apparmor.py to test kernel and
  userspace AppArmor changes with confidence

  [Test Case]

  $ apt-get source apparmor
  $ cd tests/regression/apparmor
  $ make USE_SYSTEM=1
  $ sudo bash stackonexec.sh
  Error: transition failed. Test 'STACKONEXEC (stacked with unconfined - 
okcon)' was expected to 'pass'. Reason for failure 'FAIL - current mode 
"enforce" != expected_mode "mixed"'
  Error: transition passed. Test 'STACKONEXEC (stacked with unconfined - bad 
mode)' was expected to 'fail'
  $ sudo bash stackprofile.sh
  Error: transition failed. Test 'STACKPROFILE (stacked with unconfined - 
okcon)' was expected to 'pass'. Reason for failure 'FAIL - current mode 
"enforce" != expected_mode "mixed"'

  The two previous commands should result in no output and return value of 0 
once
  the regression test is properly updated.

  [Regression Potential]

   * This is an extremely low risk change since it only touches
  regression testing code that is not user-facing.

  [Other Info]

   * This bug has already been fixed upstream:

     https://bazaar.launchpad.net/~apparmor-
  dev/apparmor/master/revision/3505

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1628295/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to