Bug 2124051
| Summary: | Ansible-type REX jobs are still delegated by satellite 6.12 to be executed via an external Capsule 6.12 even if the ansible feature is not enabled on the same | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Sayan Das <saydas> |
| Component: | Remote Execution | Assignee: | Adam Ruzicka <aruzicka> |
| Status: | CLOSED ERRATA | QA Contact: | Peter Ondrejka <pondrejk> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.12.0 | CC: | aruzicka, pcreech |
| Target Milestone: | 6.12.0 | Keywords: | Regression, Triaged |
| Target Release: | Unused | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | rubygem-foreman_remote_execution-7.2.2 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-11-16 13:35:39 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Sayan Das
2022-09-04 09:40:38 UTC
I see a 6.11 bug was filed i.e. https://bugzilla.redhat.com/show_bug.cgi?id=2111701 but The request there is different and the root cause is unidentified. My bug has a clear root cause and is more of an RFE to improve the error handling. > *The job cannot be executed as the required feature is missing on the target capsule capsule.example.com" We cannot really say that, because we do not know that. From where I'm standing it looks like we have (at least) 3 different BZs about the same issue - this one, https://bugzilla.redhat.com/show_bug.cgi?id=2111701 and https://bugzilla.redhat.com/show_bug.cgi?id=2106700 . What all three have in common is that a subset of a job gets routed to a capsule, which for some reason cannot process it an immediately gives back 404. Previously, we failed to propagate this error properly so Satellite thought the parts of the job were still running on the capsules and when you looked at the live output, you got a 404 again, but it did not kill the job. Now that https://bugzilla.redhat.com/show_bug.cgi?id=2106700 is fixed, the parts of the job for which capsule gives 404 fail straight away. If the ask here is just to improve the messaging, then I'd say the fix done in BZ #2106700 is as good as it can be. However, if the "Prefer registered through Capsule for remote execution" setting makes the job to be routed to that capsule *always*, even if it doesn't have the necessary feature then that is a thing we should address. Is there a setup available where I could take a look at this? Sure. Let me share the details in the next private comment. Verified on Satellite 6.12 snap 13. Using the scenario described in the problem description, the ansible rex job is now executed through internal capsule that has the Ansible feature on, even though the host is registered to the other caps and the "Prefer registered through Capsule..." setting is on. 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.12 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:8506 |