Bug 1812525 - [documentation] Incremental Backup - TBD 'full' is not supported, although specified in the feature page
Summary: [documentation] Incremental Backup - TBD 'full' is not supported, although sp...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage
Version: 4.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Tal Nisan
QA Contact: Shir Fishbain
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-11 14:02 UTC by Ilan Zuckerman
Modified: 2023-08-03 07:21 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-03 07:21:22 UTC
oVirt Team: Docs
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-37821 0 None None None 2022-09-06 12:21:09 UTC

Description Ilan Zuckerman 2020-03-11 14:02:38 UTC 
Description of problem:

This is documentation bug for incremental backup feature.

Reading feature page for incremental backup:
https://www.ovirt.org/develop/release-management/features/storage/incremental-backup.html

Under "Enabling backup for VM disk" section, the following line is written:
"Specify ‘backup’ property on disk entity: ‘incremental’/’none’ (TBD: ‘full’)"

But DEV claims that 'full' property is not supported and will not be.

This content need to be fixed in order to better reflect the feature.
Comment 1 Casper (RHV QE bot) 2022-09-06 12:31:57 UTC 
This bug has low overall severity and is not going to be further verified by QE. If you believe special care is required, feel free to properly align relevant severity, flags and keywords to raise PM_Score or use one of the Bumps ('PrioBumpField', 'PrioBumpGSS', 'PrioBumpPM', 'PrioBumpQA') in Keywords to raise it's PM_Score above verification threashold (1000).
Comment 2 Sandro Bonazzola 2023-08-03 07:21:22 UTC 
No updates in the last 6 years, closing as won't fix.
If still relevant please open an issue on https://github.com/oVirt/ovirt-site/issues
Note You need to log in before you can comment on or make changes to this bug.