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

dhcp-daemon pods have priority: 0 and no priority class

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • 4.15.z
    • 4.12
    • Networking / multus
    • None
    • Moderate
    • No
    • False
    • Hide

      None

      Show
      None

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

      If these pods are evicted, they loose all knowlage of exsisting dhcp leases, and any pods using dhcp ipam will fail to renew the dhcp lease. even after the pod is re-created.

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

      How reproducible:

      Steps to Reproduce:

          1. use a NAD with ipam: dhcp.
    2. delete the dhcp deamon pod on the smae node as your workload.
    3. observe the lease expire on dhcp server / get reissued to a different pod causing network outage from duplicate addresses.

      Actual results:

      dhcp-daemon

      Expected results:

      dhcp-daemon pod does not get evicted before workloads. because of system-node-critical

      Additional info:

      All other multus components system-node-critical 
  priority: 2000001000
  priorityClassName: system-node-critical

              dosmith Douglas Smith
              openshift-crt-jira-prow OpenShift Prow Bot
              Weibin Liang Weibin Liang
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: