Skip to content
Snippets Groups Projects
Commit 6023dfd3 authored by Denis Pynkin's avatar Denis Pynkin
Browse files

AUM OTA manual: copy hint with time settings for all tests

Use timedatectl to workaround NTP issues on some networks

With battery backed devices on networks with no properly reachable NTP servers
the boards would fail to automatically get the right time, so testers set it up
manually with `date`.

However, the hardware clock need to be configured as well for the time
configuration to survive a reboot, needed by the Apertis update manager OTA
test.

Without this, the device will fail to establish any TLS connection after the
reboot since every certificate will look like they are out of their validity
period.

This is only a workaround until we ensure NTP servers are reachable on the
testers' network, see https://phabricator.apertis.org/T6115



Signed-off-by: default avatarDenis Pynkin <denis.pynkin@collabora.com>
parent 96227328
No related branches found
No related tags found
No related merge requests found
......@@ -11,6 +11,16 @@ metadata:
maintainer: "Apertis Project"
description: "Test the apertis-update-manager API for updates over the air."
pre-conditions:
- >
This test requires a properly configured time source: when testing
devices not carrying a battery-backed real time clock in a network which
prevents connections to NTP servers (and only in that case) manually
ensure that the time on the device is set appropriately and that it is
propagated to the hardware clock so it is stay set on the next reboot if
the power is not plugged off.
- $ sudo timedatectl --adjust-system-clock set-time "2019-08-21 18:49:03" # use the appropriate date
resources:
- "The DUT u-boot environment must be clean: in u-boot, run: `env default -a` followed by `saveenv`"
- "A PC must be connected to DUT serial port"
......
......@@ -11,6 +11,16 @@ metadata:
maintainer: "Apertis Project"
description: "Ensure that failures due to disk full errors during network updates have no effect on the system"
pre-conditions:
- >
This test requires a properly configured time source: when testing
devices not carrying a battery-backed real time clock in a network which
prevents connections to NTP servers (and only in that case) manually
ensure that the time on the device is set appropriately and that it is
propagated to the hardware clock so it is stay set on the next reboot if
the power is not plugged off.
- $ sudo timedatectl --adjust-system-clock set-time "2019-08-21 18:49:03" # use the appropriate date
resources:
- "The DUT u-boot environment must be clean: in u-boot, run: `env default -a` followed by `saveenv`"
- "A PC must be connected to DUT serial port"
......
......@@ -11,6 +11,16 @@ metadata:
maintainer: "Apertis Project"
description: "Test the automatic rollback and blacklist mechanism of apertis-update-manager with network updates."
pre-conditions:
- >
This test requires a properly configured time source: when testing
devices not carrying a battery-backed real time clock in a network which
prevents connections to NTP servers (and only in that case) manually
ensure that the time on the device is set appropriately and that it is
propagated to the hardware clock so it is stay set on the next reboot if
the power is not plugged off.
- $ sudo timedatectl --adjust-system-clock set-time "2019-08-21 18:49:03" # use the appropriate date
resources:
- "The DUT u-boot environment must be clean: in u-boot, run: `env default -a` followed by `saveenv`"
- "A PC must be connected to DUT serial port"
......
......@@ -11,6 +11,16 @@ metadata:
maintainer: "Apertis Project"
description: "Test the apertis-update-manager uses only signed updates over the air."
pre-conditions:
- >
This test requires a properly configured time source: when testing
devices not carrying a battery-backed real time clock in a network which
prevents connections to NTP servers (and only in that case) manually
ensure that the time on the device is set appropriately and that it is
propagated to the hardware clock so it is stay set on the next reboot if
the power is not plugged off.
- $ sudo timedatectl --adjust-system-clock set-time "2019-08-21 18:49:03" # use the appropriate date
resources:
- "The DUT u-boot environment must be clean: in u-boot, run: `env default -a` followed by `saveenv`"
- "A PC must be connected to DUT serial port"
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment