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 1383258

Summary: hammer repository info should show the mirror-on-sync setting
Product: Red Hat Satellite Reporter: Peter Ondrejka <pondrejk>
Component: Hammer - ContentAssignee: Brad Buckingham <bbuckingham>
Status: CLOSED ERRATA QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2.0CC: bbuckingham, dhlavacd, jcallaha, oshtaier, tstrachota
Target Milestone: UnspecifiedKeywords: Triaged
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-21 16:31:43 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 Peter Ondrejka 2016-10-10 10:04:22 UTC 
When creating a repository in cli you can set the mirror-on-sync option:

hammer repository create --mirror-on-sync=false ...

However, the value of mirror-on-sync is not displayed in the output of `hammer repository info`. You have to view the repository in UI to find this information.
Comment 2 Brad Buckingham 2016-10-19 20:44:45 UTC 
Created redmine issue http://projects.theforeman.org/issues/17031 from this bug
Comment 3 Brad Buckingham 2016-10-19 20:50:23 UTC 
Upstream hammer-cli-katello PR: https://github.com/Katello/hammer-cli-katello/pull/460
Comment 4 Bryan Kearney 2016-10-20 20:19:20 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17031 has been resolved.
Comment 5 Oleksandr Shtaier 2017-07-17 10:14:17 UTC 
Verified on latest 6.3 build:

hammer -v -u admin -p changeme  repository info --id="5"
ID:                 5
Name:               cYShngDpxiLmXAm
Label:              cYShngDpxiLmXAm
Organization:       nuDWvn
Red Hat Repository: no
Content Type:       yum
Mirror on Sync:     no
URL:                http://inecas.fedorapeople.org/fakerepos/zoo3/
Publish Via HTTP:   yes
Published At:       http://server_name/pulp/repos/nuDWvn/Library/custom/sUhzJcONSQLnrwPQWNkE/cYShngDpxiLmXAm/
Relative Path:      nuDWvn/Library/custom/sUhzJcONSQLnrwPQWNkE/cYShngDpxiLmXAm
Download Policy:    on_demand
Product:            
    ID:   3
    Name: cgBuUDivDl
GPG Key:            

Sync:               
    Status: Not Synced
Created:            2017/07/17 10:00:27
Updated:            2017/07/17 10:00:28
Content Counts:     
    Packages:       0
    Package Groups: 0
    Errata:         0
...
Comment 6 Oleksandr Shtaier 2017-07-18 12:39:34 UTC 
Re-verified by automation
Comment 7 Bryan Kearney 2018-02-21 16:31:43 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/RHSA-2018:0336