RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1953826 - [udisks2] set wrong part_type in test_dos_type
Summary: [udisks2] set wrong part_type in test_dos_type
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: udisks2
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: beta
: ---
Assignee: Tomáš Bžatek
QA Contact: guazhang@redhat.com
URL:
Whiteboard:
Depends On: 2010363
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-27 03:53 UTC by guazhang@redhat.com
Modified: 2022-06-07 03:17 UTC (History)
0 users

Fixed In Version: udisks2-2.9.4-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-17 12:52:43 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2022:2413 0 None None None 2022-05-17 12:52:54 UTC

Description guazhang@redhat.com 2021-04-27 03:53:40 UTC 
Description of problem:
udisks2 regression failed because the test_60_partitioning.py failed 

Version-Release number of selected component (if applicable):

udisks2-2.9.2-3.el9.x86_64
RHEL-9.0.0-20210425.3

How reproducible:


Steps to Reproduce:
1. python3 src/tests/dbus-tests/run_tests.py -s test_60_partitioning.UdisksPartitionTest.test_dos_type

python3 src/tests/dbus-tests/run_tests.py -s test_60_partitioning.UdisksPartitionTest.test_gpt_type


Actual results:
hit errors 

Expected results:
no errors 

Additional info:


======================================================================
FAIL: test_dos_type (test_60_partitioning.UdisksPartitionTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/root/rpmbuild/BUILD/udisks-2.9.2/src/tests/dbus-tests/test_60_partitioning.py", line 613, in test_dos_type
    dbus_type.assertEqual(part_type)
  File "/root/rpmbuild/BUILD/udisks-2.9.2/src/tests/dbus-tests/udiskstestcase.py", line 188, in assertEqual
    raise AssertionError('%s != %s' % (self._value, value))
AssertionError: 0x83 != 0x8e

======================================================================
FAIL: test_gpt_type (test_60_partitioning.UdisksPartitionTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/root/rpmbuild/BUILD/udisks-2.9.2/src/tests/dbus-tests/test_60_partitioning.py", line 579, in test_gpt_type
    dbus_type.assertEqual(home_guid)
  File "/root/rpmbuild/BUILD/udisks-2.9.2/src/tests/dbus-tests/udiskstestcase.py", line 188, in assertEqual
    raise AssertionError('%s != %s' % (self._value, value))
AssertionError: 0fc63daf-8483-4772-8e79-3d69d8477de4 != 933ac7e1-2eb4-4f13-b844-0e14e2aef915

----------------------------------------------------------------------
Ran 194 tests in 314.985s

FAILED (failures=2, skipped=73)
All configuration cleared

# blkid /dev/sdb1 -p -o value -s PART_ENTRY_TYPE
0x83

[root@storageqe-69 api-examples]# fdisk  /dev/sdb  -l
Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xaa2d3be2

Device     Boot Start        End    Sectors  Size Id Type
/dev/sdb1        2048 3907029167 3907027120  1.8T 83 Linux


dbus_type = self.get_property(part, '.Partition', 'Type')
print("dbus_type",dbus_type.value)
# 0x83



dosfstools-4.2-2.el9.x86_64
Comment 1 Tomáš Bžatek 2021-04-27 12:07:50 UTC 
This might be https://github.com/storaged-project/udisks/commit/d4084472f59c1cf7082c913082cace4a96a1d042 although that one was done for libfdisk-based libblockdev part plugin (RHEL 10+)
Comment 3 Tomáš Bžatek 2021-10-05 14:15:12 UTC 
The change mentioned above is part of the udisks-2.9.4 release, planned for rebase in bug 2010363.
Comment 4 Tomáš Bžatek 2021-10-26 13:19:44 UTC 
Can you retest this with the udisks2-2.9.4-1.el9 build please?
Comment 5 guazhang@redhat.com 2021-10-28 03:09:40 UTC 
Hi,

Don't reproduce the bug with udisks2-2.9.4-1.el9,

dosfstools-4.2-3.el9.x86_64
Comment 6 Tomáš Bžatek 2021-10-29 15:06:43 UTC 
Thanks, I was not sure if it was just a random test failure we've been seeing occasionally or not.

OK then, let's include this in an errata. Please set Verified:Tested on this on as well.
Comment 10 errata-xmlrpc 2022-05-17 12:52:43 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (new packages: udisks2), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:2413
Note You need to log in before you can comment on or make changes to this bug.