Cause: Documentation links were removed from the Attach Storage page when the Create Storage page was added.
Consequence: There were no doc links directing you to additional help around storage topics.
Fix: A 'Learn More' link was added to the Create Storage page.
Result: If attaching storage and there are no PVCs available, you will be directed to Create Storage. The Create Storage page will show a link to 'Learn More' which directs the user to the documentation dev guide page about using persistent volumes.
Description of problem:
From OCP 3.3, documentation about using persistent volumes is removed from attach storage page
Version-Release number of selected component (if applicable):
v3.3.0.21
How reproducible:
Always
Steps to Reproduce:
1.Create app from image from web console
2.Go to DC page
3.Click "Actions -> Attach Storage"
Actual results:
3. There is no documentation about using persistent volumes on Attach Storage page
Expected results:
3. Should populate a documentation about how to claim storage from a persistent volume
Additional info:
Comment 2Jessica Forrester
2016-11-08 15:26:45 UTC
This change was intentional because we now let you Add Storage (create a pvc) from the web console. That said we may want to consider whether we should have a link to the documentation from the Create Storage page.
Comment 3openshift-github-bot
2016-12-13 22:10:36 UTC
Checked against v3.5.0.7,
1.Create app from image from web console
2.Go to DC page
3.Click Actions -> Add Storage
4.
1) When PVC exists in current project, no documentation will be shown
2) When there is no PVC, a Create Storage link will be provided on page, clicking on "Create Storage" will redirect to create-pvc page, there is Learn More link on create storage page pointing to dev_guide/persistent_volumes.html
Move to VERIFIED
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2017:0884