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

Bug 1630847

Summary: (Kuryr) OpenShift on OpenStack Node Network Configuration requires additional parameters
Product: OpenShift Container Platform Reporter: Alex Krzos <akrzos>
Component: InstallerAssignee: Tzu-Mainn Chen <tzumainn>
Installer sub component: openshift-installer QA Contact: GenadiC <gcheresh>
Status: CLOSED INSUFFICIENT_DATA Docs Contact:
Severity: medium    
Priority: medium CC: aos-bugs, gpei, jokerman, juriarte, mmccomas, tzumainn, wsun, xtian
Version: 3.11.0Keywords: Triaged
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: 2020-09-14 07:21:25 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:
Attachments:
Description Flags
provision log file none

Description Alex Krzos 2018-09-19 12:31:38 UTC
Description of problem:
While installing OpenShift on OpenStack with Kuryr reusing a node network, additional parameters are required using the provision.yml playbook.

I had to add the following parameters in order to get the provision playbook to succeed:
openshift_openstack_router_id
openshift_openstack_node_network_id
openshift_openstack_node_subnet_id

According to the documentation I would only have to define the following parameters:
openshift_openstack_router_name
openshift_openstack_node_subnet_name

The *_id parameters should be determined by the provision playbook with the _name parameters mentioned above.

Version-Release number of the following components:
(overcloud) [cloud-user@bastion openshift-ansible]$ git describe
openshift-ansible-3.11.9-1
(overcloud) [cloud-user@bastion openshift-ansible]$ git branch
  master
* release-3.11
(overcloud) [cloud-user@bastion openshift-ansible]$ git log --pretty=oneline | wc -l
13604
(overcloud) [cloud-user@bastion openshift-ansible]$ rpm -q openshift-ansible
package openshift-ansible is not installed
(overcloud) [cloud-user@bastion openshift-ansible]$ rpm -q ansible
ansible-2.6.3-1.el7ae.noarch
(overcloud) [cloud-user@bastion openshift-ansible]$ ansible --version
ansible 2.6.2
  config file = /home/cloud-user/openshift-ansible/ansible.cfg
  configured module search path = [u'/home/cloud-user/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python2.7/site-packages/ansible
  executable location = /bin/ansible
  python version = 2.7.5 (default, Sep 12 2018, 05:31:16) [GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]


How reproducible:
Always with this environment, all.yml and OSEv3.yml

Steps to Reproduce:
clone release-3.11 openshift-ansible, setup all.yml and OSEv3.yml attempt to run playbooks:

. /home/cloud-user/overcloudrc
ansible-playbook -vvv --user openshift -i inventory -i openshift-ansible/playbooks/openstack/inventory.py openshift-ansible/playbooks/openstack/openshift-cluster/prerequisites.yml 2>&1 >> /home/cloud-user/scale-ci/logs/openshift_prerequisites.log
ansible-playbook -vvv --user openshift -i inventory -i openshift-ansible/playbooks/openstack/inventory.py openshift-ansible/playbooks/openstack/openshift-cluster/provision.yml 2>&1 >> /home/cloud-user/scale-ci/logs/openstack_provision.log

^ provision.yml playbook fails with attached log

Actual results:
Please include the entire output from the last TASK line through the end of output if an error is generated

Expected results:

Additional info:
Please attach logs from ansible-playbook with the -vvv flag

Comment 1 Alex Krzos 2018-09-19 12:32:54 UTC
Created attachment 1484672 [details]
provision log file

Comment 4 Tzu-Mainn Chen 2018-09-28 12:53:37 UTC
Should be fixed by: https://github.com/openshift/openshift-ansible/pull/10131

Comment 6 Wei Sun 2018-11-06 05:45:58 UTC
Hi Alex,please help check if this bug could be verified.Thanks!