Upgrade jobs looking for wrong hash
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Incomplete
|
Medium
|
Unassigned |
Bug Description
Noticed at:
2021-02-24 03:27:34 | + export DLRN_PATH_
2021-02-24 03:27:34 | + DLRN_PATH_
2021-02-24 03:27:34 | + export DLRN_PATH_
2021-02-24 03:27:34 | + DLRN_PATH_
2021-02-24 03:27:34 | ++ curl --silent https:/
2021-02-24 03:27:34 | ++ grep baseurl
2021-02-24 03:27:34 | ++ grep component/tripleo
2021-02-24 03:27:34 | ++ cut -d= -f2
2021-02-24 03:27:34 | + rdo_dlrn=
2021-02-24 03:27:34 | + [[ -z '' ]]
2021-02-24 03:27:34 | + echo 'Failed to parse dlrn hash'
It seems to be looking from dlrn hash not in ussuri. I can see it in victoria[1]. Probably these upgrade jobs are not doing the right thing.
Changed in tripleo: | |
milestone: | none → wallaby-3 |
Changed in tripleo: | |
milestone: | wallaby-3 → wallaby-rc1 |
Changed in tripleo: | |
milestone: | wallaby-rc1 → xena-1 |
Changed in tripleo: | |
milestone: | xena-1 → xena-2 |
Changed in tripleo: | |
milestone: | xena-2 → xena-3 |
Changing the priority as it seems to be one time failure with possibly ansible magic;)