Yum required RHN to support http requests for byte ranges. We implemented this,
but not for the full spec. As a result, someone, somewhere is requesting byte
ranges in a way we do not support. Before, we would have returned The entire
file. Now, we error.
We need support for the full spec.
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.