Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1367718 - Should populate documentation about using persistent volumes on Attach Storage page
Should populate documentation about using persistent volumes on Attach Storag...
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console (Show other bugs)
3.3.0
Unspecified Unspecified
medium Severity low
: ---
: ---
Assigned To: Jessica Forrester
Yadan Pei
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-08-17 06:02 EDT by Yadan Pei
Modified: 2017-07-24 10 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
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.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-04-12 15:06:22 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
PVCDocs (22.22 KB, image/png)
2016-08-17 06:03 EDT, Yadan Pei
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0884 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.5 RPM Release Advisory 2017-04-12 18:50:07 EDT

  None (edit)
Description Yadan Pei 2016-08-17 06:02:56 EDT
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 1 Yadan Pei 2016-08-17 06:03 EDT
Created attachment 1191554 [details]
PVCDocs
Comment 2 Jessica Forrester 2016-11-08 10:26:45 EST
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 3 openshift-github-bot 2016-12-13 17:10:36 EST
Commit pushed to master at https://github.com/openshift/origin-web-console

https://github.com/openshift/origin-web-console/commit/736bf03b6717b345a07d8c293f286ecf06323c7c
Bug 1367718 - Add learn more link to create storage page
Comment 4 Troy Dawson 2017-01-20 18:27:12 EST
This has been merged into ocp and is in OCP v3.5.0.7 or newer.
Comment 5 Yadan Pei 2017-01-21 20:01:35 EST
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
Comment 7 errata-xmlrpc 2017-04-12 15:06:22 EDT
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

Note You need to log in before you can comment on or make changes to this bug.