Bug 1806395 - When glusterfs cantainer images are pre-pulled and given custom name and tag then the deployement of OCS is failing
Summary: When glusterfs cantainer images are pre-pulled and given custom name and tag ...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: cns-ansible
Version: ocs-3.11
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: John Mulligan
QA Contact: Prasanth
URL:
Whiteboard:
Depends On: 1806421
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-24 05:44 UTC by Arun Kumar
Modified: 2020-02-25 07:25 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-25 07:25:43 UTC
Embargoed:


Attachments (Terms of Use)

Description Arun Kumar 2020-02-24 05:44:28 UTC
Description of problem:

Deployment of OCS is failing with "openshift-ansible-3.11.170-2" at task "Check for specified container versions"
Inventory file contains valid and same image tags for all the gluster conatiner images, but deployemt of OCS is failing with message "A valid version tag must be specified for all GlusterFS container images"

Version-Release number of selected component (if applicable):
# rpm -qa|grep openshift-ansible
openshift-ansible-3.11.170-2.git.5.8802564.el7.noarch
openshift-ansible-roles-3.11.170-2.git.5.8802564.el7.noarch
openshift-ansible-docs-3.11.170-2.git.5.8802564.el7.noarch
openshift-ansible-playbooks-3.11.170-2.git.5.8802564.el7.noarch



failure message:
---------------------
TASK [openshift_storage_glusterfs : Check for specified container versions] *************************************************************************************************
task path: /usr/share/ansible/openshift-ansible/roles/openshift_storage_glusterfs/tasks/version_check.yml:7
fatal: [192.168.2.56]: FAILED! => {
    "changed": false, 
    "msg": "A valid version tag must be specified for all GlusterFS container images.\nValid image tags take the form of \"v3.x\" where \"x\" can be a one or two release\nversions (e.g. \"v3.0\" or \"v3.0.1\"). The following image versions were detected:\n\n\nHeketi: :v3.11.4\nglusterblock-provisioner: :v3.11.4\n"
}
 

images in the invetory file:
-----------------------------
#openshift_storage_glusterfs_image="rhgs3-rhgs-gluster-block-prov-rhel7:v3.11.5"
                                                                                
openshift_storage_glusterfs_heketi_image="rhgs3-rhgs-volmanager-rhel7:v3.11.5"  
openshift_storage_glusterfs_block_image="rhgs3-rhgs-gluster-block-prov-rhel7:v3.11.5"

Actual results: OCS Deployment is failing

Expected results: Deployment should pass

Comment 4 Scott Dodson 2020-02-24 14:11:27 UTC
Why do you want to do that? why don't you just specify the desired pull specs rather than pre-pulling, tagging, and providing just the image name? OpenShift will not function well without a registry from which to pull the required images and prepopulating every image is not expected to work.


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