Bug 1576732 - GCP cloud provider config has node tags parameter hardcoded value
Summary: GCP cloud provider config has node tags parameter hardcoded value
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.9.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.11.0
Assignee: Scott Dodson
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-10 09:29 UTC by Eduardo Minguez
Modified: 2018-08-02 12:18 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-08-02 12:18:14 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Github https://github.com/openshift openshift-ansible issues 7979 0 None None None 2018-05-10 09:29:05 UTC

Description Eduardo Minguez 2018-05-10 09:29:05 UTC 
Description of problem: GCP cloud provider config has node tags parameter hardcoded value

Version-Release number of the following components:
Latest & upstream master

How reproducible:
Nodes should be tagged as "'{{ openshift_gcp_prefix }}ocp' }" or loadbalancer services won't be accessible

Steps to Reproduce:
1. Deploy OCP in GCP
2. Don't tag instances with the previous tag
3. Create a loadbalancer service

Actual results:
Firewall rules are created but not applied to nodes

Expected results:
Allow users to specify the tag used (and explain it in the docs)

Additional info:
https://github.com/openshift/openshift-ansible/issues/7979 & https://github.com/openshift/openshift-ansible/pull/7980
Comment 1 Scott Dodson 2018-08-02 12:18:14 UTC 
Closing based on discussion in PR where Clayton mentions we don't want to do this.
Note You need to log in before you can comment on or make changes to this bug.