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.

Description of problem:

The repository create api docs (and cli options) include an ignore_global_proxy option, but the update does not.


Version-Release number of selected component (if applicable):
6.3.0 beta

How reproducible:
always

Steps to Reproduce:
1. Example apipie doc for repository update, or examine "hammer repository update --help"

Actual results:
Expect to see ignore_global_proxy (--ignore-global-proxy for hammer)

Expected results:
do not see these.

Connecting redmine issue http://projects.theforeman.org/issues/22561 from this bug

This bug was created during verification of bug 1132980.

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/22561 has been resolved.

VERIFIED
on sat6.4.0-12

the options is now documented in both - POST and PUT sections

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:2927