Skip to content
This repository has been archived by the owner on Jan 30, 2024. It is now read-only.

pulp_webserver does not always configure nginx/apache to connect to loopback API/Content #1239

Closed
mikedep333 opened this issue Jul 8, 2022 · 0 comments · Fixed by #1240
Closed

Comments

@mikedep333
Copy link
Member

The following task enables nginx/apache to connect to API/Content on the backend on the same host:
pulp_webserver : Set httpd_can_network_connect flag on and keep it persistent across reboots

However, ever since eaf30ed was implemented, it is often skipped accidentally.

mikedep333 added a commit to mikedep333/pulp_installer that referenced this issue Jul 8, 2022
to connect to ports 24816 or 24817.

fixes: pulp#1239
mikedep333 added a commit to mikedep333/pulp_installer that referenced this issue Jul 8, 2022
to connect to ports 24816 or 24817.

fixes: pulp#1239
mikedep333 added a commit to mikedep333/pulp_installer that referenced this issue Jul 8, 2022
to connect to ports 24816 or 24817.

Fixes a regression from eaf30ed

fixes: pulp#1239
mikedep333 added a commit that referenced this issue Jul 11, 2022
to connect to ports 24816 or 24817.

Fixes a regression from eaf30ed

fixes: #1239
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant