Bug 203923
Summary: | HTTP byte range support is not complete | ||
---|---|---|---|
Product: | [Retired] Red Hat Network | Reporter: | James Bowes <jbowes> |
Component: | RHN/Backend | Assignee: | Bryan Kearney <bkearney> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Beth Nackashi <bnackash> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rhn410 | CC: | bkearney, rhn-bugs |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | RHN415 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-11-09 20:36:03 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: | 189170 |
Description
James Bowes
2006-08-24 15:10:14 UTC
Moving to rhn415-must. A fix exists in 415 now. For testing, I would suggest making sure that there are no regressions around up2date and yum downloading rpms from RHN, ie make sure 'yum install zsh' and 'up2date zsh' work correctly. Testing the added behaviour is a little trickier, since we have no client code that does this. I did pretty extensive unit testing on the byte range module, however. Unit tests live in RELEASE-4.1/backend/server/byterangetests.py Well, this seems to look ok on webqa for yum and up2date. Not that I fully understood what the original issue was, exactly, or anything. moving from VERIFIED to RELEASE_PENDING since stage push is complete closing -- current release. RHN415 is now in production. |