Project

General

Profile

Bug #16645

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

Added by Justin Sherrill about 4 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Justin Sherrill
Category:
Foreman Proxy Content
Target version:
Katello 3.2.0
Difficulty:
Triaged:
Yes
Bugzilla link:
1378158
Pull request:
https://github.com/Katello/katello/pull/6337
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:

Associated revisions

Revision 4b677d8d (diff)
Added by Justin Sherrill about 4 years ago

Fixes #16645 - force https for initial capsule sync

History

#1 Updated by The Foreman Bot about 4 years ago

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

#2 Updated by Justin Sherrill about 4 years ago

  • Target version set to 129

#3 Updated by Justin Sherrill about 4 years ago

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

#4 Updated by Justin Sherrill about 4 years ago

  • Legacy Backlogs Release (now unused) set to 162

Also available in: Atom PDF