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 1718856 - "hammer ansible roles import" complains about ISE instead of providing hint for missing proxy_id
Summary: "hammer ansible roles import" complains about ISE instead of providing hint f...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Ansible - Configuration Management
Version: 6.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.6.0
Assignee: Ondřej Pražák
QA Contact: Lukas Pramuk
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-10 12:27 UTC by Lukas Pramuk
Modified: 2019-10-22 19:52 UTC (History)
2 users (show)

Fixed In Version: tfm-rubygem-foreman_ansible-3.0.3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-22 19:52:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 27033 0 Normal Closed "hammer ansible roles import" complains about ISE instead of providing hint for missing proxy_id 2020-10-14 22:33:13 UTC

Description Lukas Pramuk 2019-06-10 12:27:42 UTC
Description of problem:
"hammer ansible roles import" complains about ISE instead of providing hint for missing proxy_id
This can be very confusing for users. Other 

Version-Release number of selected component (if applicable):
@satellite-6.6.0-5.beta.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_ansible-0.3.0-2.el7sat.noarch
ansible-2.8.0-1.el7ae.noarch

How reproducible:
deterministic

Steps to Reproduce:
1. Run "hammer ansible roles import" without --proxy-id option

# hammer ansible roles import
Could not import roles:
  Internal Server Error: the server was unable to finish the request. This may be caused by unavailability of some required service, incorrect API call or a server-side bug. There may be more information in the server's logs.

# hammer ansible roles fetch
Could not fetch roles:
  Missing arguments for 'proxy_id'

>>> fetch subcommand shows us expected result

Actual results:
misleading message to the user

Expected results:
correct message to the user 
Missing arguments for 'proxy_id'

Comment 3 Ondřej Pražák 2019-06-12 14:07:51 UTC
Created redmine issue https://projects.theforeman.org/issues/27033 from this bug

Comment 4 Bryan Kearney 2019-06-13 12:07:43 UTC
Upstream bug assigned to oprazak

Comment 5 Bryan Kearney 2019-06-13 12:07:44 UTC
Upstream bug assigned to oprazak

Comment 7 Lukas Pramuk 2019-07-17 09:14:29 UTC
VERIFIED.

@Satellite-6.6.0 Snap9
tfm-rubygem-foreman_ansible-3.0.3-3.el7sat.noarch

by following command:

# hammer ansible roles import
Could not import roles:
  Missing arguments for 'proxy_id'

>>> correctly hinting user to provide --proxy-id param

Comment 8 Bryan Kearney 2019-10-22 19:52:27 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-2019:3172


Note You need to log in before you can comment on or make changes to this bug.