I put a comment for the search issue https://pulp.plan.io/issues/2620#note-8 Any ideas which option is better and what is the best way to fix it are very welcome.
I found two other potential blockers: - sync issue https://pulp.plan.io/issues/2622, I've fixed it, PR needs review. Jeff, I think you are the best person to look at it. - errata publish performance issue https://pulp.plan.io/issues/2623 Sean, it's our recent changes, I think it is better for you or me to take a look at it. Tanya On Tue, Mar 7, 2017 at 12:07 AM, Sean Myers <sean.my...@redhat.com> wrote: > A few issues cropped up today as potential blockers for the > Beta release of 2.12.2. As far as I can tell, only this issue > remains as a potential blocker: > > https://pulp.plan.io/issues/2620 > > As seen in comment #7, I've marked it as a blocker in a > "presumed guilty until proven innocent" fashion, with the > expectation that we will triage it during tomorrow's normal > triage session and deal with it accordingly. > > Tanya's got a lead on what's going wrong, so we should have > more information to work with before triage. > > If there are other potential blockers to 2.12.2, please get > them filed in Redmine. Thanks! > > > _______________________________________________ > Pulp-dev mailing list > Pulp-dev@redhat.com > https://www.redhat.com/mailman/listinfo/pulp-dev > >
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev
