Dell NativeEdge: Litmus Edge Deployment Fails at Install_init_config

Summary: This article explains why a Litmus Edge deployment fails at the step Install_init_config and how to resolve the issue.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.

Symptoms

The following message is observed during the install_init_config step when the blueprint is attempting to change the password of the Litmus Edge virtual machine.

The password change occurs as a sub task of install_init_config

2025-06-20T11:04:09.883Z		nativeedge_event	Task started 'ne_ansible.tasks.run'

(shortened)

2025-06-20T11:04:48.275Z	debug	nativeedge_log	playbook_args: 
 playbook_path : /opt/manager/resources/deployments/default_tenant/a770b122-f1d3-4557-8a7d-f13ed7968adc/init_config_y9iubj/tmp8sd5zvi5/playbook/change_password.yml
module_path : /opt/manager/resources/deployments/default_tenant/a770b122-f1d3-4557-8a7d-f13ed7968adc/tmpzn1y01ae
sources : /opt/manager/resources/deployments/default_tenant/a770b122-f1d3-4557-8a7d-f13ed7968adc/init_config_y9iubj/tmp8sd5zvi5/playbook/hosts
verbosity : 2
additional_args : 
ansible_external_venv : /opt/ansible
log_stdout : False
run_data : 
  ADMIN_PASSWD : *******
  DEFAULT_PASSWD : litmusedge
  IP : hzp-eoproxy-svc-0-tcp-service.hzp.svc.cluster.local:9004
  VALIDATE_CERTS : False
sensitive_keys : ['ADMIN_PASSWD', 'ansible_password', 'ansible_user', 'ansible_ssh_private_key_file', 'AUTHORIZATION', 'TOKEN', 'SECRET', 'PASSWORD', 'AZURE_SECRET', 'AZURE_PASSWORD', 'AWS_ACCESS_KEY_ID', 'AWS_SECRET_ACCESS_KEY']
store_facts : False
tags : []
environment_variables : 
  REST_HOST : fusion-entrypoint
  REST_PORT : 80
  LOCAL_REST_CERT_FILE : /etc/nativeedge/ssl/cloudify_internal_ca_cert.pem
  CTX_NODE_INSTANCE_ID : init_config_y9iubj
  ANSIBLE_CONFIG : /opt/manager/resources/deployments/default_tenant/a770b122-f1d3-4557-8a7d-f13ed7968adc/init_config_y9iubj/tmp8sd5zvi5/ansible.cfg


2025-06-20T11:04:48.324Z	warning	nativeedge_log	The parameter log_stdout is set to False, you will not see logs for this execution from Ansible.
2025-06-20T11:04:50.379Z	debug	nativeedge_log	log_stdout=False, log_stderr=True, stderr_to_stdout=False
2025-06-20T11:04:50.448Z	debug	nativeedge_log	Process created, PID: 100079
2025-06-20T11:04:53.973Z	debug	nativeedge_log	Execution done (PID=100079, return_code=2): /opt/ansible/bin/ansible-playbook -vv -i /opt/manager/resources/deployments/default_tenant/a770b122-f1d3-4557-8a7d-f13ed7968adc/init_config_y9iubj/tmp8sd5zvi5/playbook/hosts --extra-vars='@/tmp/tmp39kjny67' /opt/manager/resources/deployments/default_tenant/a770b122-f1d3-4557-8a7d-f13ed7968adc/init_config_y9iubj/tmp8sd5zvi5/playbook/change_password.yml   --module-path=/opt/manager/resources/deployments/default_tenant/a770b122-f1d3-4557-8a7d-f13ed7968adc/tmpzn1y01ae
2025-06-20T11:04:54.082Z	debug	nativeedge_log	Context proxy closed
2025-06-20T11:04:54.604Z		nativeedge_event	Task rescheduled 'ne_ansible.tasks.run' -> The following Ansible tasks failed: The action ansible.builtin.uri failed for localhost: Status code was 400 and not [200, 302]: HTTP Error 400: Bad Request.

The message is "The following Ansible tasks failed: The action ansible.builtin.uri failed for localhost: Status code was 400 and not [200, 302]: HTTP Error 400: Bad Request" indicates that the password change event is unsuccessful."

Cause

Definition of the password for the Litmus Edge user in the secret type Litmus Edge, for the Admin Password was set to "Test!23" (seven characters)

Resolution

To resolve this issue, the Litmus Edge user in the secret type Litmus Edge, set the Admin Password an eight character password. For example, "Test1!23"

Affected Products

NativeEdge Solutions, NativeEdge
Article Properties
Article Number: 000335016
Article Type: Solution
Last Modified: 23 May 2026
Version:  3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.