StarlingX

Ansible Bootstrap failed with error message "Fail deployment-manager app helm-chart does not exists."

Bug #2065073 reported by Bala Shankar MV on 2024-05-07

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	StarlingX	Fix Released	High	Bala Shankar MV

Bug Description

Brief Description
-----------------
Lab installation failed in step ansible bootstrap with below mentioned message

2024-05-07 14:13:32,775 p=6428 u=sysadmin n=ansible | TASK [Fail deployment-manager app helm-chart does not exists] ******************
2024-05-07 14:13:32,776 p=6428 u=sysadmin n=ansible | Tuesday 07 May 2024 14:13:32 +0000 (0:00:00.504) 0:19:01.742 ***********
2024-05-07 14:13:32,799 p=6428 u=sysadmin n=ansible | fatal: [localhost]: FAILED! =>
msg: |-
The conditional check '(app_helm_chart.files[0].path | length == 0)' failed. The error was: error while evaluating conditional ((app_helm_chart.files[0].path | length == 0)): list object has no element 0

The error appears to be in '/var/home/sysadmin/wind-river-cloud-platform-deployment-manager-playbook.yaml': line 204, column 9, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

- name: Fail deployment-manager app helm-chart does not exists
^ here
2024-05-07 14:13:32,800 p=6428 u=sysadmin n=ansible | PLAY RECAP *********************************************************************
2024-05-07 14:13:32,800 p=6428 u=sysadmin n=ansible | localhost : ok=545 changed=302 unreachable=0 failed=1 skipped=467 rescued=0 ignored=0
2024-05-07 14:13:32,801 p=6428 u=sysadmin n=ansible | Tuesday 07 May 2024 14:13:32 +0000 (0:00:00.025) 0:19:01.767 ***********
2024-05-07 14:13:32,801 p=6428 u=sysadmin n=ansible | ===============================================================================

Severity
--------
Critical

Steps to Reproduce
------------------
Install (SX,DX) labs using latest STX master load

Expected Behavior
------------------
Bootstrap should go fine without any issues

Actual Behavior
----------------
Ansible bootstrap failed with below message

The error appears to be in '/var/home/sysadmin/wind-river-cloud-platform-deployment-manager-playbook.yaml': line 204, column 9, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

Reproducibility
---------------
3/3

System Configuration
--------------------
One node system(SX), Two node system(DX)

Branch/Pull Time/Commit
-----------------------
20240505T060103Z

Last Pass
---------
20240423T060054Z

Timestamp/Logs
--------------
/folk/cgts/logs/launchpad_2065073

Test Activity
-------------
Sanity - Lab Install

Workaround
----------
NA

See original description

Tags:

Revision history for this message

Bala Shankar MV (bshankar) wrote on 2024-05-07:

system_logs_simplex.tar Edit (5.4 MiB, application/x-tar)

description:

updated

Revision history for this message

Ghada Khalil (gkhalil) wrote on 2024-05-08 (last edit on 2024-05-08):

Based on the error returned by ansible, it looks like during install, the node is not booting from ISO, but instead is booting from already installed disk. This looks like a lab setup / procedural issue.

@Bala, please investigate.

Changed in starlingx:
assignee:	nobody → Bala Shankar MV (bshankar)

Revision history for this message

Kyle MacLeod (kmacleod) wrote on 2024-05-09:

From the ansible.log in the collect, this error looks significant:

In the ansible.log:

The error appears to be in '/var/home/sysadmin/wind-river-cloud-platform-deployment-manager-playbook.yaml': line 204, column 9, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

Bala Shankar MV (bshankar) on 2024-05-09

summary:	- Ansible Bootstrap failed with error message "The bootstrap of host - localhost has already been finalized. Please re-install before - attempting to bootstrap it again." + Ansible Bootstrap failed with error message "Fail deployment-manager app + helm-chart does not exists."
description:	updated

Revision history for this message

Ghada Khalil (gkhalil) wrote on 2024-05-13:

@Michel, please assign to someone from the DM team. deployment-manager is an optional component and is not part of StarlingX. The DM helm chart should not be part of the stx bootstrap.

Changed in starlingx:
assignee:	Bala Shankar MV (bshankar) → Michel Desjardins (desjarm)

Revision history for this message

Yuxing (yuxing) wrote on 2024-05-13:

@Ghada, the error "Fail deployment-manager app helm-chart does not exist" is not a part of the stx bootstrap as well, it comes from the dm repo. We need some hacks to insert the DM components into the sanity steps, otherwise we cannot use the DM to do the lab configuration and unlock steps. I would suggest moving it to internal as there's nothing to do in the stx upstream. But we can leave this LP for now until the sanity recovers

Revision history for this message

Ghada Khalil (gkhalil) wrote on 2024-05-14:

@Yuxing, please discuss with Rob Cooke on the best way forward. I'm not directly familiar with what the test team is using for stx sanity.

Bala Shankar MV (bshankar) on 2024-05-29

Changed in starlingx:
assignee:	Michel Desjardins (desjarm) → Bala Shankar MV (bshankar)

Revision history for this message

Ghada Khalil (gkhalil) wrote on 2024-05-29:

This is not an stx software issue and appears to be an env contamination issue as the failing component is not part of the stx builds. Follow-up is required by the sanity team.

Revision history for this message

Bala Shankar MV (bshankar) wrote on 2024-05-29:

Working on the fix internally, until will keep this LP open

Revision history for this message

Ghada Khalil (gkhalil) wrote on 2024-06-05:

@Bala, Given there was a green stx sanity on June 3, can this LP be closed?
Sanity Email: https://<email address hidden>/thread/ZOGKMIT42NCR6GVQ55T45B5MJLGHA4YF/