f8779e5023
Recent changes for e.g edge scenarios caused intended move of discovery from controller to bootstrap compute node. The task is triggered by deploy-identifier to make sure it gets run on any deploy,scale, ... run. If deploy run is triggered with --skip-deploy-identifier flag, discovery will not be triggered at and as result causing failures in previously supported scenarios. This change moves the host discovery task to be an ansible deploy_steps_tasks that it gets triggered even if --skip-deploy-identifier is used, or the compute bootstrap node is blacklisted. Closes-Bug: #1831711 Change-Id: I4bd8489e4f79e3e1bfe9338ed3043241dd605dcb
13 lines
619 B
YAML
13 lines
619 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Recent changes for e.g edge scenarios caused intended move of discovery
|
|
from controller to bootstrap compute node. The task is triggered by
|
|
deploy-identifier to make sure it gets run on any deploy,scale, ... run.
|
|
If deploy run is triggered with --skip-deploy-identifier flag, discovery
|
|
will not be triggered at and as result causing failures in previously
|
|
supported scenarios.
|
|
This change moves the host discovery task to be an ansible
|
|
deploy_steps_tasks that it gets triggered even if --skip-deploy-identifier
|
|
is used, or the compute bootstrap node is blacklisted.
|