repo-setup not working correctly during emit_release upgrade jobs.

[Sofer Athlan-Guyot]

Hi,

For repo-setup to work properly we need those variables:
 - dlrn_hash_tag_newest (rdo_dlrn becomes RDO_DLRN_REPO become delorean-current)
 - dlrn_hash (tripleo_drln becomes TRIPLEO_DLRN_REPO become delorean)
 - dlrn_hash_path (tripleo_dlrn ...)

They end up in the release file[1] to get the rdo_dlrn and the tripleo_dlrn.

emit_release mechanism sets up explicit variable for dlrn_hash for each release file in a for an "shell mapping table" in release.sh, but that let dlrn_hash_tag_newest uncovered.

As this fact is set with the cacheable attribute and it's run during standalone deployment, we end up consuming it (instead of recalculating it) during the upgrade.

So we get url like[2]:

    https://bit.ly/2BtN52W

which is 404 not found because the correct url associated with this hash is:

    https://bit.ly/2BtN52W

as can be seen in the standalone deployment repo-setup log there [3]

The fact that dlrn_hash is not recalculated because we already calculated it[4] make the process fails and we use the rocky hash in the master url.

This[5] was suggested as a workaround, but now as we understand the issue better, doesn't help.

[1] https://bit.ly/2BtN52W
[2] https://bit.ly/2BtN52W
[3] https://bit.ly/2BtN52W
[4] https://bit.ly/2BtN52W
[5] https://review.openstack.org/605369

[Cédric Jeanneret (cjeanner)]

Is it still valid?

[Sofer Athlan-Guyot (sofer-athlan-guyot)]

This has been fixed.