Comment 3 for bug 1714905

I did a little bit of research and I found out that on stable/pike, the upgrade job was correctly deploying Ocata on BM and then upgrade to Pike on containers but the version of TripleO packages on Pike was too old (11 days).

I figured that tripleo-quickstart wasn't deploying current-pike repo, so I'm trying to add it here: https://review.openstack.org/500671 and test it here https://review.openstack.org/500625

On another note, more or less related but we had a successful upgrade on stable/pike yesterday:
http://logs.openstack.org/45/500145/3/check/gate-tripleo-ci-centos-7-containers-multinode-upgrades-nv/9392d26/console.html#_2017-09-04_04_15_27_962324

The main problem now is to make it work on scenarios, which my patch on quickstart might help.
At least it will help to get latest tripleo commits.