Hi Chis, we've never had pulp beta (or katello beta/RCs etc) installed on this server - it is purely production. I can confirm the file you linked to ( https://github.com/pulp/pulp_rpm/pull/900/files) does seem to be what my system has. The system is also now at pulp 2.8.6. Is there any way for me to confirm that the database is at the correct version?
Thanks :-) Dylan On Tuesday, August 30, 2016 at 12:57:36 AM UTC+12, Chris Duryee wrote: > > > > On 08/29/2016 07:50 AM, Chris Duryee wrote: > > > > > > On 08/29/2016 04:28 AM, Dylan Baars wrote: > >> Hi all > >> > >> Anyone have any ideas? We can't promote any red hat repos at the moment > >> > >> Thanks! > >> > > > > The issue is likely: > > > > pulp.server.managers.repo.unit_association:ERROR: (4160-00704) > > PulpCodedException: Content import of > > > /var/lib/pulp/content/units/yum_repo_metadata_file/3f/07e460b4eaf0910dc60e6c183373c7c61fa7f95626c6cd0888f64ae62d2050/productid.gz > > > > failed - must be an existing file. > > > > I remember this error but not the solution, I reached out to the Pulp > > team via #pulp to see if they know more. > > > > It looks like you hit https://pulp.plan.io/issues/1944 > <https://www.google.com/url?q=https%3A%2F%2Fpulp.plan.io%2Fissues%2F1944&sa=D&sntz=1&usg=AFQjCNHi3k7hRBn1K75M1qzFhHgwZJFUDg>, > > which should be > fixed in Pulp 2.8.5 and newer. > > Your pulp-manage-db output says "Migration to > pulp_rpm.plugins.migrations version 32 complete." which would include > https://github.com/pulp/pulp_rpm/pull/900/files, which should have fixed > this issue. > > Did you install a beta version of Pulp at any point on this system? > -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
