Bug 1351622 - [RFE] - Remove reports code from engine-backup
Summary: [RFE] - Remove reports code from engine-backup
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Backup-Restore.Engine
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
: ---
Assignee: Yedidyah Bar David
QA Contact: Lukas Svaty
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-30 12:48 UTC by movciari
Modified: 2019-04-24 20:57 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-12 11:09:53 UTC
oVirt Team: Integration
Embargoed:
ylavi: ovirt-future?
pstehlik: testing_plan_complete-
ylavi: planning_ack?
ylavi: devel_ack?
ylavi: testing_ack?


Attachments (Terms of Use)

Description movciari 2016-06-30 12:48:54 UTC
Description of problem:
engine-backup --help still shows options related for reports on 4.0, where reports are no longer available

Version-Release number of selected component (if applicable):
ovirt-engine-tools-backup-4.0.0.6-0.1.el7ev.noarch

How reproducible:
always

Steps to Reproduce:
1. call engine-backup --help
2.
3.

Actual results:
it shows obsolete options related to reports

Expected results:
it should only show relevant options

Additional info:

Comment 1 Yedidyah Bar David 2016-06-30 13:41:41 UTC
Please consider bug 1340810. A 4.0 engine-backup can restore a 3.6 backup that does include reports. Should we not provide relevant options? If we do, should they not appear in --help?

Also, in principle it's possible to restore such a backup, and set up a remote 3.6 reports that uses the restored database.

I'd personally close notabug.

Comment 3 Yedidyah Bar David 2016-07-10 10:18:20 UTC
Following a discussion last week: Perhaps we do want to do something for *backup*. That is, if you have a system upgraded or migrated from 3.6 with reports, and run engine-backup --mode=backup, do something:
1. Do not backup reports
2. Warn
3. Something else?

Comment 4 Yaniv Lavi 2016-07-10 11:23:12 UTC
(In reply to Yedidyah Bar David from comment #3)
> Following a discussion last week: Perhaps we do want to do something for
> *backup*. That is, if you have a system upgraded or migrated from 3.6 with
> reports, and run engine-backup --mode=backup, do something:
> 1. Do not backup reports
> 2. Warn
> 3. Something else?

Not really, the foot print of reports is too small to make a difference. Also someone may realize after upgrade he wants report and revert to backup.

I'm moving this back since I think we should not list things in help that are not usable.

Comment 5 Yedidyah Bar David 2016-07-10 11:35:48 UTC
(In reply to Yaniv Dary from comment #4)
> Not really, the foot print of reports is too small to make a difference.

Fine with me.

> Also someone may realize after upgrade he wants report and revert to backup.

Irrelevant. Someone doing that will revert to 3.6, with the 3.6 code.

> 
> I'm moving this back since I think we should not list things in help that
> are not usable.

Sorry, no idea what I should do then. Everything in '--help' is usable, if you consider a system upgraded/migrated/restored from a 3.6 backup. You can continue backing up reports, restoring that backup, setup a remote 3.6 reports to use the reports db, etc.

Comment 6 Yaniv Lavi 2016-07-11 11:52:32 UTC
Understood. Moving out with different action item.

Comment 7 Yedidyah Bar David 2016-07-11 12:38:23 UTC
Restored summary line. We already have bug 1340810 for the code.

Comment 8 Yaniv Lavi 2016-07-11 12:45:07 UTC
(In reply to Yedidyah Bar David from comment #7)
> Restored summary line. We already have bug 1340810 for the code.

1340810 drops the restore, it doesn't remove the code.

Comment 9 Yedidyah Bar David 2016-07-11 13:41:44 UTC
(In reply to Yaniv Dary from comment #8)
> 1340810 drops the restore, it doesn't remove the code.

OK. Now pushed a patch for current bug to drop the Reports help text, and a patch to bug 1340810 to disable Reports backup and restore, with a TODO comment to drop the code in 4.1. I think that's enough for now - please move current bug back to 4.0.something as you see fit. Thanks.

Comment 10 Yaniv Lavi 2016-07-14 08:30:52 UTC
Since the tooling is there for 4.0 and it works, I think we should keep it and remove all the code together in 4.1.

Comment 11 Yaniv Lavi 2018-06-12 11:09:53 UTC
Closing old RFEs, please reopen if still needed.
Patches are always welcome.


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