Bug 1694724
Summary: | [TSB] Ansible playbooks are overwriting the var 'template_service_broker_selector' making the deployment fail | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Andre Costa <andcosta> |
Component: | Service Broker | Assignee: | Shawn Hurley <shurley> |
Status: | CLOSED ERRATA | QA Contact: | Zihan Tang <zitang> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.11.0 | CC: | aos-bugs, chezhang |
Target Milestone: | --- | ||
Target Release: | 3.11.z | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-06-26 09:07:55 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
Andre Costa
2019-04-01 13:18:56 UTC
I have been unable to reproduce this bug locally. QA can you validate that you can reproduce? As I know, template-service-broker works on `master` node by default. I tried to add parameters template_service_broker_selector={"node-role.kubernetes.io/compute": "true"} in playbook, the playbook passed, but parameter not works, it still works on master. # oc get all -n openshift-template-service-broker NAME READY STATUS RESTARTS AGE pod/apiserver-h9ghc 1/1 Running 0 2h NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/apiserver ClusterIP 172.30.63.72 <none> 443/TCP 2h NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE daemonset.apps/apiserver 1 1 1 1 1 node-role.kubernetes.io/master=true 2h If you want to let it works on node, you can edit deamonset manually. it works. nodeSelector: node-role.kubernetes.io/compute: "true" openshift v3.11.98 openshift-ansible-3.11.98-1.git.0.3cfa7c3.el7.noarch Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:1605 |