No the one that the pulpcore-api service isn’t started and when trying to
start manually I get that error for the jsquery not found
Kind regards
On Thu, 15 Apr 2021 at 07:50 David Davis wrote:
> When you say you run the playbook again and got the same error, which
> error do you mean? The "No
When you say you run the playbook again and got the same error, which error
do you mean? The "No such file or directory:
'/var/lib/pulp/assets/rest_framework/js/jquery-3.4.1.min.js'" one?
David
On Thu, Apr 15, 2021 at 4:43 AM Eric VS wrote:
> Hey Matthias,
>
> I ran the pulpcore-manager
Hey Matthias,
I ran the pulpcore-manager collectstatic with success, then the playbook
again but got the same error. This is the full list of commands for
pulpcore-manager, any others I would need to run?
Last login: Thu Apr 15 16:23:00 CST 2021 on pts/0
[root@tw-stg-man01 ~]# export
pulp_deb versions 2.9.1 [0], 2.10.1 [1], and 2.11.1 [2] have been released.
These releases all fix a bug that was preventing synchronization of
repositories containing translation files (as well as the synchronization of
the translation files themselves).
See: https://pulp.plan.io/issues/8410,
Yeah, i can see how that happened. There may be some triggers from the
previous run that aren't triggered now, because "nothing changed" according
to ansible.
This one should be: pulpcore-manager collect-static (or very similar)
When you just run pulpcore-manager you get a list where you should be
Hi Matthias,
I did try to run that command but thought it was failing due to the last
error.
Unfortunately, when I just tried running the playbook again I ran into the
next error :-)
TASK [pulp.pulp_installer.pulp_health_check : Checking Pulp services]
There is the clue: Run 'pulpcore-manager handle-artifact-checksums' first
to unset forbidden checksums.
Pulp dropped to support md5 and sha1 by default. And there is a manual step
that should bring the database in the right place.
Try rerunning the ansible playbook afterwards.
However i thought
