Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1685161 - In OCS 3.11 Deployment Guide, don't mention openshift_*_registry_*_image variables
Summary: In OCS 3.11 Deployment Guide, don't mention openshift_*_registry_*_image vari...
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: doc-Container_Native_Storage_with_OpenShift
Version: ocs-3.11
Hardware: Unspecified
OS: Linux
Target Milestone: ---
: ---
Assignee: Bhavana
QA Contact:
Depends On:
Blocks: 1694089
TreeView+ depends on / blocked
Reported: 2019-03-04 14:16 UTC by Patric Uebele
Modified: 2019-04-11 07:59 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)

Description Patric Uebele 2019-03-04 14:16:13 UTC
User-Agent:       Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.119 Safari/537.36
Build Identifier: 

In section 4.1 "Specify Advanced Installer Variables", remove references to openshift_storage_glusterfs_registry_image, openshift_storage_glusterfs_registry_block_image, and openshift_storage_glusterfs_registry_heketi_image, as these variables are not documented in

Reproducible: Always

Expected Results:  
It is recommended to specify image names and version tags for all containerized components. This is primarily to prevent components, particularly the Red Hat Gluster Storage pods, from upgrading after an outage which may lead to a cluster of widely disparate software versions. The relevant variables are:
- openshift_storage_glusterfs_image
- openshift_storage_glusterfs_block_image
- openshift_storage_glusterfs_heketi_image

Comment 2 RamaKasturi 2019-04-05 12:41:26 UTC
Acking the bug for 3.11.3

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