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.

I'm creating sync plans and repositories assignments among other things automatically via hammer tool.

e.g.:

$ hammer sync-plan create --interval=daily --name='Daily sync' --organization=$ORG

When I want to assign the sync plan to a product I need to list all sync plans, get an id and then assign the sync plan to product via the id because referencing of sync plan by name fails:

$ hammer product set-sync-plan --sync-plan='Daily sync' --organization=$ORG --name='Red Hat Enterprise Linux Server'
Could not assign synchronization plan.:
  Error: option '--sync_plan_id' is required

The solution is to add --label option that will assign a tag to a sync plan or repository so that there is no ambiguity in sync plan/repo specification.

Needing to manually parse IDs is just a design flaw as there is no reason to even have --sync-plan, etc. options when they are ambiguous.

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Created redmine issue http://projects.theforeman.org/issues/10181 from this bug

Upstream bug component is Content Management

Upstream bug component is Hammer - Content

Upstream bug component is Content Management

Upstream bug component is Hammer - Content

Upstream bug component is Content Management