Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix for DM failure: Std subcloud installation #411

Merged
merged 1 commit into from
Nov 5, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 16 additions & 4 deletions docs/playbooks/wind-river-cloud-platform-deployment-manager.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -743,8 +743,20 @@
wait_for:
timeout: "{{ boot_wait_time }}"
register: waiting_after_reboot
# Unreachable: Ignore a task failure due to the host instance being ’UNREACHABLE’
# with the ignore_unreachable keyword. Ansible ignores the task errors but continues
# to execute future tasks against the unreachable host. This usually happens
# if the host is network-inaccessible. For example, during a second reboot that
# temporarily disrupts SSH connectivity, Ansible will mark it as unreachable since
# it can’t connect to the host at all.
ignore_unreachable: true

# Failed: It can ignore errors when the task is failed, except those syntax errors,
# undefined variable errors, connection failures, execution issues.
# This occurs if Ansible can reach the host, but the task itself encounters an issue. This
# could happen if the host is reachable but not fully ready to respond, or if a required
# port isn’t open yet.
ignore_errors: true

# Retry block: sometimes system reboots twice
# It will take some extra time.
- block:
Expand All @@ -760,7 +772,7 @@
delay: 20

# Waiting task after unlock to catch the right status
- name: Wait for {{ boot_wait_time }} seconds to ensure not affecting host status
- name: Waiting after second reboot for {{ boot_wait_time }} seconds to ensure not affecting host status
wait_for:
timeout: "{{ boot_wait_time }}"
register: waiting_after_new_reboot
Expand All @@ -773,9 +785,9 @@
- "Then, use subcloud reconfig command to complete deployment"
register: new_reboot
when: waiting_after_new_reboot.failed

when: waiting_after_reboot.failed

- name: Set retries to check resource reconciled status for simplex
set_fact:
host_reconcile_retries: 80
Expand Down
Loading