Epic Goal

• Release VolSync 0.5.1.  Since VolSync is a separate operator it can be released out of band of ACM releases - customers on ACM 2.6 will already be subscripted to the acm-2.6 operator channel (currently containing VolSync 0.5.0) and will automatically get VolSync 0.5.1 when it gets published.

Why is this important?

• Fixes required from the 0.5 release (which came out with ACM 2.6)
  • Fixes required for OADP
  • IPv6 fix for rsync: https://github.com/stolostron/backlog/issues/25441
  • Restic fix for FIPS: https://github.com/stolostron/backlog/issues/25925

Scenarios

1. Bring VolSync in line with base requirements for add-on.  FIPS, IPv6

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. Need to build 0.5.1 downstream operator - https://github.com/stolostron/backlog/issues/25735 (completed)

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>