To fix this more legitimately, as a workaround, run foreman-installer --foreman-proxy-content-pulpcore-cache-enabled=true
. We’ve identified the issue as a missing installer migration, so it’ll be fixed up soon.
2 Likes