Bug 1282397

Summary: [Fedora Only] engine-backup fails with: tar: '--same-order' cannot be used with '-c'
Product: [oVirt] ovirt-engine Reporter: christian.grundmann
Component: Backup-Restore.EngineAssignee: Yedidyah Bar David <didi>
Status: CLOSED CURRENTRELEASE QA Contact: Gonza <grafuls>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.6.0CC: bmcclain, bugs, sbonazzo
Target Milestone: ovirt-3.6.1Keywords: Regression, ZStream
Target Release: 3.6.1Flags: rule-engine: ovirt-3.6.z+
rule-engine: blocker+
bmcclain: planning_ack+
sbonazzo: devel_ack+
pstehlik: testing_ack+
Hardware: All   
OS: Linux   
Whiteboard: integration
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-16 12:17:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description christian.grundmann 2015-11-16 10:09:28 UTC
Description of problem:
on FC22 engine-backup fails with 
tar: '--same-order' cannot be used with '-c'

Version-Release number of selected component (if applicable):
3.6.0.3-1.fc22


Steps to Reproduce:
1. engine-backup --mode=backup --scope=all --file backup
2. Fails with error
3.

Additional info:
The Patch from https://gerrit.ovirt.org/#/c/48596/ works for me

Comment 1 Red Hat Bugzilla Rules Engine 2015-11-16 10:42:36 UTC
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 2 Gonza 2015-11-25 15:52:49 UTC
Verified with:
ovirt-engine-3.6.2-0.0.master.20151124181807.git6d4897e.fc22.noarch

# engine-backup --mode=backup --scope=all --file=backup --log=bkp.log
Backing up:
Notifying engine
- Files
- Engine database 'engine'
Packing into file 'backup'
Notifying engine
Done.

Comment 3 Sandro Bonazzola 2015-12-16 12:17:44 UTC
According to verification status and target milestone this issue should be fixed in oVirt 3.6.1. Closing current release.