After recreating all of my repositories, I ran into the offset and metadata errors again today. I can confirm the metadata error isn't generated due to problems with upstream; the repository I last saw it on was local and during publish.
I don't know if this helps, or if it's just coincidence, but the metadata errors have only (today) been on repositories where the feed has a cert. My other repos (local, CentOS, EPEL) had the offset error. I'm usually able to successfully sync after recreating the repository, but not always. The new "pulp-admin tasks list" functionality was the main reason I upgraded, but I think I'm going to have to go back to 2.6.3 until things stabilize. Reece On 9/16/15, 2:56 PM, "Webb, Reece" <[email protected]> wrote: >Thanks Randy, the CDN/metadata errors aren't showing up right now, so maybe it >was just a temporary fluke. I successfully synced right before the upgrade to >2.7, so I assumed the worse. :) In any case, I'll keep an eye on it for the >next couple of days to make sure the error doesn't return. And if there's any >other info I can provide to help get the email issue resolved, please let me >know. > >Reece > > > > >On 9/16/15, 2:39 PM, "Randy Barlow" <[email protected]> wrote: > >>Webb, Reece wrote: >>> Thanks, I upgraded from 2.6.3. As I said in my last follow-up email, >>> recreating a repository allow it to successfully sync/publish. But now I'm >>> running into two other issues... email notification events don't work at >>> all. I've also run into an error retrieving metadata on seemingly random >>> repositories that I've tried recreating to workaround the offset error. I >>> can recreate the repository, but I receive the same error. I found one bug >>> report with this error that turned out to be a selinux issue, but I have >>> selinux disabled... not good. Logs below. >> >>Hi Reece, >> >>Apologies, I misread your earlier e-mail and I thought it said you had >>upgraded to 2.6.3, not from 2.6.3. I updated the bug report to reflect >>that now. >> >>As for the e-mail error - would you mind filing a bug about that? >> >>The CDN error is more surprising. Perhaps it is possible that the CDN >>really was missing that file for a bit? Can you confirm whether that >>error is repeatable? >> _______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
