Uploaded image for project: 'OpenShift Core Networking'
  1. OpenShift Core Networking
  2. CORENET-3414

investigate if larger instances for cluster nodes improve upgrade results

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • None
    • Future Sustainability
    • False
    • None
    • False
    • 3
    • None
    • None
    • SDN Sprint 205

      There is a little background in https://bugzilla.redhat.com/show_bug.cgi?id=1981872

      essentially, there are always some failures in ovn upgrade around i/o timeouts
      and what seems like connectivity issues. two things I've noticed:

      1) we seem to always have ovsdb and/or openvswitch core dumps in our upgrade
      jobs. a story for this work is here

      2) sometimes there are failures in some alerts test case that indicate high cpu
      usage alerts.

      This story is for #2 to see if maybe we are pegging the CPUs and possibly
      throwing more resources at the cluster we will see better results in the upgrade
      job.

        1. m5.2xlarge.png
          m5.2xlarge.png
          208 kB
        2. m5.xlarge.png
          m5.xlarge.png
          292 kB

              jluhrsen Jamo Luhrsen
              jluhrsen Jamo Luhrsen
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: