dm-writeboost 2.2.6-1~16.04.2 ADT test failure with linux-hwe-edge 4.15.0-23.25~16.04.1

Bug #1777636 reported by Marcelo Cerri on 2018-06-19
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dm-writeboost (Ubuntu)
Undecided
Marcelo Cerri
Xenial
Undecided
Marcelo Cerri

Bug Description

[Impact]

Currently the DKMS package fails to install on supported custom
kernels that are based on 4.15. That includes the current 4.15
hwe-edge and some of the custom and cloud kernels as well.

[Test Case]

Install the dm-writeboost-dkms package with the 4.15 hwe-edge kernel. The
package installation should proceed without any errors.

[Regression Potential]

Although new patches were added, the regression risk is very low since
the new changes are conditionally compiled based on the kernel
version.

Besides that, the new package was tested with the following kernels in
an amd64 environment:

- linux-generic 4.4
- linux-hwe 4.13
- linux-hwe-edge 4.15
- linux-azure 4.15

[Original Description]

Testing failed on:
    amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/d/dm-writeboost/20180528_193648_1f08d@/log.gz
    armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/d/dm-writeboost/20180528_193945_1f08d@/log.gz
    i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/d/dm-writeboost/20180528_193900_1f08d@/log.gz
    ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/d/dm-writeboost/20180528_193841_1f08d@/log.gz
    s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/d/dm-writeboost/20180528_194034_1f08d@/log.gz

Marcelo Cerri (mhcerri) wrote :
tags: added: kernel-adt-failure
Marcelo Cerri (mhcerri) on 2018-06-19
description: updated
Marcelo Cerri (mhcerri) wrote :
tags: added: patch
Marcelo Cerri (mhcerri) on 2018-06-19
Changed in dm-writeboost (Ubuntu):
assignee: nobody → Marcelo Cerri (mhcerri)
status: New → In Progress
Tyler Hicks (tyhicks) on 2018-06-21
description: updated
Tyler Hicks (tyhicks) wrote :

Hey - This debdiff looks pretty good. I'd normally not sponsor it without proper patch tags but I see the patch you added is based on a patch that's in cosmic and it also doesn't have patch tags.

I've sponsored it to Xenial. Thanks!

Changed in dm-writeboost (Ubuntu Xenial):
assignee: nobody → Marcelo Cerri (mhcerri)
status: New → In Progress
Changed in dm-writeboost (Ubuntu):
status: In Progress → Invalid
Changed in dm-writeboost (Ubuntu Xenial):
status: In Progress → Fix Committed
Robie Basak (racb) wrote :

> Currently the DKMS package fails to install on supported custom
kernels that are based on 4.15. That includes the current 4.15
hwe-edge and some of the custom and cloud kernels as well.

Does this package work correctly against the equivalent kernels in Bionic and Cosmic please? Obviously they'd be different versions, but I'd like to ensure the spirit of the SRU rule about being fixed in the development release to avoid a regression where a user uses a particular kernel flavor, upgrades, and gets a failure.

Hello Marcelo, or anyone else affected,

Accepted dm-writeboost into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dm-writeboost/2.2.6-1~16.04.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

tags: added: verification-needed verification-needed-xenial
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments