Ansible配置EC2实例时区时收到master退出状态错误求助

Let's break down your issue and walk through actionable fixes step by step. First, let's recap the details you shared:

Your Ansible Task #

- name: Set Time Zone variables
  copy:
    content='Etc/UTC'
    dest=/etc/timezone
    owner=root
    group=root
    mode=0644
    backup=yes

Execution Command #

ansible-playbook nectar.yml --extra-vars "ansible_python_interpreter=/usr/local/bin/python env=DEVELOPMENT" -vvvv

Truncated ansible.cfg #

[defaults]
inventory = hosts
[ssh_connection]
ssh_args = -o Cont...

The Error: Received exit status from master #

This error usually traces back to SSH connectivity issues between your control node and the target EC2 instance, or syntax/configuration gaps in your Ansible setup. Here are the most likely fixes:

1. Fix the Truncated ssh_args Configuration

Your ssh_args line is cut off (-o Cont...), which is almost certainly breaking SSH connections. The ssh_connection section needs complete, valid SSH options. A standard, working configuration might look like this:

[ssh_connection]
ssh_args = -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no

Replace the truncated line with full, valid arguments—malformed or incomplete SSH settings will prevent Ansible from establishing a stable connection to your EC2 instance.

2. Verify the Python Interpreter Path

You’re specifying /usr/local/bin/python via ansible_python_interpreter, but you need to confirm this path actually exists on your target EC2 instance. Many modern Linux distros (like Amazon Linux 2 or Ubuntu 20.04+) default to Python 3, with the system Python located at /usr/bin/python3 instead.

Test if the path is valid by running a simple ping module against your target host:

ansible <your_host_or_group> -m ping --extra-vars "ansible_python_interpreter=/usr/local/bin/python" -vvvv

If this fails, adjust the interpreter path to match what’s available on the instance (e.g., /usr/bin/python3).

3. Correct the copy Module Syntax

While Ansible allows key=value syntax, YAML’s key: value format is more reliable and less prone to parsing errors. Your task has a few syntax quirks that could be causing issues. Rewrite it to use proper YAML formatting:

- name: Set Time Zone variables
  copy:
    content: "Etc/UTC"
    dest: /etc/timezone
    owner: root
    group: root
    mode: '0644'  # Quoting prevents YAML from interpreting 0644 as an octal number
    backup: yes

This ensures Ansible parses the module arguments correctly without unexpected failures.

Additional Debugging Steps #

• Double-check your hosts inventory file to confirm the EC2 instance’s IP/DNS, SSH user, and other connection details are accurate.
• Verify the target EC2 instance’s security group allows inbound SSH (port 22) from your control node’s IP.
• Dig into the -vvvv output for more detailed error logs—often the full trace will show exactly where the SSH connection or module execution is failing.

内容的提问来源于stack exchange，提问作者reayn3