test_mbr_image_partitions fails on disco+ version of pyparted
Bug #1826224 reported by
Łukasz Zemczak
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu Image |
Fix Released
|
High
|
Łukasz Zemczak | ||
| ubuntu-image (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
It seems something changed in pyparted 3.11.2 and higher, causing the resulting partition structure to have one more field - 'grain' seems to have been added. Other than that, it seems to work as previously. But it currently cause a failure in one of our unit tests, possibly making it even FTBFS.
| description: | updated |
| Changed in ubuntu-image: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in ubuntu-image (Ubuntu): | |
| status: | New → Fix Released |
| Changed in ubuntu-image: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This bug was fixed in the package ubuntu-image - 1.7+19.10ubuntu1
---------------
ubuntu-image (1.7+19.10ubuntu1) eoan; urgency=medium
[ Maciej Borzecki ]
* Some parser improvements: more strict schema for volume names, make sure
structure names are unique. (LP: #1823160)
[ Łukasz 'sil2100' Zemczak ]
* Add support for the new prepare-image --snap=
bump the snapd dependency to 2.38. (LP: #1815580)
* Print a deprecation warning when using the old --extra-snaps syntax.
* Ignore the new 'grain' field in the pyparted partitiontable structure
during unit-tests, as otherwise it's causing test failures for disco+.
(LP: #1826224)
-- Łukasz 'sil2100' Zemczak <email address hidden> Wed, 24 Apr 2019 16:54:22 +0200