支持控制台（Console）开发人员开始试用联系人

此内容没有您所选择的语言版本。

Appendix A. Automation execution environments precedence

Identify and control the exact automation execution environment applied to your jobs by tracing the precedence hierarchy, ensuring you can troubleshoot environment mismatches or configure accurate defaults across your templates, projects, and organizations.

Project updates always use the control plane automation execution environments by default.

However, jobs use the first available automation execution environments as follows:

  1. The execution_environment defined on the template (job template or inventory source) that created the job.
  2. The default_environment defined on the project that the job uses.
  3. The default_environment defined on the organization of the job.
  4. The default_environment defined on the organization of the inventory the job uses.
  5. The current DEFAULT_EXECUTION_ENVIRONMENT setting (configurable at api/v2/settings/system/)
  6. Any image from the GLOBAL_JOB_EXECUTION_ENVIRONMENTS setting.
  7. Any other global execution environment.
Note
  • Where an execution environment is not available, the Default execution environment can be used. However, you must select this, as the system does not automatically provide a default environment.
  • If more than one execution environment fits a criteria (applies for 6 and 7), the most recently created one is used.

A.1. If no default execution environment is provided
复制链接

Troubleshoot why a job bypasses the Default Execution Environment by verifying overrides in template, project, organization, or global settings, and checking environment array orders in configuration files and the database.

When the "Default Execution Environment" is not used for a job, double-check the following:

Procedure

  1. Check if a different execution environment EE has been defined for the template, project, or organization of the job.

  2. Check if the GLOBAL_JOB_EXECUTION_ENVIRONMENTS setting is configured with any execution environments, as these take precedence over the Default execution environment.

    Note

    This setting is not configured by default.

  3. Check the order of the GLOBAL_JOB_EXECUTION_ENVIRONMENTS in /etc/tower/conf.d/execution_environments.py. "Default Execution Environment" should be the first item in the array.
  4. Check the order of the execution environment defined in the database.

  5. Run the following command as root on the controller node to output the main_executionenvironment table:

    # echo "select id, name, created from main_executionenvironment where organization_id is null and managed = False order by created desc;" | awx-manage dbshell

To ensure that the "Default Execution Environment" is used regardless of the `GLOBAL_JOB_EXECUTION_ENVIRONMENTS`mm setting and database order, set the "Global default execution environment" in Settings Automation Execution System to "Default Execution Environment".

Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

關於紅帽

我们提供强化的解决方案，使企业能够更轻松地跨平台和环境（从核心数据中心到网络边缘）工作。

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情，请参阅红帽博客.

关于红帽文档

通过我们的产品和服务，以及可以信赖的内容，帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

Legal Notice

Theme

© 2026 Red Hat返回顶部