Fleets can contain devices running in different operating system (OS) modes. When a fleet template includes an OS image target, image-mode and package-mode devices process the delivered spec differently, which affects device update status and rollout progress.

Understanding this behavior helps you diagnose OutOfDate status on package-mode devices and plan fleet organization to avoid rollout issues.

How fleet specs are delivered

When a fleet template includes an OS image target, the Red Hat Edge Manager service renders the full spec and delivers it to all devices in the fleet regardless of OS mode. The service does not filter fleet template content per device. Every device receives the same rendered spec, including the spec.os.image field.

Agent-side atomic spec rejection

Package-mode devices reject the entire delivered spec when it contains a spec.os.image field. The rejection occurs atomically before any reconciler runs, which means the following:

• No configuration overlays from the new spec are applied.
• No application workloads from the new spec are updated.
• The device stays on its previously committed spec.
• No partial application of the spec occurs.

When the fleet template is updated to deliver a spec without an OS image target, package-mode devices accept and reconcile the new spec normally, including any configuration and application changes.

OutOfDate status on package-mode devices

The Red Hat Edge Manager service marks a package-mode device as OutOfDate when the device’s status.os.image (which is empty on package-mode devices) does not match the spec.os.image delivered from the fleet template. This is expected behavior and does not indicate an error.

Package-mode devices in this state continue to operate on their previously committed configuration. Image-mode devices in the same fleet process the spec normally and update their OS image.

Rollout batch stall limitation

Rollout batches that contain package-mode devices can stall when the fleet template includes an OS image target. Package-mode devices cannot satisfy the OS target, so the batch does not complete until the rollout timeout expires.

This stall does not affect the devices themselves, but it delays rollout progress for subsequent batches. To avoid this limitation, organize fleets so that OS image targets are applied only to fleets containing image-mode devices.