matching centos and fedora hashes, however tripleo-ci-testing pin fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
Unassigned |
Bug Description
We have matching centos and fedora hashes however we get this error:
2019-01-08 22:47:25.483706 | TASK [Promote consistent to tripleo-ci-testing for fedora repo if an equivalent exists]
2019-01-08 22:47:25.086783 | rdo-centos-7 | Looking in indexes: http://
2019-01-08 22:47:25.265637 | rdo-centos-7 | Requirement already up-to-date: dlrnapi_client in ./dlrnapi_
2019-01-08 22:47:25.302079 | rdo-centos-7 | Requirement already up-to-date: shyaml in ./dlrnapi_
2019-01-08 22:47:25.309092 | rdo-centos-7 | Requirement already satisfied, skipping upgrade: six>=1.10 in ./dlrnapi_
2019-01-08 22:47:25.311416 | rdo-centos-7 | Requirement already satisfied, skipping upgrade: urllib3>=1.15.1 in ./dlrnapi_
2019-01-08 22:47:25.325737 | rdo-centos-7 | Requirement already satisfied, skipping upgrade: setuptools>=21.0.0 in ./dlrnapi_
2019-01-08 22:47:25.331780 | rdo-centos-7 | Requirement already satisfied, skipping upgrade: certifi>=14.05.14 in ./dlrnapi_
2019-01-08 22:47:25.334027 | rdo-centos-7 | Requirement already satisfied, skipping upgrade: python-
2019-01-08 22:47:25.337730 | rdo-centos-7 | Requirement already satisfied, skipping upgrade: pyyaml in ./dlrnapi_
2019-01-08 22:47:29.998642 | rdo-centos-7 | d71c8b4aaafda38
2019-01-08 22:47:31.013064 | rdo-centos-7 | ERROR
2019-01-08 22:47:31.013305 | rdo-centos-7 | {
2019-01-08 22:47:31.013467 | rdo-centos-7 | "delta": "0:00:05.250789",
2019-01-08 22:47:31.013591 | rdo-centos-7 | "end": "2019-01-08 22:47:29.999180",
2019-01-08 22:47:31.013668 | rdo-centos-7 | "msg": "non-zero return code",
2019-01-08 22:47:31.013739 | rdo-centos-7 | "rc": 1,
2019-01-08 22:47:31.013795 | rdo-centos-7 | "start": "2019-01-08 22:47:24.748391"
2019-01-08 22:47:31.013848 | rdo-centos-7 | }
2019-01-08 22:47:31.026889 |
2019-01-08 22:47:31.026998 | PLAY RECAP
Changed in tripleo: | |
status: | Fix Committed → Fix Released |
Ok so this difference mentioned in screenshots(lag between building same package) is expected with the approach used(matching 'consistent' hashes for Fedora and CentOS) because Fedora and CentOS dlrn builder are independent so can differ in timing in building packages.
I think we can skip(or atleast not FAIL the promotion- consistent- to-tripleo- ci-testing job) the check(comparing hashes), run both CentOS/Fedora promotion jobs, promote CentOS as usual, promote Fedora only if hash matches. In this approach Fedora might lag behind CentOS hash.