[Upgrade test] "Addon update should propagate add-on file changes" failing in ci-kubernetes-e2e-gce-1.4-1.5-upgrade-cluster

[saad-ali]

Test has been failing 100% of the time in ci-kubernetes-e2e-gce-1.4-1.5-upgrade-cluster. Sample failure: link.

Based on spreadsheet tracking 1.5 upgrade test failures created by @krousey.

[MrHohn]

Paste my same comment from #35600:

This test always failed in 1.5 upgrade builds. An example as this :https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-gce-1.4-1.5-upgrade-cluster/12/.

Checked logs and found we were actually running the old version Addon update e2e test(probably depends on the original version?) after upgrade. But because Addon Manager is upgraded to a newer version in 1.5 and does not take care of resources in non kube-system namespace anymore, this test must failed without the necessary test code changes in #36008.

May triage it as a non blocker

[dims]

@saad-ali Is it appropriate to move this to the next milestone or clear the 1.5 milestone? (and remove the non-release-blocker tag as well)