Bug 1082055

Summary: spacewalk-clone-by-date: error: --channels option does not take a value
Product: [Community] Spacewalk Reporter: Pavel Studeník <pstudeni>
Component: ServerAssignee: Michael Mráka <mmraka>
Status: CLOSED DUPLICATE QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 2.2CC: dyordano
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-04-08 12:10:02 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:
Bug Depends On:    
Bug Blocks: 1484117    

Description Pavel Studeník 2014-03-28 14:58:49 UTC
Description of problem:
spacewalk-clone-by-date doesn't accept format of arguments with char '='.

Now, it is accepted only following format "spacewalk-clone-by-date --channel channel1 channel2". 

It's regression, satellite 5 works correctly. 

Version-Release number of selected component (if applicable):
spacewalk-utils-2.2.9-1.el5


How reproducible:
always

Steps to Reproduce:
1. spacewalk-clone-by-date --channel=channel1 channel2

Actual results:
>> spacewalk-clone-by-date --channel=channel1 channel2
usage: spacewalk-clone-by-date [options]

spacewalk-clone-by-date: error: --channels option does not take a value


Expected results:
I can use format with and without '='.

spacewalk-clone-by-date --channel=channel1 channel2
spacewalk-clone-by-date --channel channel1 channel2

Comment 1 Dimitar Yordanov 2014-04-08 12:10:02 UTC
This issue is fixed upstream by commit:

commit 5b8eb30d77b7e8a61e031556da24bec8a833e718
Author: Stephen Herr <sherr>
Date:   Thu Apr 3 14:23:35 2014 -0400

    1073543 - fix problem where --channels=src_label dst_label threw an error

See:BZ 1073543, "Comment 3".

*** This bug has been marked as a duplicate of bug 1073543 ***

Comment 2 Eric Herget 2017-09-28 18:08:21 UTC
This BZ closed some time during 2.5, 2.6 or 2.7.  Adding to 2.7 tracking bug.