Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1542292

Summary: Running satellite-clone triggers the playbook run twice
Product: Red Hat Satellite Reporter: sthirugn <sthirugn>
Component: Satellite CloneAssignee: John Mitsch <jomitsch>
Status: CLOSED ERRATA QA Contact: sthirugn <sthirugn>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.3.0Keywords: Regression, Triaged
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-19 17:23: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 sthirugn@redhat.com 2018-02-06 01:02:59 UTC 
Description of problem:
Running satellite-clone triggers the playbook run twice.

I noticed this when one of the ansible tasks failed but it may be very well the case for success scenario also.

Version-Release number of selected component (if applicable):
satellite-clone-1.2.1-1.el7sat.noarch

How reproducible:
Always

Steps to Reproduce:
1.Run satellite-clone and make sure that one of the ansible tasks in the playbook fails

Actual results:
Notice that the playbook finishes and gets retriggered the second time.  The run completes after two attempts.

Expected results:
satellite-clone just runs the playbook once.

Additional info:
Comment 3 sthirugn@redhat.com 2018-02-09 20:37:48 UTC 
Verified in satellite-clone-1.2.2-1.el7sat.noarch.

Now the playbook run is triggered just once by the `satellite-clone` command.
Comment 6 errata-xmlrpc 2018-02-19 17:23:44 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHBA-2018:0330