Bug 1109110 - unable to change repository urls of child channels to https in kickstart profile
Summary: unable to change repository urls of child channels to https in kickstart profile
Keywords:
Status: CLOSED EOL
Alias: None
Product: Spacewalk
Classification: Community
Component: Server
Version: 2.1
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Tomas Lestach
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space28
TreeView+ depends on / blocked
 
Reported: 2014-06-13 09:29 UTC by Andreas Schmechtig
Modified: 2018-04-20 12:21 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-11-23 15:26:54 UTC
Embargoed:


Attachments (Terms of Use)

Description Andreas Schmechtig 2014-06-13 09:29:34 UTC
Description of problem:
It is not possible (we don't find a way) to change the repository urls of child channels to https instead of http inside of a spacewalk managed kickstart profile.

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


How reproducible:


Steps to Reproduce:
1. Create a parent channel
2. Create some child channels
3. Create a kickstart profile in spacewalk
4. Change the url of the parent channel to https protocol by using Kickstart Details -> Advanced Options -> URL
5. Find no option to change the URL of child channel repository URLs
   e.g.
   repo --name=rhel-x86_64-server-epel-6 --baseurl=http://...


Actual results:
Kickstart Installation runs with https against the parent channel but additional components from child channels are tried to being installed with http access. This fails in a networking environment where only https is permitted through firewalls.

Expected results:
Find a possibility to change child channel URLs to https protocol to install all components via https regardless if parent or child channel.

Additional info:

Comment 2 Andreas Schmechtig 2017-11-23 15:26:54 UTC
Meanwhile we are on Spacewalk 2.7.
So I think it makes no sense to keep this open.

regards
Andreas


Note You need to log in before you can comment on or make changes to this bug.