Just discovered that I had the download policy for repos is set to 'on
demand', which is appears to be the default. I'm guessing that this changed
from pulp 2.91-> 2.93. But in any event, we require the repos to be stored
locally, so setting the policy to 'immediate' fixed this issue.
On Friday, December 23, 2016 at 8:44:55 AM UTC-5, Darren Wah wrote:
>
> Hi all,
>
> I'm using Foreman 1.13.3 with Puppet 4 and Pulp 2.9.3 built on CentOS 7.3.
> When I create a repo and sync it, I'm finding that with Pulp 2.9.3 the sync
> will complete successfully (no errors in production.log), but nothing will
> be published - /var/lib/pulp/content is not populated (or even created) and
> all links created in
> /var/lib/pulp/published/yum/http{,s}/repos/<Organization>/Library/custom/<Product>/<Repository>
>
> are dead. I had previously used Pulp 2.9.1 and was able to publish repos,
> however 2.9.1 was subject to http://projects.theforeman.org/issues/16877,
> and I needed to upgrade.
>
> My Foreman instance was built with:
>
> foreman-installer --scenario "katello" --foreman-proxy-dns "true"
> --foreman-proxy-dns-interface "enp0s8" --foreman-proxy-dns-forwarders
> "192.168.50.254" --foreman-proxy-dns-reverse "50.168.192"
> --foreman-proxy-tftp "true" --foreman-proxy-tftp-servername "foreman.smmtt"
> --foreman-proxy-puppet "true" --foreman-proxy-puppetca "true"
> --foreman-admin-username "admin" --foreman-admin-password "<password>"
> --foreman-puppet-home "/opt/puppetlabs/server/data/puppetserver"
>
>
> Any help would be greatly appreciated.
>
--
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.
