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 2168679 - Clicking on 'Variables' within 'Ansible' in 'Content Hosts' page fails with 'Received status code 500' when 'theforeman.foreman_scap_client' role is assigned to the host
Summary: Clicking on 'Variables' within 'Ansible' in 'Content Hosts' page fails with '...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Ansible - Configuration Management
Version: 6.13.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: 6.13.0
Assignee: nalfassi
QA Contact: addubey
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-09 18:02 UTC by Jayant Bhatia
Modified: 2023-08-03 17:35 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-03 13:25:08 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-15846 0 None None None 2023-02-13 14:32:26 UTC
Red Hat Product Errata RHSA-2023:2097 0 None None None 2023-05-03 13:25:23 UTC

Description Jayant Bhatia 2023-02-09 18:02:28 UTC 
Description of problem:
When 'theforeman.foreman_scap_client' role is assigned to the host, navigating to 'Variables' within 'Ansible' in 'Content Hosts' page   fails with "Received status code 500".


Version-Release number of selected component (if applicable): satellite-6.13.0-4.el8sat.noarch


How reproducible: Always


Steps to Reproduce:

1. Navigate to Satellite WebUI -> Configure -> Ansible Roles -> Import the 'theforeman.foreman_scap_client' role.

2. Register a host with Satellite. Navigate to Satellite WebUI -> Hosts -> Content Hosts -> click on registered host -> Ansible -> Assign roles directly to the host -> Assign 'theforeman.foreman_scap_client' role to the host -> Confirm.

3. Navigate to Satellite WebUI -> Hosts -> Content Hosts -> click on registered host -> Ansible -> Click on 'Variables' (near 'Roles').


Actual results: Below message is displayed on the screen.

       Error!
       Response not successful: Received status code 500


Expected results: Instead of status code 500, variables list should be displayed.


Additional info: Issue is only observed with 'theforeman.foreman_scap_client' ansible role.
Comment 1 Jayant Bhatia 2023-02-09 18:11:58 UTC 
This issue is not observed on Satellite 6.12.
Comment 2 Marek Hulan 2023-02-13 10:46:57 UTC 
very likely fixed by https://projects.theforeman.org/issues/35895
Comment 3 Marek Hulan 2023-02-13 10:47:32 UTC 
do you have production.log captured from when it happens so we could compare it with the upstream issue?
Comment 5 Jayant Bhatia 2023-02-13 12:38:04 UTC 
Below is error trace observed in production.log file:

~~~
[W|app|4f04e3d2] Action failed
2023-02-13T17:58:12 [I|app|4f04e3d2] Backtrace for 'Action failed' error (ArgumentError): wrong number of arguments (given 4, expected 0)
 4f04e3d2 | /usr/share/gems/gems/graphql-1.13.16/lib/graphql/execution/errors.rb:119:in `message'
 4f04e3d2 | /usr/share/gems/gems/graphql-1.13.16/lib/graphql/execution/errors.rb:119:in `rescue in with_error_handling'
 4f04e3d2 | /usr/share/gems/gems/graphql-1.13.16/lib/graphql/execution/errors.rb:106:in `with_error_handling'
~~~

Please refer attachment for complete error trace.
Comment 6 Jayant Bhatia 2023-02-13 12:39:14 UTC 
This looks similar to https://projects.theforeman.org/issues/35895
Comment 7 nalfassi 2023-02-14 15:20:17 UTC 
I agree, it is the same bug we solved here https://projects.theforeman.org/issues/35895.
Comment 12 errata-xmlrpc 2023-05-03 13:25:08 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 (Important: Satellite 6.13 Release), 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-2023:2097
Note You need to log in before you can comment on or make changes to this bug.