Bug 1686587
| Summary: | Task set_loopback_context.yml sets context.user to the wrong name for openshift-master.kubeconfig | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Russell Teague <rteague> |
| Component: | Installer | Assignee: | Russell Teague <rteague> |
| Installer sub component: | openshift-ansible | QA Contact: | ge liu <geliu> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | unspecified | ||
| Priority: | unspecified | CC: | gpei, jialiu, jmalde, rhowe, rteague |
| Version: | 3.9.0 | ||
| Target Milestone: | --- | ||
| Target Release: | 3.9.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
When a cluster is installed the username in the loopback kubeconfig
is equal to hostname of that local master. This changes the variable
to equal a value of what would originally be set.
|
Story Points: | --- |
| Clone Of: | 1675133 | Environment: | |
| Last Closed: | 2019-04-09 14:20:18 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1675133 | ||
| Bug Blocks: | 1686585 | ||
|
Comment 1
Russell Teague
2019-03-07 18:42:50 UTC
In build openshift-ansible-3.9.72-1 Verified with openshift-ansible-3.9.73-1.git.0.0b2bcaf.el7.noarch.rpm,
1. Install HA
2. change project
3. run instller playbook: deploy_cluster.yml(it will trigger the execution for set_loopback_context.yaml)
4. check the user hostname have not be changed:
- context:
cluster: qe-geliu39master-etcd-1:443
namespace: default
user: system:openshift-master/qe-geliu39master-etcd-1:443
name: default/qe-geliu39master-etcd-1:443/system:openshift-master
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:0619 |