Bug 1686587 - Task set_loopback_context.yml sets context.user to the wrong name for openshift-master.kubeconfig
Summary: Task set_loopback_context.yml sets context.user to the wrong name for openshi...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.9.z
Assignee: Russell Teague
QA Contact: ge liu
URL:
Whiteboard:
Depends On: 1675133
Blocks: 1686585
TreeView+ depends on / blocked
 
Reported: 2019-03-07 18:41 UTC by Russell Teague
Modified: 2019-04-09 14:20 UTC (History)
5 users (show)

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.
Clone Of: 1675133
Environment:
Last Closed: 2019-04-09 14:20:18 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:0619 0 None None None 2019-04-09 14:20:27 UTC

Comment 1 Russell Teague 2019-03-07 18:42:50 UTC
Merged: https://github.com/openshift/openshift-ansible/pull/11171

Comment 2 Russell Teague 2019-03-11 15:26:09 UTC
In build openshift-ansible-3.9.72-1

Comment 4 ge liu 2019-03-20 10:49:16 UTC
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

Comment 6 errata-xmlrpc 2019-04-09 14:20:18 UTC
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


Note You need to log in before you can comment on or make changes to this bug.