Project

General

Profile

Actions

Bug #16645

closed

Initial capsule syncs of new repositories does not use https for syncing

Added by Justin Sherrill over 7 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Category:
Foreman Proxy Content
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1378158
Description of problem:

When syncing a repository for the first time it appears that http is used for syncing rather than https. Subsequent syncs will use https.

This only affect repositories that are exposed via http such as kickstart or custom repositories.

Version-Release number of selected component (if applicable):
6.2.2

How reproducible:
Always

Steps to Reproduce:
1. Create a custom repository
2. Tail /var/log/httpd/foreman_access.log
3. With a capsule associated to library, sync the capsule

Actual results:

You'll see requests for this repository made to the foreman_access.log instead of the foreman-ssl_access_ssl.log

Expected results:

No requests are made via http and foreman_access.log shows no requests

Additional info:

Actions #1

Updated by The Foreman Bot over 7 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/6337 added
Actions #2

Updated by Justin Sherrill over 7 years ago

  • Target version set to 129
Actions #3

Updated by Justin Sherrill over 7 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #4

Updated by Justin Sherrill over 7 years ago

  • translation missing: en.field_release set to 162
Actions

Also available in: Atom PDF