Bug 1896245 - [CBT][RFE] Use the new VIR_ERR_CHECKPOINT_INCONSISTENT error from libvirt to identify invalid checkpoints
Summary: [CBT][RFE] Use the new VIR_ERR_CHECKPOINT_INCONSISTENT error from libvirt to ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage
Version: 4.4.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.4.5
: ---
Assignee: Eyal Shenitzky
QA Contact: Ilan Zuckerman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-10 07:11 UTC by Eyal Shenitzky
Modified: 2021-11-04 19:28 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-18 15:13:01 UTC
oVirt Team: Storage
Embargoed:
pm-rhel: planning_ack?
pm-rhel: devel_ack?
pm-rhel: testing_ack?


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 112773 0 master MERGED backup.py: distinct broken checkpoint error when starting a backup 2021-02-16 10:46:58 UTC
oVirt gerrit 112774 0 master MERGED backup.py: perform checkpoint validation when checkpoint redefine 2021-02-16 10:46:58 UTC
oVirt gerrit 112775 0 master MERGED spec.in: bump libvirt version to 6.6.0-13 2021-02-16 10:46:58 UTC

Description Eyal Shenitzky 2020-11-10 07:11:18 UTC
Description of problem:

In Libvit >= 6.10, a new error is raised in case of trying to do backup related operations
with a broken checkpoint - VIR_ERR_CHECKPOINT_INCONSISTENT.

The engine/VDSM should identify this error and act accordingly in case it is raised.

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

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Shir Fishbain 2021-01-26 11:37:04 UTC
Hi Eyal,
Please provide info on how to verify it correctly.

Comment 2 Eyal Shenitzky 2021-01-26 12:13:41 UTC
(In reply to Shir Fishbain from comment #1)
> Hi Eyal,
> Please provide info on how to verify it correctly.

Can be verified by running the regular tiers in the automation.

Comment 3 Ilan Zuckerman 2021-02-08 07:06:15 UTC
Eyal, in order to verify this, I'd like to know:
- How to raise this ERROR
- How the engine should act when this ERROR is raised

Comment 4 Eyal Shenitzky 2021-02-08 11:56:47 UTC
(In reply to Ilan Zuckerman from comment #3)
> Eyal, in order to verify this, I'd like to know:
> - How to raise this ERROR
> - How the engine should act when this ERROR is raised

In order to verify that bug we can just run the regular tiers.
There is no specific flow that should be checked.

Comment 5 Ilan Zuckerman 2021-02-09 11:49:33 UTC
Moving this on verified based on the tier1 and tier2  (tier3 doesnt exist) Automated test cases of CBT which were executed on latest rhv-4.4.5-4
tier2 was executed locally, tier1 is "RHV-4.4-tier1 #154" and can be found in Polarion.
No regression was spotted, or suspicious behavior. All test cases passed (except for known issues BZ 1914636 and BZ 1849861)

Comment 6 Sandro Bonazzola 2021-03-18 15:13:01 UTC
This bugzilla is included in oVirt 4.4.5 release, published on March 18th 2021.

Since the problem described in this bug report should be resolved in oVirt 4.4.5 release, it has been closed with a resolution of CURRENT RELEASE.

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

Comment 7 Sandro Bonazzola 2021-03-22 12:55:33 UTC
This bugzilla is included in oVirt 4.4.5 release, published on March 18th 2021.

Since the problem described in this bug report should be resolved in oVirt 4.4.5 release, it has been closed with a resolution of CURRENT RELEASE.

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


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