+++ This bug was initially created as a clone of Bug #1814357 +++ Description of problem: The router metrics and header tests can crash when migrating from an old version (e.g. 4.1) that has an un-migrated platform status field. https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade-4.1-to-4.2-to-4.3-to-4.4-nightly/22 Longer term the field should probably be backfilled/migrated during an upgrade. For now, code needs to account for the possibility of a nil platform status and fall back to the old deprecated field. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: --- Additional comment from errata-xmlrpc on 2020-03-18 02:22:38 UTC --- This bug has been added to advisory RHBA-2020:51809 by OpenShift Release Team Bot (ocp-build/buildvm.openshift.eng.bos.redhat.com) --- Additional comment from errata-xmlrpc on 2020-03-18 02:22:39 UTC --- Bug report changed to ON_QA status by Errata System. A QE request has been submitted for advisory RHBA-2020:51809-01 https://errata.devel.redhat.com/advisory/51809 --- Additional comment from OpenShift Automated Release Tooling on 2020-03-19 00:40:30 UTC --- Elliott changed bug status from ('MODIFIED',) to ON_QA.
Note the patch for this has been in-flight for 6 days, blocked on QE. https://github.com/openshift/origin/pull/24721
Checked latest e2e test in https://testgrid.k8s.io/redhat-openshift-ocp-release-4.4-informing#release-openshift-origin-installer-e2e-aws-upgrade-4.1-to-4.2-to-4.3-to-4.4-nightly didn't see the issue "invalid memory address or nil pointer dereference" any more.
*** This bug has been marked as a duplicate of bug 1830130 ***