can't fetch yum contents over https after deploying pulp3
both pulp3 and pulp2 want to 'own' /pulp/content/ in their current apache configurations. In pulp2 /pulp/content was never used directly but the existing type specific paths (/pulp/iso, /pulp/repos) redirect to /pulp/content for pulp2.
my suggestion is to change /pulp/content within pulp2 to something else like /pulp2/content/. Since it is not user facing, we can change it to whatever we want.
#4 Updated by Justin Sherrill 7 months ago
- Status changed from Ready For Testing to Closed
Applied in changeset puppet-pulp|f848c41805cefe05e141255f555d2629dd692a47.