Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1576732 - GCP cloud provider config has node tags parameter hardcoded value
GCP cloud provider config has node tags parameter hardcoded value
Status: CLOSED WONTFIX
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer (Show other bugs)
3.9.0
Unspecified Unspecified
medium Severity medium
: ---
: 3.11.0
Assigned To: Scott Dodson
Johnny Liu
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-05-10 05:29 EDT by Eduardo Minguez
Modified: 2018-08-02 08:18 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-08-02 08:18:14 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Github https://github.com/openshift/openshift-ansible/issues/7979 None None None 2018-05-10 05:29 EDT

  None (edit)
Description Eduardo Minguez 2018-05-10 05:29:05 EDT
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 08:18:14 EDT
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.