The Automation Auth Key may not be unset when processes exist

Hello Team,
We are trying to automate Replica set installation/ configuration through Ansible using OpsManager public API’s. We have done automation agent installation in the respective servers and able to see those servers in project UI. Now we tried replica set initialization using the Ansible script.

Initiate automation.yaml:-

- name: Initiate Automation
  hosts: om_hosts[0]
  gather_facts: yes
    project_projects: "{{ lookup('file', '/home/ec2-user/commercetools-iac-staging-env/ansible/project_projects.yaml') }}"
    org_private_key: "{{ lookup('file', '/home/ec2-user/commercetools-iac-staging-env/ansible/org_private_key.yaml') }}"
    org_public_key: "{{ lookup('file', '/home/ec2-user/commercetools-iac-staging-env/ansible/org_public_key.yaml') }}"
    - automation


- name: Ignore warnings raised for files with unknown extensions while loading (2.7)
    dir: vars
    ignore_unknown_extensions: True
    extensions: ['yaml', 'yml', 'json']

- name: "Set OM Base URL"
    om_base_url: "{{ om_url.0 }}/api/public/v1.0"

###### Run the below projects one at a time by commenting and uncommenting individual blocks below

- name: "Initiate Projects Automation"
    url: "{{ om_base_url }}/groups/{{ project_projects }}/automationConfig?pretty=true"
    validate_certs: no
    method: PUT
      Content-Type: "application/json"
    body: "{{ lookup('file', 'vars/projects-rs.json') }}"
    body_format: json
    status_code: 200
    # return_content: yes
    user: "{{ org_public_key }}"
    password: "{{ org_private_key }}"

projects-rs.json file attached.

The error is

TASK [automation : Initiate Projects Automation] ************************************************************************************
[WARNING]: Module did not set no_log for password
fatal: []: FAILED! => {“changed”: false, “connection”: “close”, “content_length”: “187”, “content_type”: “application/json”, “date”: “Mon, 27 Mar 2023 12:48:22 GMT”, “elapsed”: 0, “json”: {“detail”: “Invalid config: The Automation Auth Key may not be unset when processes exist.”, “error”: 400, “errorCode”: null, “parameters”: null, “reason”: “Bad Request”}, “msg”: “Status code was 400 and not [200]: HTTP Error 400: Bad Request”, “redirected”: false, “referrer_policy”: “strict-origin-when-cross-origin”, “status”: 400, “strict_transport_security”: “max-age=0; includeSubdomains;”, “url”: “**********/automationConfig?pretty=true”, “x_content_type_options”: “nosniff”, “x_frame_options”: “DENY”, “x_mongodb_service_version”: “gitHash=f6da67b6680af73325f5a4198d48f673204d72a8; versionString=”, “x_permitted_cross_domain_policies”: “none”}

Can you please help us here what’s the issue? if you can . It’s really great if so

Thanks & regards

Hello @venkat_annangi ,

Welcome to The MongoDB Community Forums! :wave:

Please correct me if I am wrong, I suppose that you are working with MongoDB Ops Manager. The issue seems to be with your configuration/environment.

I would recommend you open a support case at MongoDB Support Portal as they have the required expertise and could help you with Root Cause Analysis and provide best solutions as per your use-case.