Page MenuHomeVyOS Platform

Update Procedure Blocked Between `flavor` and `flavor-update` Types
Closed, WontfixPublicBUG

Description

Description

The recent flavor check feature prevents using xxx-update flavors for system updates. This breaks the expected behavior where update images should be usable for updating existing installations.

Expected Behavior

Users should be able to use name-update flavor images to update systems installed with the corresponding name flavor.

Current Behavior

Due to strict flavor matching, update images with the name-update flavor cannot be used to update systems installed with the name flavor. This effectively blocks the update process for many users.

Steps to Reproduce

  1. Install VyOS using a name flavor image (e.g., proxmox).
  2. Attempt to update using a name-update flavor image (e.g., proxmox-update).
  3. Observe that the update is rejected due to a flavor mismatch.

Impact

  • Customers are unable to perform updates using xxx-update images.
  • Forces unnecessary fresh installations, disrupting operations and automation pipelines.

Root Cause

The validation code enforces an exact flavor match: Image Installer Validation Code (Lines 753–759)

Proposed Resolution

Adjust the flavor check logic to treat name and name-update as compatible for update purposes.

Details

Version
1.4, 1.5, rolling
Is it a breaking change?
Perfectly compatible
Issue type
Bug (incorrect behavior)
Story points
2

Event Timeline

zsdc changed the task status from Open to Confirmed.
zsdc triaged this task as Urgent! priority.
dmbaturin claimed this task.
dmbaturin subscribed.

*-update flavors are no longer used in LTS releases — there is no need to, and it's much simpler for users when they can just use openstack or whatever ISO flavor for upgrade.

Existing systems that are running images like openstack-update can still be updated to new releases, because the flavor compatibility check is not in those older releases. Such systems would not be able to be upgraded to new *-update images, but it's not a concern, since we don't plan to make any new such images.

Downgrade is not officially supported, and in an emergency, people can still bypass the compatibility check, so I'm inclined to close this as "won't fix".

But if any new information turns up, feel free to reopen!