I don’t know anything about this step, but this is simply a flag file indicating a particular step has completed. You’d want to look for what’s failing to cause this step to fail to complete.
A couple of quick “repo grep” commands shows that the flag file is created by a puppet runtime manifest here:
which gets applied from sysinv here, after it determines initial inventory is complete:
So I’d maybe start by looking at sysinv logs.
From: Yu ChanDer <yuchander@gmail.com>
Sent: Thursday, November 12, 2020 2:07 AM
To: starlingx-discuss@lists.starlingx.io; Khalil, Ghada <Ghada.Khalil@windriver.com>
Subject: [Starlingx-discuss] Ansible-playbook deploy distributed cloud failed
[Please note this e-mail is from an EXTERNAL e-mail address]
Hello Ghada and fellows:
Please help.
I built a stx.4.0 bootimages.iso from my Starlingx-layered-build environment,
and use the bootimages.iso to deploy a distributed cloud.
However, suffer an error after ansible-playbook deploying.
I have traced the yaml file to find the root cause, but I can't find any .sc_database_configured in /etc/platform.
Where I can find the .sc_database_configured?
TASK [bootstrap/persist-config : Wait for system controller database configuration to complete] ***
fatal: [localhost]: FAILED! => {"changed": false, "elapsed": 300, "msg": "Timeout waiting for system controller database configuration to complete"}
@ansible-playbooks\playbookconfig\src\playbooks\roles\bootstrap\persist-config\tasks\update_sysinv_database.yml
- name: Wait for system controller database configuration to complete
wait_for:
path: /etc/platform/.sc_database_configured
state: present
timeout: 300
msg: Timeout waiting for system controller database configuration to complete
when: distributed_cloud_role == 'systemcontroller'