Bad md5 hash for package
Bug #1343313 reported by
Davanum Srinivas (DIMS)
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Core Infrastructure |
Triaged
|
Medium
|
Unassigned | ||
| OpenStack-Gate |
Invalid
|
Medium
|
Unassigned | ||
Bug Description
Example URL:
http://
14 hits in last 48 hours for logstash query:
message:"Bad md5 hash for package" AND filename:
Revision history for this message
| Clark Boylan (cboylan) wrote | #1 |
| Changed in openstack-ci: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Related fix proposed to elastic-recheck (master) | #2 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Related fix merged to elastic-recheck (master) | #3 |
| Changed in openstack-gate: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
Revision history for this message
| Matt Riedemann (mriedem) wrote | #4 |
| Changed in openstack-gate: | |
| status: | Triaged → Invalid |
To post a comment you must log in.
This is/was probably due to an incomplete bandersnatch sync. Bandersnatch should fix itself on the next run, but we can probably make it fail more gracefully when it notices md5sums don't match.
Its also possible that there were network bit flips and the md5sum check saved us from all kinds of nastyness. If that is the case I don't think there is much we can do about this bug.