periodic jobs delorean reporting broken when using featureset_override['dlrn_hash_tag']
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
Marios Andreou |
Bug Description
As seen during testing at [1] when running a periodic job for a particular delorean hash (i.e. override with featureset_
2021-06-22 16:27:34.055732 | primary | TASK [container-prep : echo container_build_id] *******
2021-06-22 16:27:34.055765 | primary | Tuesday 22 June 2021 16:27:34 +0000 (0:00:00.031) 0:01:44.634 **********
2021-06-22 16:27:34.071185 | primary | ok: [undercloud] => {
2021-06-22 16:27:34.071227 | primary | "container_
2021-06-22 16:27:34.071239 | primary | }
but the hash reported by delorean is instead pulled from the current value of tripleo-ci-testing:
2021-06-22 17:19:29.990691 | primary | + dlrnapi --url https:/
2021-06-22 17:19:32.053382 | primary | {
2021-06-22 17:19:32.053521 | primary | "aggregate_hash": "8067ada389f4f0
The problem comes from [3] where hash_info is populated for delorean reporting. In particular, in the get_hash role there is no attempt to use the passed delorean hash, instead directly taking {{ promote_source }}/delorean.
To be clear this is a bug against tripleo-ci ruck|rover tooling and should not impact regular users. However being able to override a hash is an important part of the ruck|rover toolbox and needs to be fixed.
[1] https:/
[2] https:/
[3] https:/
[4] https:/
I posted a test fix at [1] so when featureset_override is provided with a delorean hash it is used directly for the md5.
I am trying to test with [2] except it isn't included with depends-on. It is ci-config and besides the fact that delorean probably can't build the ci-config repo (? I cannot see any related distgit @ https:/ /github. com/rdo- packages? q=ci-config& type=&language= &sort= ), the conditional fails there [3] because zuul.override_repo is stable/ussuri for the periodic- tripleo- ci-centos- 8-standalone- on-multinode- ipa-ussuri job running in my testproject e.g. logs @ [4]
Not sure how to proceed... I have considered if we can enhance build-test-packages to apply changes from git directly to a checkout? Even if we do want to do that I don't think it is somehting that can be done in this ruck|rover cycle and needs discussion etc.
We could try merging https:/ /review. rdoproject. org/r/c/ rdo-infra/ ci-config/ +/34275 - the conditional there means it only happens when user specifies the hash. It might fix the issue, or we may need something further which we can iterate for.
[1] https:/ /review. rdoproject. org/r/c/ rdo-infra/ ci-config/ +/34275/ 1/ci-scripts/ infra-setup/ roles/get_ hash/tasks/ get_hash. yaml /review. rdoproject. org/r/c/ testproject/ +/34256 /opendev. org/openstack/ tripleo- quickstart- extras/ src/commit/ e423bb068a96ed9 19ead08226f9447 b2cdfc0332/ roles/build- test-packages/ tasks/main. yml#L200 /logserver. rdoproject. org/56/ 34256/3/ check/periodic- tripleo- ci-centos- 8-standalone- on-multinode- ipa-ussuri/ 7385797/ zuul-info/ inventory. yaml
[2] https:/
[3] https:/
[4] https:/