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 1464953 - logical volume resize fails with error message
Summary: logical volume resize fails with error message
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: udisks2
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Vojtech Trefny
QA Contact: Desktop QE
URL:
Whiteboard:
: 1462660 (view as bug list)
Depends On:
Blocks: 1459279
TreeView+ depends on / blocked
 
Reported: 2017-06-26 09:47 UTC by Dominik Perpeet
Modified: 2021-09-06 12:33 UTC (History)
6 users (show)

Fixed In Version: udisks2-2.7.3-2.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-10 15:43:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Screenshot of error from tests (102.52 KB, image/png)
2017-06-26 09:47 UTC, Dominik Perpeet
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1477736 0 unspecified CLOSED rebase udisks2 2021-09-06 12:34:21 UTC
Red Hat Product Errata RHBA-2018:0868 0 None None None 2018-04-10 15:44:11 UTC

Internal Links: 1477736

Description Dominik Perpeet 2017-06-26 09:47:59 UTC
Created attachment 1291938 [details]
Screenshot of error from tests

Original problem described in https://bugzilla.redhat.com/show_bug.cgi?id=1462660


Description of problem:
During Cockpit upstream integration testing, a test to resize a logical volume fails unexpectedly. Underlying lvm2 default behavior has changed.

I believe storaged has a fix for this on master already: https://github.com/storaged-project/udisks/commit/527e4d5683703ba2684e3f4e51e1251ff26030f2

First found in https://fedorapeople.org/groups/cockpit/logs/pull-6360-20170615-152828-dd09a8ca-verify-rhel-7-4/log.html

Version-Release number of selected component (if applicable):
Cockpit 142.x

storaged:
Arch        : x86_64
Version     : 2.5.2
Release     : 3.el

How reproducible:
Always

Steps to Reproduce:
Run integration tests for volume resize https://github.com/cockpit-project/cockpit/blob/0177950a4be3abaff3545a92f62e094956b2caa3/test/verify/check-storage-resize#L57

Actual results:
Error message, see screenshot. Trace in issue: https://github.com/cockpit-project/cockpit/issues/6960

Comment 2 Marius Vollmer 2017-06-28 08:29:35 UTC
*** Bug 1462660 has been marked as a duplicate of this bug. ***

Comment 4 Vratislav Podzimek 2017-10-24 12:47:00 UTC
I believe this is resolved in udisks2-2.7.3-2.el7

Comment 10 errata-xmlrpc 2018-04-10 15:43:20 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, 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-2018:0868


Note You need to log in before you can comment on or make changes to this bug.