Hide Forgot
2. What is the nature and description of the request? Alter the routine that generates these "randomly generated" pvc volume names, moving the more unique strings to the end of the string, in this case the first two strings after pvc- (unique pieces) rather than after pvc- tag. This way sort works more naturally without more complexity. 3. Why does the customer need this? (List the business requirements here) Faster troubleshooting and for minimizing human error as the volume names may or may not be associated with the same project. 4. How would the customer like to achieve this? (List the functional requirements here) For example: HOW IT IS: Instead of the "random" pvc volume names having the more unique strings (first two fields, delimited by -) after pvc-: $ oc get pv |grep 9174|grep 37|sort pvc-02718af7-3776-11e8-9174-06fcfbf4e02a 1Gi RWO Delete Bound xyz/abc gluster-cns-abc 33d pvc-1b759837-381e-11e8-9174-06fcfbf4e02a 1Gi RWO Delete Bound pqr/mno gluster-cns-abc 33d HOW IT SHOULD BE TO MAKE IT EASIER TO READ FOR SUPPORT REASONS: The randomly generated pvc volume name displays the more unique strings (first two fields, delimited by -) at the end of the string, instead of after pvc: $ oc get pv |grep 9174|grep 37 |sort pvc-11e8-9174-06fcfbf4e02a-3769-cd478dbf 2Gi RWO Delete Bound xyz/abc gluster-cns-abc 33d pvc-11e8-9174-06fcfbf4e02a-3775-f953adf8 1Gi RWO Delete Bound pqr/mno gluster-cns-abc 33d pvc-11e8-9174-06fcfbf4e02a-3776-02718af7 1Gi RWO Delete Bound abc/pqr 5. For each functional requirement listed in question 4, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. oc get pv |grep pvc-11e8-9174|sort oc get pvc |grep pvc-11e8-9174|sort
With the introduction of OpenShift 4, Red Hat has delivered or roadmapped a substantial number of features based on feedback by our customers. Many of the enhancements encompass specific RFEs which have been requested, or deliver a comparable solution to a customer problem, rendering an RFE redundant. This bz (RFE) has been identified as a feature request not yet planned or scheduled for an OpenShift release and is being closed. If this feature is still an active request that needs to be tracked, Red Hat Support can assist in filing a request in the new JIRA RFE system, as well as provide you with updates as the RFE progress within our planning processes. Please open a new support case: https://access.redhat.com/support/cases/#/case/new Opening a New Support Case: https://access.redhat.com/support/cases/#/case/new As the new Jira RFE system is not yet public, Red Hat Support can help answer your questions about your RFEs via the same support case system.