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

openstack/hypershift: kubelet can't start

XMLWordPrintable

    • None
    • ShiftStack Sprint 260
    • 1
    • False
    • Hide

      None

      Show
      None
    • Release Note Not Required
    • In Progress

      Description of problem:

      We added the following to openstack-kubelet-nodename.service: https://github.com/openshift/machine-config-operator/pull/4570
      
      But wait-for-br-ex-up.service is disabled, so doesn't normally do anything. This is why it doesn't break anything on other platforms, even though it's never going to work the way we are currently configuring workers for HCP. However, this Wants directive enables it when openstack-kubelet-nodename is added to the systemd transaction, so adding it broke us.
      
      "Wants" adds it to the transaction and it hangs. If it failed it would be fine, but it doesn't. It also adds a RequiredBy on node-valid-hostname.
      
      "br-ex" is up but it doesn't matter because that's not what it's testing. It's testing that /run/nodeip-configuration/br-ex-up  exists, which it won't because it's written by /etc/NetworkManager/dispatcher.d/30-resolv-prepender, which is empty.

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

      4.18  

            emacchi@redhat.com Emilien Macchi
            emacchi@redhat.com Emilien Macchi
            Itshak Brown Itshak Brown
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: