+++ This bug was initially created as a clone of Bug #2193217 +++

Cloning for RHEL8 since this will never get added in RHEL7

Description of problem:

request for better pvmove error message for failed pvmove following system fence

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

lvm2-2.02.187-6.el7_9.5.x86_64

Steps to Reproduce:

Customer reproduced once by trying to do storage migration in a 2 node cluster using pvmove. The cluster nodes got rebooted before completing the pvmove migration, and now are unable to complete or abort the pvmove migration. pvmove --abort is reporting error "Internal error: Wrong params for _copy_poll_operation_id."

Actual results:

Unclear message "Internal error: Wrong params for _copy_poll_operation_id." from pvmove --abort. Also, no message is reported from pvmove and pvmove atomic.

Expected results:

Clear message of what is wrong so next steps can be found

— Additional comment from RHEL Program Management on 2023-05-04 18:04:52 UTC —

RHEL 7 is currently in Maintenance Support 2 Phase.

The support of the product in this phase is limited, and not every bug should be getting fixed and is defined as this:

"During the Maintenance Support Phase for Red Hat Enterprise Linux Version 8 and Maintenance Support 2 Phase for Red Hat Enterprise Linux versions 6 and 7, Red Hat defined Critical and Important impact Security Advisories (RHSAs) and selected (at Red Hat discretion) Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available. Other errata advisories may be delivered as appropriate.

New functionality and new hardware enablement are not planned for availability in the Maintenance Support (RHEL 8) Phase and Maintenance Support 2 (RHEL 6, 7) Phase. Minor releases with updated installation images may be made available in this Phase."

If there is an available workaround, or the impact is minor/cosmetic, we should no longer be addressing this in RHEL 7. If the bug requires a large/invasive/risky fix, this should no longer be addressed in RHEL 7. We can address those types of issues only in future releases which are in a full support phase.

If you're unsure if the fix is suitable for RHEL 7, or if there's a real business reason to make an exception from inclusion criteria as stated above, please follow the Feature process by setting exception?, Such request will be reviewed at the RHEL Blocker and Exception meeting.

Please consider this before working on, or approving this bug.

For Product Owners and CEE: to approve this bug in 7.9.z (if it meets the inclusion criteria) set zstream+ and make sure ITR is set to 7.9.z. After devel and qa acks are provided, bug will be approved for a release, no action is needed.

— Additional comment from RHEL Program Management on 2023-05-04 18:04:52 UTC —

This bug does not have Internal Target Release set. It was set to 7.9.z (zstream) to ensure compliance with the process.

— Additional comment from John Pittman on 2023-05-04 18:19:33 UTC —

— Additional comment from John Pittman on 2023-05-04 18:24:33 UTC —

— Additional comment from John Pittman on 2023-05-04 18:30:05 UTC —

— Additional comment from John Pittman on 2023-05-04 18:31:17 UTC —

— Additional comment from John Pittman on 2023-05-04 18:32:41 UTC —

— Additional comment from John Pittman on 2023-05-04 18:33:50 UTC —

I talked with lvmguy in the #lvm slack channel and he suggested I create this bug to request better logging for this issue. If needed he may have more details on the exact expectation of the error contents.