Package upgrades and removal

Package upgrades and removal

Radiator Software tests upgrades of the Radiator Server Linux packages with every nightly build and every release. This article lists the tested upgrade paths and describes what an upgrade or a removal does to your installation.

For the first installation, see Basic Installation.

Tested upgrade paths

The tested releases are selected from the releases published in the last 12 months:

• Every main release, X.Y.0.
• The newest patch release of each of those, for example 10.32.3. See Radiator software releases.

Each tested release is upgraded to every newer tested release and to the nightly build or release being tested. Every path is tested with both the rpm and the deb package.

For example, when the releases in the last 12 months are 10.31.0, 10.31.2, 10.32.0, 10.32.3, 10.33.0, 10.33.4, 10.34.0, and 10.34.1, these upgrade paths are tested:

When the tested build is a nightly build, two earlier nightly builds are also upgraded to it: the previous nightly build with a different version, and the nightly build last published to the nightly repositories, if it is a different version.

Upgrades from other patch releases, such as 10.32.1, are not tested.

Tested distributions

Each upgrade path runs on one distribution of its package type. The distribution changes between paths, so every distribution is tested with many upgrade paths.

What each test checks

Before the upgrade, the test installs the older release, adds a license, configures RADIUS clients that use PAP and EAP-TLS, and starts the radiator-server service. PAP and EAP-TLS authentication must succeed over IPv4 and IPv6. The test then adds files that an administrator could add through Radiator UI or the command line:

• A certificate and a private key under /var/lib/radiator/tls/.
• A template, a Lua script, a configuration backup, and other files under /var/lib/radiator/, including file and directory names with spaces and a symbolic link.
• A log file under /var/log/radiator/.
• A change to a packaged configuration file: /etc/default/radiator-server for deb and /etc/logrotate.d/radiator-server for rpm.

The test upgrades the package without interactive prompts. For deb, it uses the apt-get options -o Dpkg::Options::=--force-confdef -o Dpkg::Options::=--force-confold, which keep your version of changed configuration files.

After the upgrade, the test checks that:

• The installed package has the new version.
• The package restarted radiator-server, which runs the new binary and is still enabled.
• The added files have the same content, owner, group, and permissions as before the upgrade.
• The change to the packaged configuration file is still in place.
• PAP and EAP-TLS authentication still succeed over IPv4 and IPv6.

Removing the package

The removal tests run with the nightly build or release being tested.

deb: apt-get remove

• Stops radiator-server and removes the program files.
• Keeps the files under /var/lib/radiator and /var/log/radiator, including the files you added, and the packaged configuration files under /etc.

deb: apt-get purge

• Removes everything that apt-get remove removes.
• Removes /var/lib/radiator and /var/log/radiator completely, including your configuration, certificates, licenses, backups, and logs.
• Removes the packaged configuration files under /etc.

Back up your configuration before you purge the package. See Configuration backup and restore with shell scripts.

rpm: dnf remove

• Stops and disables radiator-server and removes the program files.
• Keeps the files you added under /var/lib/radiator and /var/log/radiator.
• Saves each packaged configuration file that you changed with the .rpmsave suffix, for example /etc/logrotate.d/radiator-server.rpmsave.