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.
This issue is not observed on Satellite 6.12.
very likely fixed by https://projects.theforeman.org/issues/35895
do you have production.log captured from when it happens so we could compare it with the upstream issue?
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.
This looks similar to https://projects.theforeman.org/issues/35895
I agree, it is the same bug we solved here https://projects.theforeman.org/issues/35895.
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