Commit data and reboot right after RW-Upgrade 27/271127/2 accepted/tizen/6.5/unified/20220222.132747 submit/tizen_6.5/20220221.170654 submit/tizen_6.5/20220221.170828
authorMateusz Moscicki <m.moscicki2@partner.samsung.com>
Tue, 15 Feb 2022 14:09:30 +0000 (15:09 +0100)
committerMateusz Moscicki <m.moscicki2@partner.samsung.com>
Mon, 21 Feb 2022 14:30:29 +0000 (15:30 +0100)
Change-Id: I5ea54eb86edfb8c701c9680da399d861ade313e0

upgrade/update-post.sh

index 8aa3bb9c3a61d6a99762acdb18a8b37076db6d00..dd52044b6ff15e000e36340f29cba839635375d8 100755 (executable)
@@ -4,7 +4,16 @@ PATH=/bin:/usr/bin:/sbin:/usr/sbin
 
 if [[ $(</proc/cmdline) =~ partition_ab= ]]
 then
-    systemctl isolate default.target
+    # Finalize upgrade right after RW-Upgrade
+    #
+    # It's possible to start upgraded system and check if there are any errors
+    # there.  This allows doing checking at later point of time, potentially
+    # catching more errors from new system (eg. some apps failing to start
+    # after upgrade). Current approach is to commit data after upgrade scripts
+    # succeeds, which simply means that system is guaranted to be upgraded even
+    # if some of the apps would fail.
+    /usr/share/upgrade/update-finalize.sh
+    # systemctl isolate default.target
 else
     reboot -f
 fi