Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-34716

kubelet service is unable to parse the "kubelet_node_name" when multiple domain name used

XMLWordPrintable

    • No
    • CLOUD Sprint 254, CLOUD Sprint 255
    • 2
    • False
    • Hide

      None

      Show
      None
    • Hide
      Node name fetching logic on the host relies on the returned hostname from the AWS metadata service. When multiple domains are configured for a VPC DHCP option, this hostname may return multiple values. The logic was not previously accounting for multiple values, and crashed as it returned a node name containing a space.
      The logic is now updated to use only the first returned hostname as the node name.
      Show
      Node name fetching logic on the host relies on the returned hostname from the AWS metadata service. When multiple domains are configured for a VPC DHCP option, this hostname may return multiple values. The logic was not previously accounting for multiple values, and crashed as it returned a node name containing a space. The logic is now updated to use only the first returned hostname as the node name.
    • Bug Fix
    • In Progress

      This is a clone of issue OCPBUGS-33847. The following is the description of the original issue:
      —
      This is a clone of issue OCPBUGS-10498. The following is the description of the original issue:
      —
      Description of problem:

      The customer requires multiple domain names in their AWS VPCs DHCP option set which is to allow on-prem DNS(infoblox) lookups to work. 

The problem is that kubelet service is unable to parse the node name properly. 

~~~
hyperkube[2562]: Error: failed to run Kubelet: failed to create kubelet: could not initialize volume plugins for KubeletVolumePluginMgr: parse "http://example.compute.internal example.com:9001": invalid character " " in host name
~~~

/etc/systemd/system/kubelet.service.d/20-aws-node-name.conf
[Service]
Environment="KUBELET_NODE_NAME=ip-x-x-x-x.example.example test.example"
                                                         ^
                                                        space


The is customer is aware of this KCS article. If the cu follows what the KCS article says, it will break their DNS functionality. 

Kubelet fails to start on nodes during OCP 4.x IPI installation on AWS - Red Hat Customer Portal
https://access.redhat.com/solutions/6978959

      Version-Release number of selected component (if applicable):

       

      How reproducible:

      always

      Steps to Reproduce:

      1. Create/adding a node with multiple domain names
2. Add base domain to the DHCP option in the VPC setting
3.

      Actual results:

      kubelet is failing to start

      Expected results:

      should be able to add a worker node that has multiple domain names

      Additional info:

       

              joelspeed Joel Speed
              openshift-crt-jira-prow OpenShift Prow Bot
              Huali Liu Huali Liu
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: