-
Notifications
You must be signed in to change notification settings - Fork 25
Issue in setting up Smart Edge Open branch 22.03.02 #10
Description
Hi,
I am having issue in setting up smart edge open on branch 22.03.02. The issue that I have encounter is the playbook does not able to find the role 'infrastructure/ptp/node' in playbooks/infrastructure.yml.
The full logs are as below:
2022-08-17 02:30:31.997 INFO: esc_smart_edge_cluster network_edge.yml: command: "/usr/bin/ansible-playbook -vv /opt/apps/backend/tasks/seo/dek/network_edge.yml --inventory /opt/apps/backend/tasks/seo/dek/inventory/automated/esc_smart_edge_cluster/inventory_esc_smart_edge_cluster.yml --limit controller_group"
2022-08-17 02:30:31.998 INFO: esc_smart_edge_cluster network_edge.yml: log file: "/opt/apps/backend/tasks/seo/dek/logs/esc_smart_edge_cluster_dek_2022-08-17_02-30-31_network_edge.yml.log"
2022-08-17 02:30:37.004 INFO: Only one cluster is being deployed. Redirecting logs to stdout.
ansible-playbook [core 2.11.6]
config file = /opt/apps/backend/tasks/seo/dek/ansible.cfg
configured module search path = ['/home/controller/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python3.9/site-packages/ansible
ansible collection location = /home/controller/.ansible/collections:/usr/share/ansible/collections
2022-08-17 02:30:37.021 INFO: <Command '/usr/bin/tail -n 100000 -f /opt/apps/backend/tasks/seo/dek/logs/esc_smart_edge_cluster_dek_2022-08-17_02-30-31_network_edge.yml.log', pid 13111>: process started
executable location = /usr/bin/ansible-playbook
python version = 3.9.13 (main, Jul 26 2022, 13:12:30) [GCC 10.3.1 20211027]
2022-08-17 02:30:37.023 ERROR: esc_smart_edge_cluster network_edge.yml: failed. Please check the logs: /opt/apps/backend/tasks/seo/dek/logs/esc_smart_edge_cluster_dek_2022-08-17_02-30-31_network_edge.yml.log
jinja version = 3.0.1
libyaml = True
Using /opt/apps/backend/tasks/seo/dek/ansible.cfg as config file
[DEPRECATION WARNING]: [defaults]callback_whitelist option, normalizing names
to new standard, use callbacks_enabled instead. This feature will be removed
from ansible-core in version 2.15. Deprecation warnings can be disabled by
setting deprecation_warnings=False in ansible.cfg.
redirecting (type: modules) ansible.builtin.selinux to ansible.posix.selinux
redirecting (type: modules) ansible.builtin.selinux to ansible.posix.selinux
redirecting (type: modules) ansible.builtin.sysctl to ansible.posix.sysctl
redirecting (type: modules) ansible.builtin.make to community.general.make
redirecting (type: modules) ansible.builtin.make to community.general.make
redirecting (type: modules) ansible.builtin.make to community.general.make
redirecting (type: modules) ansible.builtin.modprobe to community.general.modprobe
redirecting (type: modules) ansible.builtin.modprobe to community.general.modprobe
statically imported: /opt/apps/backend/tasks/seo/dek/tasks/reboot_server.yml
ERROR! the role 'infrastructure/ptp/controlplane' was not found in /opt/apps/backend/tasks/seo/dek/playbooks/roles:/opt/apps/backend/tasks/seo/dek/roles:/opt/apps/backend/tasks/seo/dek/roles/baseline_ansible:/opt/apps/backend/tasks/seo/dek/playbooks
The error appears to be in '/opt/apps/backend/tasks/seo/dek/playbooks/infrastructure.yml': line 59, column 7, but may
be elsewhere in the file depending on the exact syntax problem.
The offending line appears to be:
roles:
- role: infrastructure/ptp/controlplane
^ here
2022-08-17 02:30:38.025 INFO: ====================
2022-08-17 02:30:38.026 INFO: DEPLOYMENT RECAP:
2022-08-17 02:30:38.026 INFO: ====================
2022-08-17 02:30:38.026 INFO: DEPLOYMENT COUNT: 1
2022-08-17 02:30:38.027 INFO: SUCCESSFUL DEPLOYMENTS: 0
2022-08-17 02:30:38.027 INFO: FAILED DEPLOYMENTS: 1
2022-08-17 02:30:38.027 INFO: DEPLOYMENT "esc_smart_edge_cluster": FAILED
2022-08-17 02:30:38.028 INFO: ====================
2022-08-17 02:30:38.028 INFO: Deployment failed, pulling logs
2022_08_17_02_30_38_SmartEdge_experience_kit_archive.tar.gz 100% 783KB 22.1MB/s 00:00
log_collector 100% 15KB 10.5MB/s 00:00
log_collector.json
May I know if this is a known issue and is there any ways that we can used to fix this installation issue?