Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1642923

Summary: Deployment playbook fails at task "Enable RHEL repositories" with error "'openshift_version' is undefined"
Product: OpenShift Container Platform Reporter: Mohammed Salih <mputhenp>
Component: InstallerAssignee: Tzu-Mainn Chen <tzumainn>
Status: CLOSED DUPLICATE QA Contact: Johnny Liu <jialiu>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.11.0CC: aos-bugs, jokerman, mmccomas
Target Milestone: ---   
Target Release: 3.11.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-12-03 14:52:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Mohammed Salih 2018-10-25 10:21:39 UTC
Description of problem:
Deployment playbook fails at task "Enable RHEL repositories" with error "'openshift_version' is undefined". 'openshift_version' variable is supposed to be derived automatically during the playbook run.
here is the output from failing task. https://paste.fedoraproject.org/paste/urrC2jkdIx88viVjx5T8eA

Provisioning was done using command
ansible-playbook --user openshift -i /usr/share/ansible/openshift-ansible/playbooks/openstack/inventory.py -i inventory /usr/share/ansible/openshift-ansible/playbooks/openstack/openshift-cluster/provision.yml

Workaround or a fix would be to include "- import_playbook: ../../init/version.yml" to /usr/share/ansible/openshift-ansible/playbooks/openstack/openshift-cluster/provision.yml

Version-Release number of selected component (if applicable):
OCP version 3.11

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Tzu-Mainn Chen 2018-12-03 14:52:24 UTC

*** This bug has been marked as a duplicate of bug 1642929 ***