keremet/rpm-ostree
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
466f66fcd4
rpm-ostree/tests/vmcheck/test-autoupdate-stage.sh

63 lines
2.4 KiB
Bash
Raw Normal View History

Add "ex-stage" update policy, support for ostree staged deployments Following up to https://github.com/projectatomic/rpm-ostree/pull/1352 AKA 506910d9300120f57ce710206ddc6fc0f2c9a628 which added an experimental flag to globally enable deployment staging, let's add an `ex-stage` automatic update policy. I chose to create a new `test-autoupdate-stage.sh` and rename the previous one to `test-autoupdate-check.sh` in going with the previous theme of smaller test files; it's way faster to iterate on new tests when it's a new file. And adding staging at the top would have been weird. This was all quite straightforward, just plumbing through lots of layers. Closes: #1321 Approved by: jlebon
2018-03-29 16:24:53 +03:00
#!/bin/bash
#
# Copyright (C) 2018 Jonathan Lebon
# Copyright (C) 2018 Red Hat, Inc.
#
# This library is free software; you can redistribute it and/or
# modify it under the terms of the GNU Lesser General Public
# License as published by the Free Software Foundation; either
# version 2 of the License, or (at your option) any later version.
#
# This library is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# Lesser General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public
# License along with this library; if not, write to the
# Free Software Foundation, Inc., 59 Temple Place - Suite 330,
# Boston, MA 02111-1307, USA.
set -euo pipefail
. ${commondir}/libtest.sh
. ${commondir}/libvm.sh
set -x
# Prepare an OSTree repo with updates
vm_ostreeupdate_prepare_reboot
vm_ostreeupdate_create v2
vm_rpmostree cleanup -m
vm_rpmostree status > status.txt
status: Rework auto-update status display First, split it into its own section; it's important enough to merit it. Second, explicitly reference the systemd timer/service units. For example, a question I often have is "when is the next run" and of course you can get that rpm `systemctl status rpm-ostreed-automatic.timer` but you have to know that, and the reminder helps. (I briefly looked at implementing the `Trigger` line from `systemctl status` but it's not entirely trivial...tempting to just fork off a `systemctl status | grep `) Prep for unifying this text with the message we print when one does `rpm-ostree upgrade` when auto-updates are enabled. Closes: #1432 Approved by: jlebon
2018-06-28 17:54:52 +03:00
assert_file_has_content status.txt 'AutomaticUpdates: disabled'
Stabilize `stage` automatic update policy Now that staging is the default, there's no reason for this policy not to be stable too. Closes: #1510 Approved by: jlebon
2018-08-21 00:53:56 +03:00
vm_change_update_policy stage
vm_rpmostree status > status.txt
assert_file_has_content_literal status.txt 'AutomaticUpdates: stage; rpm-ostreed-automatic.timer: inactive'
# And test that we still support "ex-stage"
Add "ex-stage" update policy, support for ostree staged deployments Following up to https://github.com/projectatomic/rpm-ostree/pull/1352 AKA 506910d9300120f57ce710206ddc6fc0f2c9a628 which added an experimental flag to globally enable deployment staging, let's add an `ex-stage` automatic update policy. I chose to create a new `test-autoupdate-stage.sh` and rename the previous one to `test-autoupdate-check.sh` in going with the previous theme of smaller test files; it's way faster to iterate on new tests when it's a new file. And adding staging at the top would have been weird. This was all quite straightforward, just plumbing through lots of layers. Closes: #1321 Approved by: jlebon
2018-03-29 16:24:53 +03:00
vm_change_update_policy ex-stage
vm_rpmostree status > status.txt
Stabilize `stage` automatic update policy Now that staging is the default, there's no reason for this policy not to be stable too. Closes: #1510 Approved by: jlebon
2018-08-21 00:53:56 +03:00
assert_file_has_content_literal status.txt 'AutomaticUpdates: stage; rpm-ostreed-automatic.timer: inactive'
Add "ex-stage" update policy, support for ostree staged deployments Following up to https://github.com/projectatomic/rpm-ostree/pull/1352 AKA 506910d9300120f57ce710206ddc6fc0f2c9a628 which added an experimental flag to globally enable deployment staging, let's add an `ex-stage` automatic update policy. I chose to create a new `test-autoupdate-stage.sh` and rename the previous one to `test-autoupdate-check.sh` in going with the previous theme of smaller test files; it's way faster to iterate on new tests when it's a new file. And adding staging at the top would have been weird. This was all quite straightforward, just plumbing through lots of layers. Closes: #1321 Approved by: jlebon
2018-03-29 16:24:53 +03:00
vm_rpmostree upgrade --trigger-automatic-update-policy
vm_assert_status_jq ".deployments[1][\"booted\"]" \
".deployments[0][\"staged\"]" \
".deployments[0][\"version\"] == \"v2\""
vm_rpmostree status -v > status.txt
assert_file_has_content status.txt "Staged: yes"
upgrade: Note if automatic updates are enabled When e.g. FAH does the automatic update transition, let's remind people who are doing it manually still. Closes: #1399 Approved by: jlebon
2018-06-11 21:30:55 +03:00
vm_rpmostree upgrade > upgrade.txt
Stabilize `stage` automatic update policy Now that staging is the default, there's no reason for this policy not to be stable too. Closes: #1510 Approved by: jlebon
2018-08-21 00:53:56 +03:00
assert_file_has_content_literal upgrade.txt 'note: automatic updates (stage) are enabled'
Add "ex-stage" update policy, support for ostree staged deployments Following up to https://github.com/projectatomic/rpm-ostree/pull/1352 AKA 506910d9300120f57ce710206ddc6fc0f2c9a628 which added an experimental flag to globally enable deployment staging, let's add an `ex-stage` automatic update policy. I chose to create a new `test-autoupdate-stage.sh` and rename the previous one to `test-autoupdate-check.sh` in going with the previous theme of smaller test files; it's way faster to iterate on new tests when it's a new file. And adding staging at the top would have been weird. This was all quite straightforward, just plumbing through lots of layers. Closes: #1321 Approved by: jlebon
2018-03-29 16:24:53 +03:00
# And ensure that we have new content in /etc after staging
vm_cmd echo new-content-in-etc \> /etc/somenewfile
vm_reboot
vm_assert_status_jq ".deployments[0][\"booted\"]" \
".deployments[0][\"staged\"]|not" \
".deployments[1][\"staged\"]|not" \
".deployments[0][\"version\"] == \"v2\""
vm_cmd cat /etc/somenewfile > somenewfile.txt
assert_file_has_content somenewfile.txt new-content-in-etc
echo "ok autoupdate staged"
Reference in New Issue Copy Permalink