071f1d3715
Previously, software sync relied solely on the subcloud's
SW_VERSION, causing issues when the system controller
and subcloud ran different software versions (e.g.,
stx 11.0 and stx10.0). This led to incorrect software metadata
sync, as the ostree_feed_repo_dir path was constructed
using the subcloud's version, resulting in mismatched
paths and unnecessary synchronization.
This change:
1.Ignores the software sync if system controller is
stx11 and greater and subcloud with stx10
2.Ensures software sync only occurs when both the system
controller and the subcloud run the same software version.
This prevents unintended sync when versions differ,
ensuring metadata is only transferred when appropriate.
Disabling sync-patch-metadata as it no longer used from stx-11
Test Plan:
PASS N-1 subcloud deployment should not show incorrect
patch as installed after system controller upgrade
PASS Verify subcloud add and install from SystemController with
stx 10 patch level applied
PASS Verify N subcloud add, in upgraded system controller
PASS No alarm found
Closes-Bug: 2103692
Change-Id: I3213ad335a43ac3b746c79d3b9545eb4742dae8e
Signed-off-by: rummadis <ramu.ummadishetty@windriver.com>
stx-ansible-playbooks
StarlingX Bootstrap and Deployment Ansible1 Playbooks
Execution environment
- Unix like OS (recent Linux based distributions, MacOS, Cygwin)
- Python 3.8 and later
Additional Required Packages
In addition to the pakages listed in requirements.txt and test-requirements.txt, the following packages are required to run the playbooks remotely:
- python3-pexpect
- python3-ptyprocess
- sshpass
Supported StarlingX Releases
The playbooks are compatible with StarlingX R8.0 and later.
Executing StarlingX Playbooks
Bootstrap Playbook
For instructions on how to set up and execute the bootstrap playbook
from another host, please refer to the StarlingX Documentation2, at
Installation Guides, section Configure
controller-0 of the respective system deployment type.
Developer Notes
This repository is not intended to be developed standalone, but rather as part of the StarlingX Source System, which is defined by the StarlingX manifest3.