Heitor Matsui
3fcdf70d68
Exclude releases directory from sync in legacy upgrade
In an upgrade from stx.11 or stx.12, that are non-metapackage
releases, to stx.13, that is metapackage-aware, the sync between
controllers may end up deleting metapackage data incorrectly
from the /opt/software/releases directory, when one of the
controllers is metapackage-aware and the other is not.
This commit checks if the upgrade-in-progress flag exists on
the host, and if it does, it excludes the "releases" directory
from the rsync command executed by the neighbor sync, so that
the metapackage data is not affected.
Test Plan
PASS: upgrade end-to-end stx.12 to stx.13, verify the flag
is detected and the sync doesn't delete metapackage data
PASS: force the peer to sync from the active controller during
an upgrade, simulating failures or reboots, verify the flag
is detected and the sync doesn't delete metapackage data
Closes-bug: 2163452
Assisted-by: Amazon Kiro
Change-Id: I99e9df1165d9bb6cf8f96db4c424aa8ef9ef6df9
Signed-off-by: Heitor Matsui <heitorvieira.matsui@windriver.com>
2026-08-13 20:33:11 -03:00
2026-05-26 13:53:52 +00:00
2026-01-13 02:36:19 -05:00
2024-11-25 15:05:33 +00:00
2023-08-31 17:01:12 +00:00
2025-12-30 02:41:52 -05:00
2026-07-22 20:33:23 +00:00
2018-05-31 07:37:12 -07:00
2026-03-19 14:40:19 -03:00
2020-06-04 14:40:40 +02:00
2026-08-13 20:33:11 -03:00
2026-08-05 12:38:00 +00:00
2024-10-07 10:45:15 -03:00
2019-04-19 19:52:36 +00:00
2026-06-16 21:18:35 +00:00
2026-08-05 11:06:27 -03:00
2018-05-31 07:37:12 -07:00
2021-10-05 14:12:40 -04:00
2026-01-08 11:31:00 -03:00
2026-01-08 11:31:00 -03:00
2026-01-08 11:31:00 -03:00
2026-01-16 01:58:33 -05:00
2026-01-16 01:58:33 -05:00
2018-05-31 07:37:12 -07:00
2019-07-19 10:28:00 -04:00
2018-05-31 07:37:12 -07:00
2026-02-26 18:35:30 +00:00
2026-02-26 18:35:30 +00:00
2026-01-08 11:31:00 -03:00
stx-update
StarlingX Software Management