Bug 116124
Summary: | up2date-4.3.11-2 gives traceback | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Bernd Bartmann <bernd.bartmann> |
Component: | up2date | Assignee: | Adrian Likins <alikins> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | byte, djuran |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-08-25 20:33:21 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 114961, 123268 |
Description
Bernd Bartmann
2004-02-18 14:18:29 UTC
Bernd, can you please check whether the problem persists with current up2date? I haven't seen the problem in the past two weeks. If I remember correctly it only occured when the Fedora mirror that I use was rsyncing to the Fedora master site. Not sure if it helps to report in that I dont see this on my test3 box. But if this is only viewable if there is a mirror syncing problem on the server side, I'm not really sure how many people can try to reproduce this. Does this really need to be a blocker? I don't see this on the latest up2date - up2date-4.3.17-1 - so this might have been a problem that disappeared with what was included in test1. I'm with Jef on this, does this really sound like a blocker? I still se this with up2date-4.3.19-1. Anyway, it's not quite straight forward to from this message deduce that the mirror is broken. |