Comment 0 for bug 2036632

Revision history for this message
Cristian Mondo (cmondo) wrote :

Brief Description
-----------------

DM is unable to apply due to corrupt deployment-config.yaml

the metioned file only contains OS_REGION_NAME:

Severity
---------

is imposible to deploy subclouds

<Critical: System/Feature is not usable after the defect>

Steps to Reproduce
-----------------

install system controller with latest 23.09 load
upload deploy files
perform subcloud add
Expected Behavior

Subcloud is deployed successfully

Actual Behavior
-----------------

subcloud deployment fails at DM apply stage

Reproducibility
-----------------

Reproducible 100%

System Configuration
-----------------

DC

Last Pass
----------

Timestamp/Logs
-----------------

TASK [Fail if config file failed to apply] *************************************
Monday 18 September 2023 22:39:38 +0000 (0:00:53.431) 0:16:31.958 ******
fatal: [subcloud1]: FAILED! => changed=false
  msg:
  - Failed to apply DM config file
  - 'Check syntax into config file. See documentation examples. '
  - Err_code= dm_apply_failed
  - 'Config file error: error: error validating "/home/sysadmin/deployment-config.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false'

Alarms
------

no alarms present

Test Activity
-----------------

Feature Testing Subcloud Name Reconfiguration

Workaround
-----------

N/A