ocata upgrade CI is broken

[Steven Hardy]

https://review.openstack.org/#/c/465914/ is an example of a failing upgrade job, which is voting on ocata.

It's failing because we landed this:

https://review.openstack.org/#/c/464667/

Which is needed to fix the j2 rendered references, but deployed-server-bootstrap-environment-centos.yaml doesn't currently exist on newton

If possible the simplest fix here is to backport deployed-server-bootstrap-environment-centos.yaml to newton but waiting on feedback from slagle as to whether that's reasonable.

[James Slagle (james-slagle)]

think the root cause here is:

09:45 <@slagle> shardy: alright, i see the issue now. that envrionment (deployed-server-bootstrap-environment-centos.yaml) shouldn't even be getting added when deploying newton, but due to how "multinode-upgrades" is parsed
                in toci_gate_test-orig, it gets added to deploy args before we reset STABLE_RELEASE to newton

09:50 <@slagle> shardy: we could do something like check $UPGRADE_RELEASE there

[Steven Hardy (shardy)]

Discussion with slagle on IRC indicates that we shouldn't be including the deployed-server-bootstrap-environment-centos.yaml on this branch, but it gets mistakenly included due to ordering issues in toci_gate_test-orig

[Steven Hardy (shardy)]

https://review.openstack.org/#/c/466042/ landed which should fix the issue described in this bug, although ocata upgrade CI is still broken for some other reason (not yet investigated)

[Steven Hardy (shardy)]

https://review.openstack.org/#/c/465914/ shows CI is now working so closing this