Description of problem: When importing some channel dumps from a directory, satellite-sync will mark the channels *not* in the dump as end-of-service even though they're not. For example, download and prepare the first channel dump iso for the ppc version of RHEL 3 and do a --list-channels against the directory. It will list RHEL 4 as being end-of-service when it's not. If you place the dumped file for the ppc version of RHEL 4 into directory you placed RHEL 3 into and rerun satellite-sync with --list-channels, it no longer lists the channels as end-of-service. It looks as though the logic that controls whether a channel is considered to be end-of-service is in the compute method of the RequestedChannels class in req_channels.py.
So this is only when importing channel dumps from the filesystem, and only when the expected channels don't exist in that directory? Basically trying to understand if this is serious enough to warrant blocking 406... Moving to rhn410-must in the interim.
Yep, seems to only be a problem when importing channel dumps from the filesystem. When I doing a regular --list-channels against hosted the RHEL 4 channels are not marked end-of-service.
Fixed in svn. I changed satellite-sync to not list the end-of-service channel when the --mount-point option is being used. Test Plan: 1. On a satellite, wget/curl a channel dump and mount the iso. 2. Sync another channel not included in the channel dump. satellite-sync -c<channel-label> 3. Use satellite-sync to list the channels included in the channel dump. It should not list the channel you synced in step 2 as end-of-service. satellite-sync --list-channels --mount-point=<channel-dump-directory>
Changing state to ON_QA after QA push.
closing - currentrelease