Bug 1687803 - [3.10] sync-pod tried to override the hostname
Summary: [3.10] sync-pod tried to override the hostname
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.10.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 3.10.z
Assignee: Scott Dodson
QA Contact: Weihua Meng
URL:
Whiteboard:
Depends On: 1657769
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-12 12:34 UTC by Scott Dodson
Modified: 2019-04-09 23:40 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
If an override hostname hadn't been set the sync script generated an error in the sync logs. That error message is no longer present in situations where /etc/sysconfig/KUBELET_HOSTNAME_OVERRIDE is not present.
Clone Of: 1657769
Environment:
Last Closed: 2019-04-09 23:40:44 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:0620 0 None None None 2019-04-09 23:40:47 UTC

Comment 1 Scott Dodson 2019-03-12 12:35:10 UTC 
https://github.com/openshift/openshift-ansible/pull/11339 release-3.10 backport
Comment 3 Weihua Meng 2019-03-21 03:19:16 UTC 
Fixed.

openshift-ansible-3.10.127-1.git.0.131da09.el7


[root@ip-172-18-4-60 ~]# oc logs -n openshift-node sync-8x5rv
info: Configuration changed, restarting kubelet
I0321 02:58:39.084140   13346 feature_gate.go:190] feature gates: map[RotateKubeletClientCertificate:true RotateKubeletServerCertificate:true]
info: Applying node labels role=node registry=enabled router=enabled 
node "ip-172-18-9-88.ec2.internal" labeled
node "ip-172-18-9-88.ec2.internal" annotated
node "ip-172-18-9-88.ec2.internal" annotated
node "ip-172-18-9-88.ec2.internal" annotated


Kernel Version: 3.10.0-957.10.1.el7.x86_64
Operating System: Red Hat Enterprise Linux Server 7.6 (Maipo)
Comment 5 errata-xmlrpc 2019-04-09 23:40:44 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:0620
Note You need to log in before you can comment on or make changes to this bug.