Description of problem: Part of REX job fails if multiple capsules are used for the job Version-Release number of selected component (if applicable): tfm-rubygem-foreman-tasks-5.2.1-1.el7sat.noarch How reproducible: always Steps to Reproduce: 1. Have at least 2 capsules, both configured for REX 2. Run a job on at least 2 hosts, ensure both capsules are used Actual results: On part of the hosts the job fails, on part it succeeds The hosts the fail will have something like the following in their output 1:Initialization error: RestClient::NotFound - 404 Not Found 2:Initialization error: RestClient::NotFound - 404 Not Found 3:Initialization error: RestClient::NotFound - 404 Not Found 4:Initialization error: RestClient::NotFound - 404 Not FoundError loading data from Capsule: NoMethodError - undefined method `code' for "404 Not Found":String 5:Did you mean? encode Expected results: It succeeds on all hosts.
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/34447 has been resolved.
Verified on Satellite 6.11 snap 16, the issue no longer occurs with multiple rex capsules
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 (Moderate: Satellite 6.11 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-2022:5498