2022-12-06 22:41:56 +00:00
|
|
|
use base "installedtest";
|
|
|
|
use strict;
|
|
|
|
use testapi;
|
|
|
|
use utils;
|
|
|
|
|
|
|
|
sub run {
|
|
|
|
|
|
|
|
my $self = shift;
|
|
|
|
$self->root_console(tty => 3);
|
2023-03-29 21:29:52 +00:00
|
|
|
if (get_var("ARCH") eq "aarch64") {
|
|
|
|
# this should stop audit messages screwing things up
|
|
|
|
assert_script_run "rpm-ostree kargs --append=audit=0";
|
|
|
|
script_run "systemctl reboot", 0;
|
|
|
|
boot_to_login_screen;
|
|
|
|
$self->root_console(tty => 3);
|
|
|
|
}
|
2022-12-06 22:41:56 +00:00
|
|
|
|
|
|
|
# list available branches
|
|
|
|
my $subv = lc(get_var("SUBVARIANT"));
|
|
|
|
my $remote = "fedora";
|
|
|
|
$remote = "fedora-iot" if ($subv eq "iot");
|
|
|
|
assert_script_run "ostree remote refs $remote";
|
|
|
|
|
|
|
|
# get current branch
|
|
|
|
my $current = script_output "rpm-ostree status -b | grep fedora";
|
|
|
|
|
|
|
|
my $arch = lc(get_var("ARCH"));
|
|
|
|
|
|
|
|
# decide target
|
|
|
|
my $rebase;
|
|
|
|
my $target;
|
|
|
|
if ($current =~ "iot") {
|
|
|
|
$rebase = $current =~ "stable" ? "devel" : "stable";
|
|
|
|
$target = "fedora/${rebase}/${arch}/iot";
|
|
|
|
}
|
|
|
|
elsif ($current =~ "silverblue") {
|
|
|
|
my $relnum = get_release_number;
|
|
|
|
$rebase = $relnum - 1;
|
|
|
|
# avoid rebasing from 37 to <37, bad stuff happens
|
2023-02-17 04:36:03 +00:00
|
|
|
# FIXME when 38 branches, we should change this to RELNUM+1
|
2023-06-10 23:00:21 +00:00
|
|
|
$rebase = "38" if ($relnum eq "37");
|
|
|
|
# on update tests, just rebase to the 'official' ref for the
|
|
|
|
# release, as opposed to the custom ref we used when building;
|
|
|
|
# this should be more reliable than a different release
|
|
|
|
$rebase = $relnum if (get_var("ADVISORY_OR_TASK"));
|
|
|
|
$rebase = "rawhide" if ($rebase eq get_var("RAWREL"));
|
2022-12-06 22:41:56 +00:00
|
|
|
$target = "fedora/${rebase}/${arch}/silverblue";
|
|
|
|
}
|
|
|
|
elsif ($current =~ "coreos") {
|
|
|
|
$rebase = $current =~ "stable" ? "testing" : "stable";
|
|
|
|
$target = "fedora/${arch}/coreos/${rebase}";
|
|
|
|
}
|
|
|
|
|
|
|
|
# rebase to the chosen target
|
2023-03-23 05:59:21 +00:00
|
|
|
validate_script_output "rpm-ostree rebase $target --bypass-driver", sub { m/systemctl reboot/ }, 300;
|
2022-12-06 22:41:56 +00:00
|
|
|
script_run "systemctl reboot", 0;
|
|
|
|
|
|
|
|
boot_to_login_screen;
|
|
|
|
$self->root_console(tty => 3);
|
|
|
|
|
|
|
|
# check booted branch to make sure successful rebase
|
|
|
|
validate_script_output "rpm-ostree status -b", sub { m/$target/ }, 300;
|
|
|
|
|
|
|
|
# rollback and reboot
|
2023-03-02 18:16:52 +00:00
|
|
|
if (get_var("ADVISORY") eq "FEDORA-2023-f6afa6f9e5") {
|
|
|
|
# FIXME: workaround for a very odd phenomenon with this update
|
|
|
|
# https://bodhi.fedoraproject.org/updates/FEDORA-2023-f6afa6f9e5#comment-2919613
|
|
|
|
# if that keeps happening after the update is stable we will
|
|
|
|
# have to do this for all affected releases
|
|
|
|
script_run "rpm-ostree rollback && systemctl reboot", 0;
|
|
|
|
boot_to_login_screen(timeout => 450);
|
|
|
|
}
|
|
|
|
else {
|
|
|
|
validate_script_output "rpm-ostree rollback", sub { m/systemctl reboot/ }, 300;
|
|
|
|
script_run "systemctl reboot", 0;
|
|
|
|
boot_to_login_screen;
|
|
|
|
}
|
2022-12-06 22:41:56 +00:00
|
|
|
$self->root_console(tty => 3);
|
|
|
|
|
|
|
|
# check to make sure rollback successful
|
|
|
|
validate_script_output "rpm-ostree status -b", sub { m/$current/ }, 300;
|
|
|
|
}
|
|
|
|
|
|
|
|
sub test_flags {
|
|
|
|
return {fatal => 1};
|
|
|
|
}
|
|
|
|
|
|
|
|
1;
|
|
|
|
|
|
|
|
# vim: set sw=4 et:
|