Bug 1505724

Summary: unattended cleanup fails
Product: [oVirt] ovirt-engine Reporter: Yedidyah Bar David <didi>
Component: Setup.CoreAssignee: Yedidyah Bar David <didi>
Status: CLOSED CURRENTRELEASE QA Contact: Lucie Leistnerova <lleistne>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: bugs, lleistne
Target Milestone: ovirt-4.2.0Flags: rule-engine: ovirt-4.2+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
engine-cleanup now does not fail when using an answer file generated by an interactive invocation of it.
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-20 10:52:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Yedidyah Bar David 2017-10-24 07:55:03 UTC
Description of problem:

Running engine-cleanup with an answer file generated by an interactive run fails with:

[ ERROR ] Failed to execute stage 'Initializing': File contains parsing errors: /var/lib/ovirt-engine/setup/answers/20171024101708-cleanup.conf
                [line 12]: 'ovirt-engine-websocket-proxy\n'

The answer file contains:

OVESETUP_REMOVE/removeOptions=multi-str:ovirt-imageio-proxy
ovirt-engine-websocket-proxy

(in two lines)

Need to split with commas or something like that.

Comment 1 Yedidyah Bar David 2017-11-27 15:02:45 UTC
To clarify, the flow of this bug is something like:

1. engine-setup
2. engine-backup --mode=backup --file=f1 --log=l1
3. engine-cleanup, generates anser file ans1
4. engine-backup --mode=restore --file=f1 --log=r1 --no-restore-permissions
5. engine-cleanup --config-append=ans1

Comment 2 Lucie Leistnerova 2017-12-11 09:50:05 UTC
no error in engine-cleanup with answer file

verified in ovirt-engine-setup-4.2.0-0.6.el7.noarch

Comment 3 Sandro Bonazzola 2017-12-20 10:52:30 UTC
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

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