Description of problem: spacewalk-clone-by-date is not correctly cloning errata that has been UPDATED into our downstream channels. When issuing the command: [root@*****]$ spacewalk-clone-by-date --config=someconfigfile.config -d \ 2014-09-30 it is skipping the bash errata that was updated on 30-Sep-2014. Doing some more testing, I realized that if I change the to-date to 16-Oct it will clone everything that has been released, but NOT the bash errata. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: Using spacewalk-clone-by-date 1. clone RH channel to 2014-09-26 (this will clone the initial bash errata released on that day) 2. clone RH channel to 2014-09-30 3. Check private channels Actual results: The bash errata is still the previous 09/26/2014 Expected results: The updated errata, released on the 30th would be cloned to private channels Additional info: It appears that spacewalk-clone-by-date is checking the issue date of the errata, and NOT the updated date. In the case of RHSA-2014:1306, which was originally issued on 09/26 and updated on 09/30, it was seeing the errata in the channel and skipping it, not cloning the update. Before and after the clone, both the issue date and the updated date were 09/26
I feel this already has been resolved by Bug 905259. Closing as duplicate. *** This bug has been marked as a duplicate of bug 905259 ***