Epic Goal*

 We should have a test that OCP upgrade does not result in device symlinks missing in /dev/disk/by-id and thus does not break applications that use local-storage-operator (for example ODF).

 
Why is this important? (mandatory)

As result of OCPBUGS-16670, we should have an e2e test to prevent such bugs in the future. For example having a test with LSO + few local devices installed, cluster upgraded and check that LSO PVs are still usable. We can add LSO upgrade to the test too. 

 
Scenarios (mandatory) 

1. RHEL 9.x removes an udev rule
2. RHCOS is updated to  that version
3. OCP gets that RHCOS
4. A nightly CI -upgrade job upgrades a cluster to that version and sees some symlinks in /dev/disk/by-id/ are missing. Such job fails, people investigate why and restore the udev rule / device symlink. 
5. No customer cluster gets broken by a missing udev rule.

 
Dependencies (internal and external) (mandatory)

Contributing Teams(and contacts) (mandatory) 

Maybe RHCOS - they could help with RHCOS / udev related questions / issues.

• Development - 
• Documentation -
• QE - 
• PX - 
• Others -

Acceptance Criteria (optional)

E2e job exists for at least one cloud. All clouds are strongly preferred, as they often have cloud-specific udev rules.

Drawbacks or Risk (optional)

Done - Checklist (mandatory)

The following points apply to all epics and are what the OpenShift team believes are the minimum set of criteria that epics should meet for us to consider them potentially shippable. We request that epic owners modify this list to reflect the work to be completed in order to produce something that is potentially shippable.

• CI Testing -  Basic e2e automationTests are merged and completing successfully
• Documentation - Content development is complete.
• QE - Test scenarios are written and executed successfully.
• Technical Enablement - Slides are complete (if requested by PLM)
• Engineering Stories Merged
• All associated work items with the Epic are closed
• Epic status should be “Release Pending”