Prestage Orchestration - inconsistent state reporting for skipped subclouds
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Kyle MacLeod |
Bug Description
Brief Description
-----------------
Prestage Orchestration - Non-AIO-SX subclouds shows state complete for prestage
Note: it could show as complete, but we need a details message saying that the non-AIO-SX subcloud will be skipped for prestage
Severity
--------
Minor
Steps to Reproduce
------------------
Create a prestag-strategy for a group of subclouds which contains non-AIO-SX subclouds
Expected Behavior
------------------
Non-AIO-SX subclouds should be skipped and the details message field should have the reason why the subcloud was NOT prestaged.
Actual Behavior
----------------
state shows as 'complete'
Reproducibility
---------------
Reproducible
System Configuration
-------
Distributed Cloud system
Branch/Pull Time/Commit
-------
latest starlingx master
Last Pass
---------
This is a new test scenario
Timestamp/Logs
--------------
Not required
Test Activity
-------------
Feature testing
Workaround
----------
n/a
Fix proposed to branch: master /review. opendev. org/c/starlingx /distcloud/ +/832286
Review: https:/