[Pulp-list] Version 2.8 bug 1749 and production usage of Pulp
vaclav.adamec at suchy-zleb.cz
Wed Mar 23 17:02:36 UTC 2016
With completely fresh installation it is ok, simple upgrade from latest GA
2.7 to 2.8 + database update and restart didn't help. Data validation tool
wasn't used, but I can try it (if it's valuable for you).
On Wed, Mar 23, 2016 at 3:23 PM, Brian Bouterse <bbouters at redhat.com> wrote:
> Hi Vaclav,
> The bug #1749 was fixed in the 2.8.0 Pulp release. What version of Pulp
> are you running? Also we don't support upgrading from one beta to
> another. Did you upgrade your system directly from a GA release to
> another GA release?
> Did you run the pre-upgrade data validation tool? What results did it
> show? That tool can help identify data quality issues which sounds like
> what you are experiencing. I believe you can run it post-upgrade too and
> still get information about your problem from it.
> If you are running 2.8.0 and are still having issues, consider getting
> on #pulp on freenode and asking more in there.
> On 03/21/2016 03:21 AM, Vaclav Adamec wrote:
> > Hi,
> > I still hitting this bug https://pulp.plan.io/issues/1749 and unable to
> > use latest version. And seems that it's not critical for anybody else
> > than me :-)
> > So I'm a quite curious is there anybody else who use Pulp for Centos6
> > consumers ? How many users really use Pulp ? is it stable enough to use
> > it for production systems ?
> > Vasek
> > _______________________________________________
> > Pulp-list mailing list
> > Pulp-list at redhat.com
> > https://www.redhat.com/mailman/listinfo/pulp-list
> Pulp-list mailing list
> Pulp-list at redhat.com
-- May the fox be with you ...
) ) /\_/\
( \ /
" " " "
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pulp-list