Chapter 5. Upgrading the Red Hat Edge Manager RPM installation
Upgrade the flightctl-services package on your Red Hat Enterprise Linux host to move to a newer Red Hat Edge Manager release. You can run the upgrade while Flight Control services are running; after the package upgrade completes, restart the services and verify that they are healthy.
Prerequisites
-
An existing Red Hat Edge Manager installation on Red Hat Enterprise Linux that uses the
flightctl-servicesRPM. For more information, see Additional resources. - An active Red Hat Edge Manager subscription that includes the content repositories for the release you are upgrading to
- Administrative access (root or sudo-capable user) on the Red Hat Enterprise Linux host
-
You are logged in to the Red Hat Container Registry at
registry.redhat.ioon the Red Hat Enterprise Linux host (sudo podman login registry.redhat.iowith your Red Hat Customer Portal credentials). Podman must pull updated container images when services restart; without registry authentication,dnfcan report a successful upgrade while Flight Control services fail to start. -
A current backup of the PostgreSQL database that stores Flight Control data (the
flightctldatabase), created according to your organization’s RPO, or a planned maintenance window to create that backup before you upgrade
Procedure
- Back up the PostgreSQL database for Red Hat Edge Manager on your Red Hat Enterprise Linux host before you change packages. Plan retention, tooling, and verification using Backing up the PostgreSQL database for Red Hat Edge Manager on Red Hat Enterprise Linux.
- SSH into your Red Hat Enterprise Linux host.
Authenticate to the Red Hat Container Registry if you are not already logged in. Enter your Red Hat Customer Portal credentials when prompted. Without a valid registry login, services can fail to pull updated images after the package upgrade even when
dnfcompletes successfully.sudo podman login registry.redhat.ioEnable the content repositories for the Red Hat Edge Manager release you are upgrading to. Run a command that follows the pattern in the following example, replacing the placeholders with the repository identifiers that match your target release, Red Hat Enterprise Linux version, and system architecture:
sudo subscription-manager repos --enable edge-manager-<release>-for-rhel-<major_version>-<architecture>-rpmsList available versions of the
flightctl-servicespackage in your enabled repositories:sudo dnf repoquery --showduplicates flightctl-servicesUpgrade the Red Hat Edge Manager services package:
sudo dnf upgrade -y flightctl-servicesNoteYou do not need to stop Flight Control services before this step. The supported upgrade path applies database migrations while services may still be running older versions during the transition.
Restart Flight Control so all units run the upgraded software:
sudo systemctl restart flightctl.targetVerify that the required services are active:
sudo systemctl list-units flightctl-*.serviceEnsure that all listed services show a status of active. Some units are one-time initialization tasks and correctly display
active(exited); persistent services displayactive(running). For more information, see Additional resources.Optional: If you installed the Flight Control CLI from the RPM, upgrade it to match the server:
sudo dnf upgrade -y flightctl-cli
Troubleshooting
If services do not run correctly after the upgrade, use the following command, replacing <impacted_service> with the unit name:
sudo journalctl -u <impacted_service> -b --no-pager