-
Feature
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
Product / Portfolio Work
-
None
-
100% To Do, 0% In Progress, 0% Done
-
False
-
-
False
-
None
-
None
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
Feature Overview (aka. Goal Summary)
Send a warning if LSO PVs are provision through device names
We've seen a lot of case where users are provisioning volumes with device names. by-id can fail and failback to device name e.g with vsphere where ids are not populated if disk.EnableUUID = “TRUE” is not set to yes.
Goals (aka. expected user outcomes)
Be proactive to anticipate potential device name changes
Requirements (aka. Acceptance Criteria):
If LSO PVs are provisioned with device name a warning should be raised to inform the user that this is unsafe
| Deployment considerations | List applicable specific needs (N/A = not applicable) |
| Self-managed, managed, or both | both |
| Classic (standalone cluster) | yes |
| Hosted control planes | yes |
| Multi node, Compact (three node), or Single node (SNO), or all | all |
| Connected / Restricted Network | both |
| Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x) | all that apply to LSO |
| Operator compatibility | LSO |
| Backport needed (list applicable versions) | no |
| UI need (e.g. OpenShift Console, dynamic plugin, OCM) | no |
| Other (please specify) | N/A |
Out of Scope
High-level list of items that are out of scope. Initial completion during Refinement status.
only applies to LSO and device names
Background
Provide any additional context is needed to frame the feature. Initial completion during Refinement status.
see RFE-8389 although it will apply to non vmware env too
Customer Considerations
Make sure the warning is clear enough and perhaps link to a KB for resolution
Documentation Considerations
TBC but can likely be addressed with a KB
Interoperability Considerations
Initially intended for vsphere env but ultimately benefit all env using LSO
