centos-9 content provider jobs not starting
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
Unassigned |
Bug Description
Centos 9 content provider jobs are failing with retry_limit due to an issue with the upstream ansible-collections community.general git repository.
Affected jobs: https:/
Context from #opendev:
<ianw> Adding node request <NodeRequest 300-0017269841 ['centos-
<ianw> 2022-02-16 22:05:04,927 DEBUG zuul.nodepool: [e: 1a7616b0e3c7411
<ianw> 2022-02-16 22:05:04,884 DEBUG nodepool.
<ianw> nl04 fufilled the request, and it went to ovh-bhs1
<ianw> 2022-02-16 22:04:24,900 ERROR zuul.AnsibleJob: [e: 1a7616b0e3c7411
<ianw> on ze03 ... this might be a clue
<ianw> https:/
<ianw> 2022-02-16 22:04:24,900 ERROR zuul.AnsibleJob: ValueError: SHA b'01e50ed7dac6c
...
<clarkb> considering this seems to be somewhat widepsread I suspect this isn't a problem on our end but somethign we are managing to fetch from upstream (but we should confirm that)
<ianw> this must have run several times across executors you'd think
<ianw> yeah, what you said :)
<ianw> [iwienand@fedora19 community.general (main)]$ git show 01e50ed7dac6cd2
<ianw> fatal: bad object 01e50ed7dac6cd2
<clarkb> that is unfortunate for ansible, but I'm not sure we can do anything about it?
<clarkb> eg that should be fixed upstream
<ianw> i guess i will file an issue with ansible, i feel like github may have to get involved
Changed in tripleo: | |
status: | Triaged → Fix Released |
@Rafael is this still a blocker? I see CIX was moved to Done, if so this LP should be closed and/or Tag promotion-blocker removed.