Alan Rominger

Hmm, I put up https://github.com/ansible/awx/pull/13422 so that the check would run the sanity tests with devel, and discover the failures you mention. In the steps, it does clearly confirm Ansible...

@thedoubl3j I tried to double-check this locally, so I ran with Ansible devel locally _without_ the `--docker` flag, and it still passed. This appears consistent with the result from that...

I tried this patch, and it successfully addressed the warning, but... ```diff diff --git a/awx_collection/plugins/lookup/schedule_rrule.py b/awx_collection/plugins/lookup/schedule_rrule.py index 5f1d34c0ae..fb9ae9e304 100644 --- a/awx_collection/plugins/lookup/schedule_rrule.py +++ b/awx_collection/plugins/lookup/schedule_rrule.py @@ -82,7 +82,8 @@ RETURN = """...

This got more aggressive to the point of failing the checks, the action was super clear so change was made in https://github.com/ansible/awx/pull/15625 This may require modifying playbooks with that collection...

The EE `verify_ssl` is implemented in ansible-runner https://github.com/ansible/ansible-runner/blob/88130033e6b4791952236a8b1eb6f7ac823649e3/test/integration/containerized/test_container_management.py#L114 However, in openshift, it's not the podman CLI but openshift itself that pulls the image. This may be a fairly fundamental issue...

A workflow's execution can take multiple branches simultaneously, and some nodes could have already traversed their "failure" or "always" connections. The best feature spec I could imagine would be to...

Checks actually look okay here. Baby YOLO 199

Discovered 2 new failures ``` tests.api.rbac.test_job_templates_rbac.Test_Cross_Org_Job_Template_RBAC.test_users_of_project_org[admin] ``` > awxkit.exceptions.BadRequest: Bad Request (400) received - {'detail': "Cannot resolve keyword 'descendents' into field. Choices are: activitystream, children, content_object, content_type, content_type_id, id, implicit_parents,...

Can you link some kind of issue to document the bug that this is fixing? Also, can we add a test for this? For efficient test-writing, I want to say...

I'm collecting a list of remaining problematic settings: ``` tools_awx_1 | Marking setting ORG_ADMINS_CAN_SEE_ALL_USERS read_only tools_awx_1 | Marking setting MANAGE_ORGANIZATION_AUTH read_only tools_awx_1 | Marking setting CSRF_TRUSTED_ORIGINS read_only tools_awx_1 | Marking...