d634510319
For Redfish-based subcloud installs which use a local ostree repo as the basis of their install, we perform a secondary ostree pull from the system controller. This will pull any ostree commits which have been applied (via patch) since the local ostree repo was created. Note that this also requires syncing of the patch metadata via /opt/patching. This step is done via the install ansible playbook. Test Plan: PASS: - Simulate a local ostree-based install during a sushy subcloud add in libvirt. Verify that a remote ostree pull retrieves any patch commits from the system controller. This is done by manipulating ostree repo contents on the system controller during the miniboot.cfg kicktart. PASS: - Prestage a subcloud from a non-patched system controller. Prestaged ostree_repo is stored on platform-backup partition. Patch the system controller. Add the prestaged subcloud. Verify that the subcloud boots and that the patched ostree commit is transferred to the subcloud during the miniboot.cfg kickstart. Partial-Bug: 1998256 Signed-off-by: Kyle MacLeod <kyle.macleod@windriver.com> Change-Id: Iee08b40dc2b930dacbbf4df08b0f727eb945d4ba
metal
StarlingX Bare Metal Management