Dell NativeEdge: La implementación de Litmus Edge falla en Install_init_config
Resumen: En este artículo, se explica por qué una implementación de Litmus Edge falla en el paso Install_init_config y cómo resolver el problema.
Síntomas
Se observa el siguiente mensaje durante la install_init_config paso cuando el diseño intenta cambiar la contraseña de la máquina virtual de Litmus Edge.
El cambio de contraseña se produce como una subtarea de 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.El mensaje es "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.”
Causa
La definición de la contraseña para el usuario de Litmus Edge en el tipo de seña secreta Litmus Edge para la contraseña de administrador se estableció en "Test!23" (siete caracteres)
Resolución
Para resolver este problema, el usuario de Litmus Edge en el tipo secreto Litmus Edge establece la contraseña del administrador en una contraseña de ocho caracteres. Por ejemplo, "Test1!23”