Epic Goal

• MicroShift support upgrades on rpm based deployments

Why is this important?

• We need to automate the lifecycle of Edge Devices for scalable operations.
• Upgrading to new versions of MicroShift must be an automated process.
• We will have RPM based deployments which we need to support, too.

Scenarios

1. Customer has an RPM based installation in the field and needs to update to a new MicroShift release. Customer can simply "yum update" and "reboot" to apply the update.
2. Y and Z stream updates  have to be supported. Y updates are especally important for GA, as we explicility do not support that from pre-GA versions.

Out of scopes

Rollbacks. In case the update fails for whatever reasons, no rollback is possible. We need to make sure to document this with a prominent warning. The rationale here is that we expect device provisioning to be automated and a device suffering from a failed update can easily be provisioned. Adequate backup/restore mechanisms for workload data should be in place. 

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents
• Skip version updates (e.g. from V4.10 to V4.12) are detected and fail the update
• Update should be as seamless as possible, e.g. there should be no network interruption between "yum update" and the "reboot". 

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>