-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
6.11.0
-
0
-
False
-
-
False
-
CLOSED
-
800
-
Endeavour
-
-
-
Sat_docs_1_2024
-
Moderate
-
No
Description of problem:
Not able to select the Satellite as a template capsule for subnet after upgrade. Section 4.1.3 of the upgrade guide indicates that we need to update the subnets as part of the post upgrade process. The upgrade of a capsule server turns on the template capsule feature, but the upgrade of the satellite does not. You cannot then select a template capsule for the subnets managed by the Satellite server.
Version-Release number of selected component (if applicable):
6.10.5 -> 6.11GA
How reproducible:
unknown
Steps to Reproduce:
1. Follow upgrade guide for Satellite.
2. Follow upgrade guide for Capsule
3. Subnet assigned to Satellite does not show satellite available for template capsule.
Actual results:
satellite-installer --scenario=satellite --help | grep template
--[no-]enable-foreman-plugin-templates Enable 'foreman_plugin_templates' puppet module (default: true)
--foreman-proxy-template-url URL a client should use for provisioning templates (current: "http://sat6.parmstrong.ca:8000")
--foreman-proxy-templates Enable templates feature (current: false)
--foreman-proxy-templates-listen-on Templates proxy to listen on https, http, or both (current: "both")
Expected results:
template capsule can be selected for subnet
Additional info:
Calling satellite-installer --scenario=satellite --foreman-proxy-templates=true
turns on the functionality and allows a user to select the Satellite server as the template capsule for the subnet.