Uploaded image for project: 'OCP Technical Release Team'
  1. OCP Technical Release Team
  2. TRT-553

Investigate single node disruption

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • None
    • False
    • None
    • False

      Given the update in https://github.com/openshift/origin/pull/27420 and the graphs in https://datastudio.google.com/reporting/26007bde-88c8-44dd-8fb9-4f5e41dfb0ce/page/p_i6fa5cr1mc, Azure disruption is out of control and looks to have been for quite some time, as far back as we have data.

      https://datastudio.google.com/s/ogGapAS61iY looks to show a regression when upgrading 4.11, happened around June 6th. This may also imply it was always present in 4.12 when we forked, thus why we don't see any regression in those charts.

      Be wary Azure didn't just change something, perhaps check graphs for 4.10.

      This might be a good time for https://github.com/mfojtik/ocp-what-merged to see what happened around that time across all repos, but it may not catch rhcos work which would be a very big possibility here.

            kenzhang@redhat.com Ken Zhang
            rhn-engineering-dgoodwin Devan Goodwin
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: